Stuck at clean, files, block at boot

Support
,
1

Hello there!

My laptop (Lenovo Legion 5) gets stuck on dev/nvme0np5: clean, x/x files, x/x blocks for ~2mins every time I boot it.
It also has other problems (mainly with suspending) that probably come from the same cause, which I strongly suspect to be the NVidia driver (as always)…

I have had this issue for around 1 month now and I have tried to resolve it on:

  • linux515/manjaro stable
  • linux516/manjaro stable
  • linux517/manjaro stable
  • linux517/manjaro testing
  • linux518/manjaro testing
    On all these configs the issue continues to occur…

I have tried this solution already, just if anyone tries to redirect me there.

All packages are up to date (pamac).

mhwd -l:

> 0000:03:00.0 (0200:10ec:8168) Network controller Realtek Semiconductor Co., Ltd.:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
         network-r8168            2016.04.20                true            PCI


> 0000:01:00.0 (0300:10de:2560) Display controller nVidia Corporation:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
          video-nvidia            2021.12.18               false            PCI
    video-nvidia-470xx            2021.12.18               false            PCI
           video-linux            2018.05.04                true            PCI
     video-modesetting            2020.01.13                true            PCI
            video-vesa            2017.03.12                true            PCI

mhwd -li:

[kendlbat@oxygen ~]$ mhwd -li
> Installed PCI configs:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
           video-linux            2018.05.04                true            PCI
          video-nvidia            2021.12.18               false            PCI


Warning: No installed USB configs!

I really want to thank everyone who reads through this post and I appreciate y’all!

2

post formated output from inxi -Fazy

3 
System:
  Kernel: 5.18.0-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 11.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.18-x86_64
    root=UUID=2301193a-578a-497e-8fb6-08bbffaa02e3 rw quiet splash apparmor=1
    security=apparmor udev.log_priority=3
  Desktop: GNOME v: 42.1 tk: GTK v: 3.24.33 wm: gnome-shell dm: GDM v: 42.0
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 82JY v: Legion 5 17ACH6H
    serial: <superuser required> Chassis: type: 10 v: Legion 5 17ACH6H
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0R32862 WIN
    serial: <superuser required> UEFI: LENOVO v: GKCN49WW date: 11/08/2021
Battery:
  ID-1: BAT0 charge: 47.8 Wh (64.9%) condition: 73.6/80.0 Wh (92.0%)
    volts: 15.5 min: 15.4 model: Celxpert L20C4PC2 type: Li-poly
    serial: <filter> status: discharging cycles: 190
