Boot time tripled after last nights Updates

[bonesaw]

After last nights updates I did a reboot and after setting for more than a minute on the splash screen I rebooted again and again it just sat at the splash screen for over a minute so I rebooted and selected a snapshot from the day before. This time it still sat at the splash screen, but I chose to let it sit and see if it would go to the desktop after all. After about taking about 3 times longer to get to the desktop it finally did. I then did another reboot and when I got the splash screen I hit Esc and saw this message “setfont: kdfontop: function not implemented”. I don’t think that is part of the issue but figure I’d mention it just in case. At this point I’m assuming the nVidia or the systemd update is the actual cause. Anyone else experiencing this or have suggestions on tracking down and possibly fixing the issue? Thanks

[boot] setfont: KDFONTOP: Function not implemented

During boot, I always see the message: setfont: KDFONTOP: Function not implemented I was unable to find much of anything on it. Here are three (Possibly related) links: https://forums.gentoo.org/viewtopic-t-335492-start-0.html https://bbs.archlinux.org/viewtopic.php?id=146038 A typical recommendation for this would probably be to ignore or suppress it. I don't have time to dig deeper at the moment so posting this here as a placeholder.

 
╭─jigsaw@NSAFieldStation in ~ 
╰─λ systemd-analyze
Startup finished in 15.245s (firmware) + 2.535s (loader) + 3.445s (kernel) + 1min 37.918s (userspace) = 1min 59.144s 
graphical.target reached after 1min 37.918s in userspace

╭─jigsaw@NSAFieldStation in ~ took 5ms
╰─λ systemd-analyze blame
14.581s man-db.service
5.707s NetworkManager-wait-online.service
1.011s fwupd.service
836ms updatedb.service
436ms lvm2-monitor.service
424ms udisks2.service
376ms dev-nvme0n1p2.device
306ms mnt-Downloads.mount
225ms systemd-remount-fs.service
220ms mnt-Movies.mount
219ms mnt-Television.mount
211ms systemd-tmpfiles-setup.service
196ms snapd.service
196ms ldconfig.service
178ms [email protected]
166ms mnt-Movie\x20Series.mount
161ms var-lib-snapd-snap-core-11316.mount
159ms systemd-journal-flush.service
155ms var-lib-snapd-snap-scrcpy-283.mount
152ms mnt-Master\x20Backup.mount
147ms var-lib-snapd-snap-core18-2074.mount
146ms var-lib-snapd-snap-scrcpy-276.mount
140ms var-lib-snapd-snap-gnome\x2d3\x2d34\x2d1804-72.mount
140ms mnt-Docs.mount
140ms mnt-XXX.mount
138ms mnt-Master\x20Backup\x202.mount
136ms var-lib-snapd-snap-core18-2066.mount

