My desktop used to boot pretty quickly (well under a minute) and now it boots much slower. It’s a fairly modern system (ryzen 5600, 32 gb ram, 1 gb nvme hard drive). The problem started occurring several weeks ago, I don’t remember changing anything myself, I guess a recent update introduced the problem.
Here are the results of systemd-analyze:
Startup finished in 26.256s (firmware) + 406ms (loader) + 2.410s (kernel) + 1min 2.922s (initrd) + 3.840s (userspace) = 1min 35.835s
graphical.target reached after 3.839s in userspace.
Here’s systemd-analyze blame:
1min 3.340s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpmrm-tpmrm0.device
1min 3.340s dev-tpmrm0.device
1min 3.339s dev-ttyS3.device
1min 3.339s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
1min 3.337s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
1min 3.337s dev-ttyS1.device
1min 3.337s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
1min 3.337s dev-ttyS2.device
1min 3.329s sys-module-fuse.device
1min 3.328s sys-module-configfs.device
1min 3.310s dev-ttyS0.device
1min 3.310s sys-devices-pnp0-00:04-00:04:0-00:04:0.0-tty-ttyS0.device
1min 3.239s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-8684\x2d671A.device
1min 3.239s dev-disk-by\x2did-nvme\x2dKINGSTON_SNV2S1000G_50026B76860F445E_1\x2dpart1.device
1min 3.239s dev-disk-by\x2did-nvme\x2dKINGSTON_SNV2S1000G_50026B76860F445E\x2dpart1.device
1min 3.239s dev-nvme0n1p1.device
1min 3.239s dev-disk-by\x2did-nvme\x2deui.00000000000000000026b76860f445e5\x2dpart1.device
1min 3.239s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
1min 3.239s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
1min 3.239s dev-disk-by\x2duuid-8684\x2d671A.device
1min 3.239s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart1.device
1min 3.239s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-cc657aac\x2d0e1b\x2d46eb\x2db47d\x2d6fed2cd55b1d.device
1min 3.239s dev-disk-by\x2dpartuuid-cc657aac\x2d0e1b\x2d46eb\x2db47d\x2d6fed2cd55b1d.device
1min 3.239s dev-disk-by\x2ddiskseq-1\x2dpart1.device
1min 3.238s dev-disk-by\x2did-nvme\x2dKINGSTON_SNV2S1000G_50026B76860F445E_1\x2dpart2.device
1min 3.238s dev-nvme0n1p2.device
1min 3.238s dev-disk-by\x2dlabel-endeavouros.device
1min 3.238s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-7dae9613\x2d42bd\x2d4951\x2d99da\x2da57b4fb26b0c.device
1min 3.238s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart2.device
1min 3.238s dev-disk-by\x2did-nvme\x2deui.00000000000000000026b76860f445e5\x2dpart2.device
1min 3.238s dev-disk-by\x2duuid-7dae9613\x2d42bd\x2d4951\x2d99da\x2da57b4fb26b0c.device
1min 3.238s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-endeavouros.device
1min 3.238s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-2.device
1min 3.238s dev-disk-by\x2dpartuuid-05cadc3d\x2d56cd\x2d4f9b\x2db6af\x2d23b2786d3bd4.device
1min 3.238s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
1min 3.238s dev-disk-by\x2did-nvme\x2dKINGSTON_SNV2S1000G_50026B76860F445E\x2dpart2.device
1min 3.238s dev-disk-by\x2ddiskseq-1\x2dpart2.device
1min 3.238s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-05cadc3d\x2d56cd\x2d4f9b\x2db6af\x2d23b2786d3bd4.device
1min 3.238s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-endeavouros.device
1min 3.238s dev-disk-by\x2dpartlabel-endeavouros.device
1min 3.236s dev-disk-by\x2did-nvme\x2dKINGSTON_SNV2S1000G_50026B76860F445E.device
1min 3.236s dev-disk-by\x2ddiskseq-1.device
1min 3.236s dev-disk-by\x2did-nvme\x2dKINGSTON_SNV2S1000G_50026B76860F445E_1.device
1min 3.236s dev-disk-by\x2did-nvme\x2deui.00000000000000000026b76860f445e5.device
1min 3.236s dev-nvme0n1.device
1min 3.236s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.0-nvme-nvme0-nvme0n1.device
1min 3.236s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1.device
1.203s efi.mount
882ms NetworkManager.service
521ms initrd-switch-root.service
178ms user@1000.service
161ms ldconfig.service
117ms systemd-udev-trigger.service
94ms systemd-tmpfiles-clean.service
91ms lvm2-monitor.service
80ms systemd-boot-random-seed.service
76ms systemd-journald.service
74ms systemd-journal-flush.service
66ms upower.service
66ms power-profiles-daemon.service
66ms systemd-tmpfiles-setup.service
61ms systemd-tmpfiles-setup-dev-early.service
59ms initrd-cleanup.service
56ms systemd-timesyncd.service
53ms systemd-vconsole-setup.service
52ms systemd-remount-fs.service
49ms udisks2.service
48ms dev-mqueue.mount
47ms dev-hugepages.mount
47ms sys-kernel-debug.mount
40ms systemd-udevd.service
40ms polkit.service
40ms wpa_supplicant.service
40ms systemd-journal-catalog-update.service
36ms initrd-udevadm-cleanup-db.service
35ms systemd-hostnamed.service
34ms tmp.mount
33ms systemd-fsck@dev-disk-by\x2duuid-8684\x2d671A.service
33ms accounts-daemon.service
32ms systemd-update-utmp.service
32ms systemd-logind.service
30ms user-runtime-dir@1000.service
29ms systemd-userdbd.service
26ms dracut-cmdline.service
24ms systemd-sysusers.service
23ms sys-kernel-tracing.mount
23ms kmod-static-nodes.service
22ms dbus-broker.service
20ms modprobe@drm.service
17ms systemd-tmpfiles-setup-dev.service
16ms systemd-fsck-root.service
15ms systemd-rfkill.service
15ms systemd-modules-load.service
12ms initrd-parse-etc.service
11ms systemd-udev-load-credentials.service
11ms systemd-random-seed.service
9ms rtkit-daemon.service
8ms systemd-sysctl.service
7ms avahi-daemon.service
6ms sys-fs-fuse-connections.mount
6ms modprobe@loop.service
5ms alsa-restore.service
4ms modprobe@configfs.service
4ms systemd-update-done.service
4ms modprobe@dm_mod.service
4ms modprobe@fuse.service
4ms systemd-user-sessions.service
3ms dracut-shutdown.service
If I’m reading that correctly (which I’m probably not), it looks like the problem is caused by my hard drive taking long to mount? Any help is appreciated.