CPU:
  Info: model: AMD Ryzen 7 5800H with Radeon Graphics bits: 64 type: MT MCP
    arch: Zen 3 family: 0x19 (25) model-id: 0x50 (80) stepping: 0
    microcode: 0xA50000C
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
    L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 2810 high: 3169 min/max: 400/4463 boost: enabled
    scaling: driver: amd-pstate governor: schedutil cores: 1: 2860 2: 2828
    3: 2530 4: 2535 5: 2535 6: 2535 7: 3169 8: 3169 9: 2533 10: 2535 11: 3169
    12: 3166 13: 2531 14: 2535 15: 3169 16: 3168 bogomips: 102248
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: always-on, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] vendor: Lenovo
    driver: nvidia v: 510.68.02 alternate: nouveau,nvidia_drm pcie: gen: 1
    speed: 2.5 GT/s lanes: 8 link-max: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 01:00.0 chip-ID: 10de:2560 class-ID: 0300
  Device-2: Acer Integrated Camera type: USB driver: uvcvideo bus-ID: 1-3:3
    chip-ID: 5986:212b class-ID: 0e02
  Display: x11 server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.1
    compositor: gnome-shell driver: X: loaded: nvidia gpu: nvidia display-ID: :1
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-size: <missing: xdpyinfo>
  Monitor-1: DP-4 res: 1920x1080 hz: 144 dpi: 128 size: 381x214mm (15x8.43")
    diag: 437mm (17.2") modes: N/A
  OpenGL: renderer: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2
    v: 4.6.0 NVIDIA 510.68.02 direct render: Yes
Audio:
  Device-1: NVIDIA driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s
    lanes: 8 link-max: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.1
    chip-ID: 10de:228e class-ID: 0403
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Lenovo driver: N/A
    alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_sof_amd_renoir
    pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s
    bus-ID: 05:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h/19h HD Audio vendor: Lenovo driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s bus-ID: 05:00.6 chip-ID: 1022:15e3 class-ID: 0403
  Sound Server-1: ALSA v: k5.18.0-1-MANJARO running: yes
  Sound Server-2: sndio v: N/A running: no
  Sound Server-3: PulseAudio v: 15.0 running: no
  Sound Server-4: PipeWire v: 0.3.51 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Lenovo driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    port: 2000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: eno1 state: down mac: <filter>
  Device-2: Realtek RTL8852AE 802.11ax PCIe Wireless Network Adapter
    vendor: Lenovo driver: rtw89_8852ae v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: 1000 bus-ID: 04:00.0 chip-ID: 10ec:8852 class-ID: 0280
  IF: wlp4s0 state: up mac: <filter>
Bluetooth:
  Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8
    bus-ID: 3-4:3 chip-ID: 0bda:4852 class-ID: e001 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 2 state: up address: see --recommends
Drives:
  Local Storage: total: 476.94 GiB used: 238.03 GiB (49.9%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: MZALQ512HBLU-00BL2 size: 476.94 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 5L2QFXM7 temp: 27.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 476.28 GiB size: 467.72 GiB (98.20%)
    used: 238.03 GiB (50.9%) fs: ext4 dev: /dev/nvme0n1p5 maj-min: 259:2
  ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
    used: 2.7 MiB (2.8%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 8 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Sensors:
  System Temperatures: cpu: N/A mobo: N/A gpu: nvidia temp: 37 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 330 Uptime: 37m wakeups: 1 Memory: 15.54 GiB
  used: 3.46 GiB (22.2%) Init: systemd v: 250 target: graphical.target
  tool: systemctl Compilers: gcc: 11.2.0 clang: 13.0.1 Packages: 1761
  pacman: 1718 lib: 519 flatpak: 34 snap: 9 Shell: Bash v: 5.1.16
  running-in: gnome-terminal inxi: 3.3.15
4

you could go to etc/default/grub and from GRUB_CMDLINE_LINUX_DEFAULT remove ‘quiet’ , save and exit the file, run sudo update-grub reboot and see on what its stuck exactly…

5

Or you could simply look for errors in the journals.

6

Ok, after doing that and rebooting, the “more concise” version says:

A start job is running for /dev/disk/by-uuid (xs / 1min 30s)

The output from journalctl --boot=-1 --priority=3 --catalog is:

Mai 08 17:25:26 oxygen kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PB2], AE_NOT_>
Mai 08 17:25:26 oxygen kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20211217/psobject->
Mai 08 17:25:26 oxygen kernel: 
Mai 08 17:25:26 oxygen systemd-fstab-generator[326]: Failed to create unit file /run/systemd/generator/>
Mai 08 17:25:26 oxygen systemd[317]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed >
Mai 08 17:25:26 oxygen systemd-modules-load[346]: Failed to find module 'vboxdrv'
Mai 08 17:25:26 oxygen systemd-modules-load[346]: Failed to find module 'vboxnetadp'
Mai 08 17:25:26 oxygen systemd-modules-load[346]: Failed to find module 'vboxnetflt'
Mai 08 17:25:26 oxygen kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD.>
Mai 08 17:25:26 oxygen kernel: ACPI Error: Aborting method \_SB.PCI0.GP17.VGA.LCD._BCM due to previous >
Mai 08 17:26:56 oxygen systemd[1]: Timed out waiting for device /dev/disk/by-uuid.
░░ Subject: A start job for unit dev-disk-by\x2duuid.device has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
Mai 08 17:25:26 oxygen kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PB2], AE_NOT_>
Mai 08 17:25:26 oxygen kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20211217/psobject->
Mai 08 17:25:26 oxygen kernel: 
Mai 08 17:25:26 oxygen systemd-fstab-generator[326]: Failed to create unit file /run/systemd/generator/>
Mai 08 17:25:26 oxygen systemd[317]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed >
Mai 08 17:25:26 oxygen systemd-modules-load[346]: Failed to find module 'vboxdrv'
Mai 08 17:25:26 oxygen systemd-modules-load[346]: Failed to find module 'vboxnetadp'
Mai 08 17:25:26 oxygen systemd-modules-load[346]: Failed to find module 'vboxnetflt'
Mai 08 17:25:26 oxygen kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD.>
Mai 08 17:25:26 oxygen kernel: ACPI Error: Aborting method \_SB.PCI0.GP17.VGA.LCD._BCM due to previous >
Mai 08 17:26:56 oxygen systemd[1]: Timed out waiting for device /dev/disk/by-uuid.
░░ Subject: A start job for unit dev-disk-by\x2duuid.device has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit dev-disk-by\x2duuid.device has finished with a failure.
░░ 
░░ The job identifier is 66 and the job result is timeout.
Mai 08 17:26:58 oxygen systemd[1]: Failed to start Service for snap application anbox.container-manager.
░░ Subject: A start job for unit snap.anbox.container-manager.service has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit snap.anbox.container-manager.service has finished with a failure.
░░ 
░░ The job identifier is 1526 and the job result is failed.
Mai 08 17:27:01 oxygen gnome-session-binary[1070]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error >
Mai 08 17:27:01 oxygen gnome-session-binary[1070]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error >
Mai 08 17:27:07 oxygen gdm-password][1328]: gkr-pam: unable to locate daemon control file
Mai 08 17:27:11 oxygen systemd[1339]: Failed to start Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 442 and the job result is failed.
Mai 08 17:27:11 oxygen systemd[1339]: Failed to start Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 454 and the job result is failed.
Mai 08 17:27:11 oxygen systemd[1339]: Failed to start Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 422 and the job result is failed.
Mai 08 17:27:14 oxygen gdm-launch-environment][962]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJE>
Mai 08 18:23:54 oxygen gdm[831]: Gdm: Failed to contact accountsservice: Error calling StartServiceByNa>
Mai 08 18:23:56 oxygen systemd[1339]: Failed to start Portal service (GTK/GNOME implementation).
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 893 and the job result is failed.
Mai 08 18:23:57 oxygen kernel: watchdog: watchdog0: watchdog did not stop!

