Slow to boot after updates

Updates went fine, didn’t see any errors per say, but I went from about 10 seconds to login, to about 4 to 5 minutes. Where is a good place to looks to see what it is hanging or does not like now?

System seems fine once I login, no issues. Just slow getting to login page now.

It was almost instant on before updates. ;-).

Below is is the Garuda-inxi

garuda-inxi
System:
Kernel: 6.6.3-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc available: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=85d10ba7-1da5-4b61-a934-a0dd37c75c5e rw rootflags=subvol=@
rd.driver.pre=vfio-pci intel_iommu=on rd.udev.log_priority=3
vt.global_cursor_default=0 loglevel=3 vfio_pci.ids=10de:1c82,10de:0fb9
pcie_acs_override=downstream,multifunction video=efifb:off iommu=pt
ibt=off
Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.11 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: TUF GAMING Z590-PLUS WIFI v: Rev 1.xx
serial: <superuser required> UEFI: American Megatrends v: 1801
date: 12/26/2022
Battery:
Device-1: hid-0003:256F:C62E.0002-battery model: 3Dconnexion SpaceMouse
Wireless serial: N/A charge: N/A status: discharging
CPU:
Info: model: 11th Gen Intel Core i9-11900KF bits: 64 type: MT MCP
arch: Rocket Lake gen: core 11 level: v4 note: check built: 2021+
process: Intel 14nm family: 6 model-id: 0xA7 (167) stepping: 1
microcode: 0x5D
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 640 KiB desc: d-8x48 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 1450 high: 5100 min/max: 800/5100:5300 scaling:
driver: intel_pstate governor: powersave cores: 1: 800 2: 800 3: 2607
4: 5100 5: 5100 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800
13: 800 14: 800 15: 800 16: 800 bogomips: 112128
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA TU104 [GeForce RTX 2080 Rev. A] vendor: ZOTAC
driver: nvidia v: 545.29.06 alternate: nouveau,nvidia_drm non-free: 545.xx+
status: current (as of 2023-10; EOL~2026-12-xx) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-2022 pcie: gen: 3 speed: 8 GT/s
lanes: 16 ports: active: none off: DP-1, DP-2, DP-3, Unknown-2
empty: HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:1e87 class-ID: 0300
Device-2: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: Micro-Star MSI
driver: vfio-pci v: N/A alternate: nouveau,nvidia_drm,nvidia
non-free: 545.xx+ status: current (as of 2023-10; EOL~2026-12-xx)
arch: Pascal code: GP10x process: TSMC 16nm built: 2016-2021 pcie: gen: 1
speed: 2.5 GT/s lanes: 4 link-max: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 04:00.0 chip-ID: 10de:1c82 class-ID: 0300
Device-3: Adomax Nuroum C40
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1.1:4 chip-ID: 0627:a6bf
class-ID: 0102 serial: <filter>
Device-4: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 5-2:3
chip-ID: 046d:082d class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.9 with: Xwayland v: 23.2.2
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch
display-ID: :0 screens: 1
Screen-1: 0 s-res: 8320x1440 s-dpi: 92 s-size: 2297x393mm (90.43x15.47")
s-diag: 2330mm (91.75")
Monitor-1: DP-1 note: disabled pos: 2-4 model: HP 27es serial: <filter>
built: 2016 res: 1920x1080 hz: 60 dpi: 82 gamma: 1.2
size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
max: 1920x1080 min: 640x480
Monitor-2: not-matched mapped: DP-3 pos: 2-2 res: 1920x1080 hz: 60 dpi: 82
size: 598x336mm (23.54x13.23") diag: 686mm (27.01") modes: N/A
Monitor-3: not-matched mapped: DP-4 pos: primary,1-3 res: 2560x1440
dpi: 93 size: 698x392mm (27.48x15.43") diag: 801mm (31.52") modes: N/A
Monitor-4: not-matched mapped: USB-C-0 pos: 2-1 res: 1920x1080 dpi: 163
size: 300x260mm (11.81x10.24") diag: 397mm (15.63") modes: N/A
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 545.29.06
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2080/PCIe/SSE2
memory: 7.81 GiB
API: Vulkan v: 1.3.269 layers: 1 device: 0 type: discrete-gpu
name: NVIDIA GeForce RTX 2080 driver: nvidia v: 545.29.06
device-ID: 10de:1e87 surfaces: xcb,xlib
Audio:
Device-1: Intel Tiger Lake-H HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3
chip-ID: 8086:43c8 class-ID: 0403
Device-2: NVIDIA TU104 HD Audio vendor: ZOTAC driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.1
chip-ID: 10de:10f8 class-ID: 0403
Device-3: NVIDIA GP107GL High Definition Audio vendor: Micro-Star MSI
driver: vfio-pci alternate: snd_hda_intel pcie: speed: Unknown lanes: 63
link-max: gen: 6 speed: 64 GT/s bus-ID: 04:00.1 chip-ID: 10de:0fb9
class-ID: 0403
Device-4: Adomax Nuroum C40
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1.1:4 chip-ID: 0627:a6bf
class-ID: 0102 serial: <filter>
Device-5: SteelSeries ApS Arctis 7
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 1-7.4.2:12 chip-ID: 1038:12ad class-ID: 0300
Device-6: GN Netcom Jabra Engage 75 driver: jabra,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-7.4.4:14
chip-ID: 0b0e:1112 class-ID: 0300 serial: <filter>
Device-7: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 5-2:3
chip-ID: 046d:082d class-ID: 0102 serial: <filter>
API: ALSA v: k6.6.3-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Tiger Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:43f0 class-ID: 0280
IF: wlo1 state: down mac: <filter>
Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 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>
IF-ID-1: virbr0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:17 chip-ID: 8087:0026
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 5.2
lmp-v: 11 status: discoverable: no pairing: no class-ID: 7c0104
Drives:
Local Storage: total: 24.35 TiB used: 121.68 GiB (0.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
model: WDS100T2B0C-00PXH0 size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 233010WD temp: 33.9 C scheme: MBR
ID-2: /dev/nvme1n1 maj-min: 259:3 vendor: Samsung model: SSD 970 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 2B2QEXE7 temp: 42.9 C
scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: SanDisk model: SSD PLUS 1000GB
size: 931.52 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 00RL scheme: MBR
ID-4: /dev/sdb maj-min: 8:16 vendor: SanDisk model: SSD PLUS 1000GB
size: 931.52 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 00RL scheme: GPT
ID-5: /dev/sdc maj-min: 8:32 vendor: SanDisk model: SDSSDH3 512G
size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 1000 scheme: MBR
ID-6: /dev/sdd maj-min: 8:48 vendor: Silicon Power model: SPCC M.2 SSD
size: 119.24 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 1B0 scheme: GPT
ID-7: /dev/sde maj-min: 8:64 vendor: Seagate model: Expansion Desk
size: 7.28 TiB block-size: physical: 4096 B logical: 512 B type: USB
rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
fw-rev: 0915 scheme: GPT
ID-8: /dev/sdf maj-min: 8:80 vendor: ASMedia model: T ASM236X NVME
size: 119.24 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: SSD serial: <filter>
scheme: GPT
ID-9: /dev/sdg maj-min: 8:96 vendor: Samsung model: SSD 860 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
fw-rev: 0001 scheme: GPT
ID-10: /dev/sdh maj-min: 8:112 vendor: Samsung model: SSD 860 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
fw-rev: 0001 scheme: GPT
ID-11: /dev/sdk maj-min: 8:160 vendor: Samsung model: SSD 860 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
fw-rev: TB08 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-12: /dev/sdl maj-min: 8:176 vendor: Samsung model: SSD 860 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
fw-rev: TB08 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-13: /dev/sdm maj-min: 8:192 vendor: Seagate model: Expansion SW
size: 7.28 TiB block-size: physical: 4096 B logical: 512 B type: USB
rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
fw-rev: 1801 scheme: GPT
ID-14: /dev/sdn maj-min: 8:208 vendor: Seagate model: Backup+ Hub BK
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B type: USB
rev: 3.1 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
fw-rev: D781 scheme: GPT
Partition:
ID-1: / raw-size: 159.23 GiB size: 159.23 GiB (100.00%)
used: 121.65 GiB (76.4%) fs: btrfs dev: /dev/nvme1n1p5 maj-min: 259:8
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
used: 25.9 MiB (27.0%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:4
ID-3: /home raw-size: 159.23 GiB size: 159.23 GiB (100.00%)
used: 121.65 GiB (76.4%) fs: btrfs dev: /dev/nvme1n1p5 maj-min: 259:8
ID-4: /var/log raw-size: 159.23 GiB size: 159.23 GiB (100.00%)
used: 121.65 GiB (76.4%) fs: btrfs dev: /dev/nvme1n1p5 maj-min: 259:8
ID-5: /var/tmp raw-size: 159.23 GiB size: 159.23 GiB (100.00%)
used: 121.65 GiB (76.4%) fs: btrfs dev: /dev/nvme1n1p5 maj-min: 259:8
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.15 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 61.0 C mobo: N/A gpu: nvidia temp: 40 C
Fan Speeds (rpm): N/A gpu: nvidia fan: 33%
Info:
Processes: 476 Uptime: 5m wakeups: 0 Memory: total: 32 GiB note: est.
available: 31.15 GiB used: 5.06 GiB (16.2%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
Packages: pm: pacman pkgs: 1865 libs: 462
tools: gnome-software,octopi,pamac,paru Shell: fish v: 3.6.1
running-in: konsole inxi: 3.3.31
Garuda (2.6.19-2):
System install date:     2023-08-25
Last full system update: 2023-12-02
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       Probably (Run as root to verify)
Failed units:            preload.service

Check /etc/fstab and

lsblk -f

Have you removed some hard disk?
Hardware failure.

Try also a snapshot before the update.

Please provide also

systemd-analyze blame
systemd-analyze critical-chain
1 Like

No hard disk removeal prior to update other than thumbdrives in and out, but same drives attached during update and reboot.

I did a snap just before, I can go back to it and all is well.

Critical Chain:

https://termbin.com/jtuo

Blame:

https://termbin.com/8l8yy

I think we should focus on this

dev-zram0.swap @627ms +36.663s

which is really a lot.
I’ve no experience on this but maybe someone can help. Did you make any changes to the zram?
Additionally

NetworkManager-wait-online.service @38.553s +23.275s

This can be normally disabled.

1 Like

No, at least not knowlying made changes. Been running fine for a week just using VMs. If I made a change to zram, It was not a dilebrate one.

I just decided to update after a week or two, I don’t have any knowledge on zram, probably should, but still learning.

Let’s take a look:

sudo journalctl -b -u preload.service
1 Like

Dec 02 12:24:33 blackbox-I9 systemd[1]: Started Adaptive readahead daemon.
Dec 02 12:24:33 blackbox-I9 systemd[1]: preload.service: Main process exited, code=exited, status=1/FAILURE
Dec 02 12:24:33 blackbox-I9 systemd[1]: preload.service: Failed with result ‘exit-code’.

Hangs here now for quite some time:

OK OK

DK

OK

OK

OK

OK

OK

Starting Hold until boot process Starting Terminate Plymouth Boot !

1 Finished Hold until boot process

1 Finished Terminate Plymouth Boot

1 Finished Network Manager Wait Onl Reached target Network is Online.

Starting autorandr execution hook.

Starting Samba NMB Daemon…

1 Started Simple Desktop Display Mar I Finished autorandr execution hook.

Started Samba NMB Daemon.

Starting Samba SMB Daemon…

_ Started

Started Samba SMB Daemon.

1 Reached

Reached target Multi-User System.

1 Reached target Graphical Interface

It looks similar to this one: [SOLVED]Preload fails to start / Newbie Corner / Arch Linux Forums

I’m not sure, but it might be worth a shot.

sudo touch /var/lib/preload/preload.state

I can see you are not even using Plymouth because you don’t have the kernel parameters set up, so you may as well remove this package.

sudo pacman -R plymouth-git

I am guessing it is the git version installed, but if not just do sudo pacman -R plymouth.

After those changes, reboot and test again. :crossed_fingers:

Before I 0 out the preload file, will it just recreate it? Is that the thought?

I’m not sure what you mean by this.

In the linked thread, the error you have was caused by the file /var/lib/preload/preload.state not existing. It is supposed to be installed along with the application, but I guess for some reason that didn’t happen. They resolved the issue by creating the file.

touch” is a command that creates a new file. It can be used for other things too, but in this case it just makes that file if it doesn’t already exist.

Sorry. The file exists, it’s a few megabytes I think. Not at my pc atm. I figured if I touched it with that command it would create or override/ create a 0 byte file.

So I wanted to make sure before I did that on an existing file if that makes
Sense.

If you touch a file that already exists, it will update the “last modified” timestamp, but will otherwise leave the file unchanged. Your problem is something else though anyway, if you already have that file.

You could test disabling the service to see if it is slowing down your boot. It could be it is just a red herring.

Did you remove Plymouth? I almost forgot: after uninstalling Plymouth, if you’d like you can rebuild your initramfs because it does add a module in there if it is installed.

sudo dracut-rebuild

No harm to have an extra module, but it’s not needed.

I am thinking removing Plymouth will speed up your boot because it looks like there are nearly twenty seconds between mounting the disks and Plymouth quitting in the blame output:

[...]
23.275s NetworkManager-wait-online.service
23.239s plymouth-quit.service
23.230s plymouth-quit-wait.service
 4.138s dev-disk-by\x2duuid-5CBA8D51BA8D291A.device
 4.138s dev-disk-by\x2ddiskseq-2\x2dpart1.device
 4.138s dev-disk-by\x2did-wwn\x2d0x5001b444a846fcaf\x2dpart1.device
[...]
2 Likes

I did remove plymouth, but did not think about rebuilding initramfs. I will do that now and reboot to see what happens.

iniramfs rebuilt, rebooting. Fingers Crossed, I miss the instant one boot times ;-).

Small increase, but nothing real exciting ;-). Thank you for help so far though.
There is some needle in this haystack, I may just revert back the snapshot ;-(

Tried disabling preload as well, no difference really so I renabled it.

Just a shot in the dark. Maybe you could try testing a different kernel.
I’d start from the LTS

sudo pacman -S linux-lts linux-lts-headers

Then maybe also the mainline one.

2 Likes

It would be interesting to know what was updated.

Post the output from

cat /var/log/pacman.log | grep 'year-month-day' | grep -E 'installed|upgraded|removed'

(replace year-month-day with the date of the update)

1 Like