╭─jigsaw@NSAFieldStation in ~  
╰─λ inxi -Fza
System:    Kernel: 5.12.15-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0  
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=78688345-46c9-46e1-9ff4-63d70dd964a1  
rw rootflags=subvol=@ quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 loglevel=3
Desktop: KDE Plasma 5.22.3 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux  
base: Arch Linux  
Machine:   Type: Desktop System: ASUS product: N/A v: N/A serial: <filter>  
Mobo: ASUSTeK model: ROG STRIX B550-F GAMING v: Rev X.0x serial: <filter>  
UEFI: American Megatrends v: 2403 date: 06/16/2021  
Battery:   Device-1: hidpp_battery_2 model: Logitech Wireless Mouse M325 serial: <filter>  
charge: 55% (should be ignored) rechargeable: yes status: Discharging  
Device-2: hidpp_battery_3 model: Logitech Wireless Keyboard K360 serial: <filter>  
charge: 100% (should be ignored) rechargeable: yes status: Discharging  
CPU:       Info: 6-Core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2 family: 17 (23)  
model-id: 71 (113) stepping: 0 microcode: 8701021 cache: L2: 3 MiB  
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 86237  
Speed: 3592 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 3592 2: 3591  
3: 3592 4: 3380 5: 3592 6: 3353 7: 4191 8: 3359 9: 3587 10: 3580 11: 3550 12: 3353  
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 and seccomp  
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization  
Type: spectre_v2  
mitigation: Full AMD retpoline, IBPB: conditional, STIBP: conditional, RSB filling  
Type: srbds status: Not affected  
Type: tsx_async_abort status: Not affected  
Graphics:  Device-1: NVIDIA TU116 [GeForce GTX 1650 SUPER] vendor: eVga.com. driver: nvidia v: 470.57.02  
alternate: nouveau,nvidia_drm bus-ID: 08:00.0 chip-ID: 10de:2187 class-ID: 0300  
Display: x11 server: X.Org 1.20.12 compositor: kwin_x11 driver: loaded: nvidia display-ID: :0  
screens: 1  
Screen-1: 0 s-res: 2560x1080 s-dpi: 97 s-size: 670x283mm (26.4x11.1") s-diag: 727mm (28.6")  
Monitor-1: HDMI-0 res: 2560x1080 hz: 60 dpi: 97 size: 673x284mm (26.5x11.2")  
diag: 730mm (28.8")  
OpenGL: renderer: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 v: 4.6.0 NVIDIA 470.57.02  
direct render: Yes  
Audio:     Device-1: NVIDIA TU116 High Definition Audio vendor: eVga.com. driver: snd_hda_intel v: kernel  
bus-ID: 08:00.1 chip-ID: 10de:1aeb class-ID: 0403  
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel  
bus-ID: 0a:00.4 chip-ID: 1022:1487 class-ID: 0403  
Sound Server-1: ALSA v: k5.12.15-zen1-1-zen running: yes  
Sound Server-2: JACK v: 0.125.0 running: no  
Sound Server-3: PulseAudio v: 14.2 running: yes  
Sound Server-4: PipeWire v: 0.3.32 running: yes  
Network:   Device-1: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel port: N/A bus-ID: 07:00.0  
chip-ID: 8086:15f3 class-ID: 0200  
IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>  
Drives:    Local Storage: total: 20.48 TiB used: 9.51 TiB (46.4%)  
SMART Message: Unable to run smartctl. Root privileges required.  
ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Seagate model: XPG GAMMIX S11 Pro size: 476.94 GiB  
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 rotation: SSD  
serial: <filter> rev: 32B3T8EB scheme: GPT  
ID-2: /dev/sda maj-min: 8:0 type: USB vendor: Seagate model: ST8000AS0002-1NA17Z size: 7.28 TiB  
block-size: physical: 4096 B logical: 512 B rotation: 5980 rpm serial: <filter> scheme: GPT  
ID-3: /dev/sdb maj-min: 8:16 type: USB vendor: Seagate model: Expansion HDD size: 7.28 TiB  
block-size: physical: 4096 B logical: 512 B serial: <filter> rev: 1801 scheme: GPT  
ID-4: /dev/sdc maj-min: 8:32 type: USB vendor: Seagate model: ST330006 51NS size: 2.73 TiB
block-size: physical: 4096 B logical: 512 B serial: <filter> rev: 7101 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-5: /dev/sdd maj-min: 8:48 type: USB vendor: Seagate model: ST3000DM 001-1E6166
size: 2.73 TiB block-size: physical: 4096 B logical: 512 B serial: <filter> rev: 7101
scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition: ID-1: / raw-size: 476.68 GiB size: 476.68 GiB (100.00%) used: 61.23 GiB (12.8%) fs: btrfs
dev: /dev/nvme0n1p2 maj-min: 259:5
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 546 KiB (0.2%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:4
ID-3: /home raw-size: 476.68 GiB size: 476.68 GiB (100.00%) used: 61.23 GiB (12.8%) fs: btrfs
dev: /dev/nvme0n1p2 maj-min: 259:5
ID-4: /var/log raw-size: 476.68 GiB size: 476.68 GiB (100.00%) used: 61.23 GiB (12.8%)
fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:5
ID-5: /var/tmp raw-size: 476.68 GiB size: 476.68 GiB (100.00%) used: 61.23 GiB (12.8%)
fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:5
Swap:      Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.33 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:   System Temperatures: cpu: 38.6 C mobo: N/A gpu: nvidia temp: 43 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:      Processes: 426 Uptime: 8h 13m wakeups: 43 Memory: 31.33 GiB used: 8.73 GiB (27.9%)
Init: systemd v: 249 tool: systemctl Compilers: gcc: 11.1.0 clang: 12.0.1 Packages: 1989
pacman: 1955 lib: 553 flatpak: 23 snap: 11 Shell: fish v: 3.3.1 default: Zsh v: 5.8
running-in: konsole inxi: 3.3.05

╭─jigsaw@NSAFieldStation in ~ took 1s
╰─λ

[dalto]

@bonesaw

graphical.target reached after 1min 37.918s in userspace

That seems bad. Perhaps something waiting for timeout?

Does systemctl list-units --failed return anything?

[petsam]

@bonesaw

nvidia v: 470.57.02

Is this new? I missed it…

[TilliDie]

Yes it came out on monday the new nvidia driver

[bonesaw]

Here. should add once on the desktop everything seems good. I checked my programs, switched between my various virtual desktops, checked the browsers and all seems as it was prior to the updates. The time from clicking restart and seeing the Grub screen hasn't changed, whatever is up seems to be after I press enter at the Grub screen.

╭─jigsaw@NSAFieldStation in ~
╰─λ systemctl list-units --failed
UNIT           LOAD   ACTIVE SUB    DESCRIPTION
● shadow.service loaded failed failed Verify integrity of password and group files

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
1 loaded units listed.

@petsam it dropped at least 12 hours ago. I checked updates at 7:45 last night and it was there and it's 8:15Am now so it was dropped over 12 hours ago. Thought it odd that they would chose to drop Systemd, nViudia, and a Chrome update at the same time.

[bonesaw]

This and one thread on Reddit refer to removing a user.

I cannot load the shadow service [Solved]

r/archlinux - Error regarding shadow.service

╭─jigsaw@NSAFieldStation in ~  
╰─λ journalctl --no-hostname --no-pager -u shadow.service
-- Journal begins at Fri 2021-06-11 05:54:19 PDT, ends at Wed 2021-07-21 08:24:48 PDT. --
Jun 12 02:33:26 systemd[1]: Started Verify integrity of password and group files.
Jun 12 02:33:26 systemd[1]: shadow.service: Deactivated successfully.
-- Boot 2d668214e216444c9695b26da23cc29f --
Jun 13 00:00:43 systemd[1]: Started Verify integrity of password and group files.
Jun 13 00:00:43 systemd[1]: shadow.service: Deactivated successfully.
-- Boot f77380ef3ba24270aa523f322bbfa70f --
Jun 14 00:00:23 systemd[1]: Started Verify integrity of password and group files.
Jun 14 00:00:23 systemd[1]: shadow.service: Deactivated successfully.
-- Boot e8088670a4a242f6a6c5365aace0c5d5 --
Jun 15 00:00:46 systemd[1]: Started Verify integrity of password and group files.
Jun 15 00:00:46 systemd[1]: shadow.service: Deactivated successfully.
-- Boot 0aa35989d5cc4012ac716227947826ec --
Jun 15 14:33:45 systemd[1]: Started Verify integrity of password and group files.
Jun 15 14:33:45 systemd[1]: shadow.service: Deactivated successfully.
-- Boot 5312a34892a9434c9f40ad014f68d0e0 --
Jun 16 04:15:55 systemd[1]: Started Verify integrity of password and group files.
Jun 16 04:15:55 systemd[1]: shadow.service: Deactivated successfully.
Jun 17 00:00:00 systemd[1]: Started Verify integrity of password and group files.
Jun 17 00:00:00 systemd[1]: shadow.service: Deactivated successfully.
Jun 18 00:00:00 systemd[1]: Started Verify integrity of password and group files.
Jun 18 00:00:00 systemd[1]: shadow.service: Deactivated successfully.
Jun 19 00:00:00 systemd[1]: Started Verify integrity of password and group files.
Jun 19 00:00:00 systemd[1]: shadow.service: Deactivated successfully.
-- Boot 6589795b88b64da28dba0d16e9dc0936 --
Jun 20 00:01:01 systemd[1]: Started Verify integrity of password and group files.
Jun 20 00:01:01 sh[813859]: user 'emby': directory '/home/emby' does not exist
Jun 20 00:01:01 sh[813859]: pwck: no changes
Jun 20 00:01:01 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jun 20 00:01:01 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot 4a8ab689c12c4166b7e3e14e7dbd107e --
Jun 21 00:00:38 systemd[1]: Started Verify integrity of password and group files.
Jun 21 00:00:38 sh[1152203]: user 'emby': directory '/home/emby' does not exist
Jun 21 00:00:38 sh[1152203]: pwck: no changes
Jun 21 00:00:38 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jun 21 00:00:38 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot 0f7f6d7e4ee64a46b8b494d2d048536d --
Jun 22 00:00:05 systemd[1]: Started Verify integrity of password and group files.
Jun 22 00:00:05 sh[1755918]: user 'emby': directory '/home/emby' does not exist
Jun 22 00:00:05 sh[1755918]: pwck: no changes
Jun 22 00:00:05 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jun 22 00:00:05 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot 6f28008ecf7a457bb282e983769e6b4d --
Jun 23 00:00:18 systemd[1]: Started Verify integrity of password and group files.
Jun 23 00:00:18 sh[1194628]: user 'emby': directory '/home/emby' does not exist
Jun 23 00:00:18 sh[1194628]: pwck: no changes
Jun 23 00:00:18 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jun 23 00:00:18 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot 4e0bc9ea6c384a7b83d1b36c8c6e0127 --
Jun 24 00:00:06 systemd[1]: Started Verify integrity of password and group files.
Jun 24 00:00:06 sh[2390734]: user 'emby': directory '/home/emby' does not exist
Jun 24 00:00:06 sh[2390734]: pwck: no changes
Jun 24 00:00:06 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jun 24 00:00:06 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot 33ee20797d464f9ba282304c4775a294 --
Jun 25 00:00:00 systemd[1]: Started Verify integrity of password and group files.
Jun 25 00:00:00 sh[1119402]: user 'emby': directory '/home/emby' does not exist
Jun 25 00:00:00 sh[1119402]: pwck: no changes
Jun 25 00:00:00 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jun 25 00:00:00 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot 70e415e9c9be46efb101a0a24b04589d --
Jun 26 00:00:57 systemd[1]: Started Verify integrity of password and group files.
Jun 26 00:00:57 sh[1274054]: user 'emby': directory '/home/emby' does not exist
Jun 26 00:00:57 sh[1274054]: pwck: no changes
Jun 26 00:00:57 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jun 26 00:00:57 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot b56f475fa97741ae867132b39fb8df11 --
Jun 27 00:00:52 systemd[1]: Started Verify integrity of password and group files.
Jun 27 00:00:52 sh[1660091]: user 'emby': directory '/home/emby' does not exist
Jun 27 00:00:52 sh[1660091]: pwck: no changes
Jun 27 00:00:52 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jun 27 00:00:52 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot e4a88f3de8a9419d863a6df409dffa25 --
Jun 28 00:00:28 systemd[1]: Started Verify integrity of password and group files.
Jun 28 00:00:28 sh[1653951]: user 'emby': directory '/home/emby' does not exist
Jun 28 00:00:28 sh[1653951]: pwck: no changes
Jun 28 00:00:28 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jun 28 00:00:28 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot 459617a014424fad9bfac6ce8de54103 --
Jun 29 00:00:42 systemd[1]: Started Verify integrity of password and group files.
Jun 29 00:00:42 sh[690982]: user 'emby': directory '/home/emby' does not exist
Jun 29 00:00:42 sh[690982]: pwck: no changes
Jun 29 00:00:42 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jun 29 00:00:42 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot dbb51d1ef7bc486fb969c6010ff61998 --
Jun 30 00:00:00 systemd[1]: Started Verify integrity of password and group files.
Jun 30 00:00:00 sh[302891]: user 'emby': directory '/home/emby' does not exist
Jun 30 00:00:00 sh[302891]: pwck: no changes
Jun 30 00:00:00 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jun 30 00:00:00 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot 75b542dbdf844cad925fbe5573749abd --
Jul 01 00:00:20 systemd[1]: Started Verify integrity of password and group files.
Jul 01 00:00:20 sh[496486]: user 'emby': directory '/home/emby' does not exist
Jul 01 00:00:20 sh[496486]: pwck: no changes
Jul 01 00:00:20 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jul 01 00:00:20 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot 30837cd5d12d4804997ad14b0294cd38 --
Jul 02 00:00:59 systemd[1]: Started Verify integrity of password and group files.
Jul 02 00:00:59 sh[519304]: user 'emby': directory '/home/emby' does not exist
Jul 02 00:00:59 sh[519304]: pwck: no changes
Jul 02 00:00:59 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jul 02 00:00:59 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot 5ef1a3fc64eb4fb1a97b739e6b83e450 --
Jul 03 00:00:23 systemd[1]: Started Verify integrity of password and group files.
Jul 03 00:00:23 sh[724758]: user 'emby': directory '/home/emby' does not exist
Jul 03 00:00:23 sh[724758]: pwck: no changes
Jul 03 00:00:23 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jul 03 00:00:23 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot 04142f3aa9ae4e3084e5b53204060e27 --
Jul 04 00:00:00 systemd[1]: Started Verify integrity of password and group files.
Jul 04 00:00:00 sh[179053]: user 'emby': directory '/home/emby' does not exist
Jul 04 00:00:00 sh[179053]: pwck: no changes
Jul 04 00:00:00 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jul 04 00:00:00 systemd[1]: shadow.service: Failed with result 'exit-code'.
Jul 05 00:00:00 systemd[1]: Started Verify integrity of password and group files.
Jul 05 00:00:00 sh[523859]: user 'emby': directory '/home/emby' does not exist
Jul 05 00:00:00 sh[523859]: pwck: no changes
Jul 05 00:00:00 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jul 05 00:00:00 systemd[1]: shadow.service: Failed with result 'exit-code'.
Jul 06 00:00:00 systemd[1]: Started Verify integrity of password and group files.
Jul 06 00:00:00 sh[853272]: user 'emby': directory '/home/emby' does not exist
Jul 06 00:00:00 sh[853272]: pwck: no changes
Jul 06 00:00:00 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jul 06 00:00:00 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot 10b740fc5a70412ebed1d6c4faaae892 --
Jul 07 00:00:01 systemd[1]: Started Verify integrity of password and group files.
Jul 07 00:00:01 sh[750349]: user 'emby': directory '/home/emby' does not exist
Jul 07 00:00:01 sh[750349]: pwck: no changes
Jul 07 00:00:01 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jul 07 00:00:01 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot 3a872584c8134bddaff188e1c3cb82ce --
Jul 08 00:00:25 systemd[1]: Started Verify integrity of password and group files.
Jul 08 00:00:25 sh[282133]: user 'emby': directory '/home/emby' does not exist
Jul 08 00:00:25 sh[282133]: pwck: no changes
Jul 08 00:00:25 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jul 08 00:00:25 systemd[1]: shadow.service: Failed with result 'exit-code'.
Jul 09 00:00:13 systemd[1]: Started Verify integrity of password and group files.
Jul 09 00:00:13 sh[1033586]: user 'emby': directory '/home/emby' does not exist
Jul 09 00:00:13 sh[1033586]: pwck: no changes
Jul 09 00:00:13 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jul 09 00:00:13 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot 0b7c22dfd8204048936a5e0fe0b0286f --
Jul 10 00:00:11 systemd[1]: Started Verify integrity of password and group files.
Jul 10 00:00:11 sh[166593]: user 'emby': directory '/home/emby' does not exist
Jul 10 00:00:11 sh[166593]: pwck: no changes
Jul 10 00:00:11 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jul 10 00:00:11 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot 5c677ac7805c4611a678d1cf9ace4e44 --
Jul 11 00:00:00 systemd[1]: Started Verify integrity of password and group files.
Jul 11 00:00:00 sh[127325]: user 'emby': directory '/home/emby' does not exist
Jul 11 00:00:00 sh[127325]: pwck: no changes
Jul 11 00:00:00 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jul 11 00:00:00 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot cb701d8c247d4f6dad89f2ca7e4e5f01 --
Jul 12 00:00:53 systemd[1]: Started Verify integrity of password and group files.
Jul 12 00:00:53 sh[1839833]: user 'emby': directory '/home/emby' does not exist
Jul 12 00:00:53 sh[1839833]: pwck: no changes
Jul 12 00:00:53 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jul 12 00:00:53 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot fdd70f43437449b985310f4575072e69 --
Jul 13 00:00:27 systemd[1]: Started Verify integrity of password and group files.
Jul 13 00:00:27 sh[2026733]: user 'emby': directory '/home/emby' does not exist
Jul 13 00:00:27 sh[2026733]: pwck: no changes
Jul 13 00:00:27 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jul 13 00:00:27 systemd[1]: shadow.service: Failed with result 'exit-code'.
Jul 14 00:00:27 systemd[1]: Started Verify integrity of password and group files.
Jul 14 00:00:27 sh[3472096]: user 'emby': directory '/home/emby' does not exist
Jul 14 00:00:27 sh[3472096]: pwck: no changes
Jul 14 00:00:27 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jul 14 00:00:27 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot bb7d8ac5aefe476b8b7fa50e426c8d5a --
Jul 15 00:00:00 systemd[1]: Started Verify integrity of password and group files.
Jul 15 00:00:00 sh[2236785]: user 'emby': directory '/home/emby' does not exist
Jul 15 00:00:00 sh[2236785]: pwck: no changes
Jul 15 00:00:00 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jul 15 00:00:00 systemd[1]: shadow.service: Failed with result 'exit-code'.
Jul 16 00:00:00 systemd[1]: Started Verify integrity of password and group files.
Jul 16 00:00:00 sh[4165702]: user 'emby': directory '/home/emby' does not exist
Jul 16 00:00:00 sh[4165702]: pwck: no changes
Jul 16 00:00:00 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jul 16 00:00:00 systemd[1]: shadow.service: Failed with result 'exit-code'.
Jul 17 00:00:01 systemd[1]: Started Verify integrity of password and group files.
Jul 17 00:00:01 sh[720679]: user 'emby': directory '/home/emby' does not exist
Jul 17 00:00:01 sh[720679]: pwck: no changes
Jul 17 00:00:01 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jul 17 00:00:01 systemd[1]: shadow.service: Failed with result 'exit-code'.
Jul 18 00:00:00 systemd[1]: Started Verify integrity of password and group files.
Jul 18 00:00:00 sh[1006891]: user 'emby': directory '/home/emby' does not exist
Jul 18 00:00:00 sh[1006891]: pwck: no changes
Jul 18 00:00:00 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jul 18 00:00:00 systemd[1]: shadow.service: Failed with result 'exit-code'.
Jul 19 00:00:00 systemd[1]: Started Verify integrity of password and group files.
Jul 19 00:00:00 sh[1564006]: user 'emby': directory '/home/emby' does not exist
Jul 19 00:00:00 sh[1564006]: pwck: no changes
Jul 19 00:00:00 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jul 19 00:00:00 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot 60684b6e87224d17b00f0cb584388171 --
Jul 20 00:00:35 systemd[1]: Started Verify integrity of password and group files.
Jul 20 00:00:35 sh[2540431]: user 'emby': directory '/home/emby' does not exist
Jul 20 00:00:35 sh[2540431]: pwck: no changes
Jul 20 00:00:35 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jul 20 00:00:35 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot eb0336d49632433d9c3706bc64b585d4 --
Jul 20 20:21:39 systemd[1]: Started Verify integrity of password and group files.
Jul 20 20:21:39 sh[661]: user 'emby': directory '/home/emby' does not exist
Jul 20 20:21:39 sh[661]: pwck: no changes
Jul 20 20:21:39 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jul 20 20:21:39 systemd[1]: shadow.service: Failed with result 'exit-code'.
-- Boot 4f9f8e6f55e94db1b2146ec40cb2b93f --
Jul 21 00:00:00 systemd[1]: Started Verify integrity of password and group files.
Jul 21 00:00:00 sh[542156]: user 'emby': directory '/home/emby' does not exist
Jul 21 00:00:00 sh[542156]: pwck: no changes
Jul 21 00:00:00 systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Jul 21 00:00:00 systemd[1]: shadow.service: Failed with result 'exit-code'.

[petsam]

@bonesaw

shadow.service: Failed

This error has nothing to do with your original OT error. Just correct it, if you don’t want to see warnings (they remind you that you did something wrong, or the wrong way ).

@bonesaw

systemd-analyze blame

To get something useful, use this

systemd-analyze critical-chain

[bonesaw]

I just followed where the info took me and "shadow.service: failed" was where I was taken. Here's the info you asked for.

╭─jigsaw@NSAFieldStation in ~
╰─λ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @1min 37.959s
└─multi-user.target @1min 37.959s
└─teamviewerd.service @1min 37.863s +95ms
└─network-online.target @1min 37.861s
└─NetworkManager-wait-online.service @1min 32.150s +5.710s
└─NetworkManager.service @1min 32.102s +46ms
└─dbus.service @1min 32.100s
└─basic.target @1min 32.098s
└─sockets.target @1min 32.098s
└─snapd.socket @1min 32.097s +356us
└─sysinit.target @1min 32.095s
└─systemd-timesyncd.service @1min 32.041s +54ms
└─systemd-tmpfiles-setup.service @1min 31.833s +206ms
└─local-fs.target @1min 31.830s
└─run-user-1000-gvfs.mount @1min 37.673s
└─run-user-1000.mount @1min 33.622s
└─swap.target @2.178s
└─dev-zram0.swap @2.156s +21ms
└─[email protected] @2.105s +50ms
└─dev-zram0.device @2.098s

[dalto]

Can we see lsblk -o name,fstype,size,uuid,mountpoint and the contents of /etc/fstab

[bonesaw]

╭─jigsaw@NSAFieldStation in ~  
╰─λ lsblk -o name,fstype,size,uuid,mountpoint
NAME        FSTYPE     SIZE UUID                                 MOUNTPOINT
loop0       squashfs    20K                                      /var/lib/snapd/snap/hello-world/29
loop1       squashfs  55.4M                                      /var/lib/snapd/snap/core18/2066
loop2       squashfs 193.5M                                      /var/lib/snapd/snap/picard/632
loop3       squashfs    93M                                      /var/lib/snapd/snap/youtube-dl/4568
loop4       squashfs  55.4M                                      /var/lib/snapd/snap/core18/2074
loop5       squashfs    51M                                      /var/lib/snapd/snap/snap-store/547
loop6       squashfs  82.9M                                      /var/lib/snapd/snap/scrcpy/283
loop7       squashfs  82.9M                                      /var/lib/snapd/snap/scrcpy/276
loop8       squashfs  65.1M                                      /var/lib/snapd/snap/gtk-common-themes/1515
loop9       squashfs  61.7M                                      /var/lib/snapd/snap/core20/1026
loop10      squashfs  92.8M                                      /var/lib/snapd/snap/youtube-dl/3805
loop11      squashfs   219M                                      /var/lib/snapd/snap/gnome-3-34-1804/72
loop12      squashfs  99.4M                                      /var/lib/snapd/snap/core/11187
loop13      squashfs  99.4M                                      /var/lib/snapd/snap/core/11316
sda                    7.3T
└─sda1      ext4       7.3T 0a31a19b-b10e-4fec-857e-317dc6113e92 /mnt/Master Backup
sdb                    2.7T
└─sdb1      ext4       2.7T 8e37f67a-3bec-4ccd-8adf-e41c63d0fe07 /mnt/Master Backup 2
sdc                    7.3T
├─sdc1      ext4       4.1T e47dfa9c-4b1f-4d4d-83c5-c78c48f3c087 /mnt/Television
├─sdc2      ext4       2.3T d0636ad1-e534-4831-8bbc-c29cf40dd262 /mnt/Movies
├─sdc3      ext4     232.7G 66680475-7b00-4600-be67-950f78ee5818 /mnt/Music Videos
├─sdc4      ext4     476.2G 2f8b8a65-923f-418a-8050-5c1fc9e14bb1 /mnt/Downloads
└─sdc5      ext4     200.2G 5a22def7-5780-4a1a-8b88-3d8bece55554 /mnt/Docs
sdd                    2.7T
├─sdd1      ext4     732.2G 6856cc2d-558b-445f-89e9-0b2f590c67d4 /mnt/XXX
├─sdd2      ext4       198G b681c23e-da1b-49e4-934d-f448145236d9 /mnt/Music
└─sdd3      ext4       1.8T 9357e542-82f2-4190-ab23-87733e51f084 /mnt/Movie Series
zram0                 31.3G                                      [SWAP]
nvme1n1              238.5G
├─nvme1n1p1 vfat       500M 9821-0A90
└─nvme1n1p2 btrfs      238G 22f293c1-419a-4f27-b6f5-7846acc7aa56
nvme0n1              476.9G
├─nvme0n1p1 vfat       256M 9C64-4805                            /boot/efi
└─nvme0n1p2 btrfs    476.7G 78688345-46c9-46e1-9ff4-63d70dd964a1 /run/timeshift/backup

# /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=9C64-4805                            /boot/efi      vfat    umask=0077 0 2
UUID=78688345-46c9-46e1-9ff4-63d70dd964a1 /              btrfs   subvol=/@,defaults,noatime,space_cache,autodefrag,compress=zstd 0 1
UUID=78688345-46c9-46e1-9ff4-63d70dd964a1 /home          btrfs   subvol=/@home,defaults,noatime,space_cache,autodefrag,compress=zstd 0 2
UUID=78688345-46c9-46e1-9ff4-63d70dd964a1 /root          btrfs   subvol=/@root,defaults,noatime,space_cache,autodefrag,compress=zstd 0 2
UUID=78688345-46c9-46e1-9ff4-63d70dd964a1 /srv           btrfs   subvol=/@srv,defaults,noatime,space_cache,autodefrag,compress=zstd 0 2
UUID=78688345-46c9-46e1-9ff4-63d70dd964a1 /var/cache     btrfs   subvol=/@cache,defaults,noatime,space_cache,autodefrag,compress=zstd 0 2
UUID=78688345-46c9-46e1-9ff4-63d70dd964a1 /var/log       btrfs   subvol=/@log,defaults,noatime,space_cache,autodefrag,compress=zstd 0 2
UUID=78688345-46c9-46e1-9ff4-63d70dd964a1 /var/tmp       btrfs   subvol=/@tmp,defaults,noatime,space_cache,autodefrag,compress=zstd 0 2
/dev/disk/by-id/usb-Seagate_Expansion_HDD_00000000NAC60TMX-0:0-part1 /mnt/Television/ auto nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-id/usb-ST3000DM_001-1E6166_DD564198838DA-0:0-part4 /mnt/Television\0402/ auto nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-id/usb-Seagate_Expansion_HDD_00000000NAC60TMX-0:0-part2 /mnt/Movies/ auto nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-id/usb-Seagate_Expansion_HDD_00000000NAC60TMX-0:0-part3 /mnt/Music\040Videos/ auto nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-id/usb-Seagate_Expansion_HDD_00000000NAC60TMX-0:0-part4 /mnt/Downloads/ auto nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-id/usb-Seagate_Expansion_HDD_00000000NAC60TMX-0:0-part5 /mnt/Docs/ auto nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-id/usb-ST3000DM_001-1E6166_DD564198838DA-0:0-part2 /mnt/Music/ auto nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-id/usb-ST3000DM_001-1E6166_DD564198838DA-0:0-part1 /mnt/XXX/ auto nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-id/usb-ST3000DM_001-1E6166_DD564198838DA-0:0-part3 /mnt/Movie\040Series/ auto nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-id/wwn-0x5000c50092e490e9-part1 /mnt/Master\040Backup/ auto nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-id/usb-ST330006_51NS_DD564198838DA-0:0-part1 /mnt/Master\040Backup\0402/ auto nosuid,nodev,nofail,x-gvfs-show 0 0

Please ignore Television 2 cause I just removed it. Forgot to yeaterday.

[dalto]

@bonesaw

Please ignore Television 2 cause I just removed it. Forgot to yeaterday.

That is probably your problem. Try rebooting. You have tons of auto,nofail mounts which means it won’t fail but it will still try to mount them. From your output you have 90 second wait while mounting…something.

[bonesaw]

I agree it's probably sitting there trying to boot into a nonexistent partition. Be back. Thanks

[bonesaw]

Thanks that does seem to have done the trick. Can't believe I forgot that after removing a partition. Well it was basically bedtime. Thanks again.

[petsam]

@bonesaw

after setting for more than a minute on the splash screen I rebooted again and again it just sat at the splash screen for over a minute

One minute late or so is not enough to risk breaking your hard drives with hard rebooting.

It seems this makes your clever system to check drives file systems, to save you from potential loss.

Check your journal for errors (-p3) and if there are not several, you just have to calm down and stop playing with the computers.

---

Edit: Oh, I did not read the latest posts, but I guess I was on target