( “Mai” is just the german word for May, even though the system is set to English, it still uses German here for some reason…?; “oxygen” is the name of my Computer if anyone’s wondering)

7

boot into tty, enter your credentials, and try reinstalling these:
sudo pacman -S gnome-shell
sudo pacman -S gnome-session
sudo pacman -S gdm
systemctl reboot

8

Let’s get details on the failed services.

journalctl --boot=-1 --unit=dev-disk-by\x2duuid.device
journalctl --boot=-1 --unit=snap.anbox.container-manager.service
journalctl --boot=-1 --unit=gnome-session-binary

Here are some tips for extracting the information: [HowTo] Use the terminal / TTY

9

No infos on dev-disk-by\xduuid.device and gnome-session-binary.

I just uninstalled anbox and will see if it helps in any way

10

Don’t forget the 2 !

11

I have ran the tty commands as instructed, (while I had to substitute gdm for gdm-plymouth) yet still hangs at the same point on boot

12

Ok, status quo is:

  • Uninstalling Anbox didn’t help
  • Reinstalling gnome-shell, gnome-session and gdm-plymouth didn’t help
  • There are “-- No entries --” from journalctl for the devices @maycne.sonahoz suggested

So we’re basically back to exactly where we started…
Still gets stuck at A start job is running for /dev/disk/by-uuid (xs / 1min 30s).
It just sits there, counts up to 1:30 and then boots instantly. Maybe I can somehow shorten the timeout to like .1sec?

13

and if you reinstall virtualbox - there are error logs regarding it, then reboot

14

I just uninstalled it as I don’t really use it anyway and still just hangs…

The current output from journalctl --boot=-1 --unit=gnome-session-binary is:

Mai 08 19:11:54 oxygen kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PB2], AE_NOT_FOUND (20211217/dswload2-162)
Mai 08 19:11:54 oxygen kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20211217/psobject-220)
Mai 08 19:11:54 oxygen kernel: 
Mai 08 19:11:54 oxygen systemd-fstab-generator[324]: Failed to create unit file /run/systemd/generator/dev-disk-by\x2duuid.swap, as it already exists. Duplicate entry in /etc/fstab?
Mai 08 19:11:54 oxygen systemd[317]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
Mai 08 19:11:54 oxygen systemd-modules-load[342]: Failed to find module 'vboxdrv'
Mai 08 19:11:54 oxygen systemd-modules-load[342]: Failed to find module 'vboxnetadp'
Mai 08 19:11:54 oxygen systemd-modules-load[342]: Failed to find module 'vboxnetflt'
Mai 08 19:11:54 oxygen kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20211217/psargs-330)
Mai 08 19:11:54 oxygen kernel: ACPI Error: Aborting method \_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
Mai 08 19:13:24 oxygen systemd[1]: Timed out waiting for device /dev/disk/by-uuid.
░░ Subject: A start job for unit dev-disk-by\x2duuid.device has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit dev-disk-by\x2duuid.device has finished with a failure.
░░ 
░░ The job identifier is 62 and the job result is timeout.
Mai 08 19:13:28 oxygen gnome-session-binary[817]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Mai 08 19:13:28 oxygen gnome-session-binary[817]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Mai 08 19:13:40 oxygen gdm-password][1076]: gkr-pam: unable to locate daemon control file
Mai 08 19:13:45 oxygen systemd[1087]: Failed to start Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 422 and the job result is failed.
Mai 08 19:13:47 oxygen gnome-session-binary[817]: GLib-CRITICAL: g_hash_table_foreach_remove_or_steal: assertion 'version == hash_table->version' failed
Mai 08 19:13:47 oxygen gdm-launch-environment][768]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Mai 08 19:22:30 oxygen systemd-fstab-generator[2391]: Failed to create unit file /run/systemd/generator/dev-disk-by\x2duuid.swap, as it already exists. Duplicate entry in /etc/fstab?
Mai 08 19:22:30 oxygen systemd[2384]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
Mai 08 19:22:38 oxygen sudo[2420]: pam_unix(sudo:auth): conversation failed
Mai 08 19:22:38 oxygen sudo[2420]: pam_unix(sudo:auth): auth could not identify password for [kendlbat]
Mai 08 19:22:38 oxygen sudo[2420]: pam_unix(sudo:auth): conversation failed
Mai 08 19:22:38 oxygen sudo[2420]: pam_unix(sudo:auth): auth could not identify password for [kendlbat]
Mai 08 19:22:43 oxygen gdm[737]: Gdm: Failed to contact accountsservice: Error calling StartServiceByName for org.freedesktop.Accounts: Refusing activation, D-Bus is shutting down.
Mai 08 19:22:45 oxygen kernel: watchdog: watchdog0: watchdog did not stop!
15

What is your partitioning scheme?

cat /etc/fstab
lsblk -fa
LANG=C sudo parted -l
16 
[kendlbat@oxygen ~]$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=DA0A-16B4                            /boot/efi      vfat    umask=0077 0 2
UUID=2301193a-578a-497e-8fb6-08bbffaa02e3 /              ext4    defaults,noatime 0 1
UUID= none swap defaults 0 0
UUID= none swap defaults 0 0
/swapfile none swap defaults 0 0
[kendlbat@oxygen ~]$ lsblk -fa
NAME        FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1                                                                            
├─nvme0n1p1 vfat   FAT32       DA0A-16B4                              93,3M     3% /boot/efi
└─nvme0n1p5 ext4   1.0         2301193a-578a-497e-8fb6-08bbffaa02e3  207,8G    50% /
[kendlbat@oxygen ~]$ LANG=C sudo parted -l
[sudo] password for kendlbat: 
Model: SAMSUNG MZALQ512HBLU-00BL2 (nvme)
Disk /dev/nvme0n1: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size   File system  Name                  Flags
 1      1049kB  106MB  105MB  fat32        EFI system partition  boot, esp
 5      106MB   512GB  511GB  ext4         root
17

I am not so familiar with swapfiles, but i suppose that:

  • you don’t need to declare a swap partition (through UUID) if you use a swapfile
  • furthermore, that any partition declared there through UUID should have an UUID
  • furthermore, that you shouldn’t have a mount declared twice

I’d suggest removing (or commenting) those first two lines.

18

Thanks a lot for both of your help!
Commenting the mentioned lines in /etc/fstab worked!

19

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.