Slow boot times in Fedora Kinote?

I don’t have a reference of what should be a fast boot time on any OS with an SSD because I never had an SSD until this new computer, but I was curious if my boot time was slow or not on this system: GIGABYTE B650M GAMING PLUS WIFI motherboard, AMD Ryzen 5 8400F CPU and a SSD Kingston NV3, 1TB, M.2 NVMe, 2280, PCIe 4.0, Read 6000MBs and Write 4000MBs.

I did a systemd-analyze and these are the results:

Startup finished in 14.034s (firmware) + 3.266s (loader) + 4.213s (kernel) + 21.387s (initrd) + 9.933s (userspace) = 52.835s 
graphical.target reached after 4.514s in userspace.

From what I can gather around the internet, boot times on SSDs should not be this slow: https://www.reddit.com/r/linuxmasterrace/comments/tyl5it/what_are_your_boot_times/

I also asked ChatGPT and it told me it should be 15-25s

systemd analyze blame gives me these results

22.108s sys-module-fuse.device
21.949s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
21.949s dev-ttyS2.device
21.949s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
21.949s dev-ttyS3.device
21.949s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpmrm-tpmrm0.device
21.948s dev-tpmrm0.device
21.948s dev-ttyS1.device
21.948s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
21.946s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
21.946s dev-ttyS0.device
21.943s dev-tpm0.device
21.943s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpm-tpm0.device
21.926s sys-module-configfs.device
21.818s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-8DB5\x2d1EE3.device
21.818s sys-devices-pci0000:00-0000:00:01.2-0000:04:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
21.818s dev-disk-by\x2did-nvme\x2dKINGSTON_SNV3S1000G_50026B768724EAC1_1\x2dpart1.device
21.818s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
21.818s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-EFI\x5cx20System\x5cx20P>
21.818s dev-disk-by\x2ddiskseq-1\x2dpart1.device
21.818s dev-disk-by\x2duuid-8DB5\x2d1EE3.device
21.818s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart1.device
21.818s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-5bc21399\x2d8bf4\x2d41a8\>
21.818s dev-disk-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
21.818s dev-nvme0n1p1.device
21.818s dev-disk-by\x2did-nvme\x2dKINGSTON_SNV3S1000G_50026B768724EAC1\x2dpart1.device
21.818s dev-disk-by\x2dpartuuid-5bc21399\x2d8bf4\x2d41a8\x2d80aa\x2d204332ffc56c.device
21.818s dev-disk-by\x2did-nvme\x2deui.00000000000000000026b768724eac15\x2dpart1.device
21.809s dev-disk-by\x2duuid-8cf5a2b5\x2d53e8\x2d495f\x2d8812\x2d208becd93011.device
21.809s dev-disk-by\x2dpartuuid-1bbbc012\x2d5dc7\x2d4d08\x2d9e60\x2d8d2bb4eeddfb.device
21.809s dev-disk-by\x2did-nvme\x2deui.00000000000000000026b768724eac15\x2dpart2.device
21.809s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-8cf5a2b5\x2d53e8\x2d495f\x2d8>
21.809s dev-disk-by\x2ddiskseq-1\x2dpart2.device
21.809s dev-disk-by\x2did-nvme\x2dKINGSTON_SNV3S1000G_50026B768724EAC1\x2dpart2.device
21.809s dev-disk-by\x2did-nvme\x2dKINGSTON_SNV3S1000G_50026B768724EAC1_1\x2dpart2.device
21.809s sys-devices-pci0000:00-0000:00:01.2-0000:04:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
21.809s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart2.device
21.809s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-2.device
21.809s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-1bbbc012\x2d5dc7\x2d4d08\>
21.809s dev-nvme0n1p2.device
21.807s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1.device
21.807s sys-devices-pci0000:00-0000:00:01.2-0000:04:00.0-nvme-nvme0-nvme0n1.device
21.807s dev-disk-by\x2ddiskseq-1.device
21.807s dev-disk-by\x2did-nvme\x2dKINGSTON_SNV3S1000G_50026B768724EAC1.device
21.807s dev-disk-by\x2did-nvme\x2deui.00000000000000000026b768724eac15.device
21.807s dev-nvme0n1.device
21.807s dev-disk-by\x2did-nvme\x2dKINGSTON_SNV3S1000G_50026B768724EAC1_1.device
21.798s dev-nvme0n1p3.device
21.798s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart3.device
21.798s dev-disk-by\x2ddiskseq-1\x2dpart3.device
21.798s sys-devices-pci0000:00-0000:00:01.2-0000:04:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
21.798s dev-disk-by\x2duuid-5c42b6fd\x2de261\x2d4959\x2d91d5\x2d0e8438223c39.device
21.798s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-3.device
21.798s dev-disk-by\x2dpartuuid-1117723e\x2d2516\x2d48cd\x2d9d4a\x2dec64acf6ba5b.device
21.798s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-1117723e\x2d2516\x2d48cd\>
21.798s dev-disk-by\x2did-nvme\x2deui.00000000000000000026b768724eac15\x2dpart3.device
21.798s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-5c42b6fd\x2de261\x2d4959\x2d9>
21.798s dev-disk-by\x2did-nvme\x2dKINGSTON_SNV3S1000G_50026B768724EAC1\x2dpart3.device
21.798s dev-disk-by\x2did-nvme\x2dKINGSTON_SNV3S1000G_50026B768724EAC1_1\x2dpart3.device
20.359s dracut-initqueue.service
20.194s systemd-cryptsetup@luks\x2d5c42b6fd\x2de261\x2d4959\x2d91d5\x2d0e8438223c39.service
 5.781s NetworkManager-wait-online.service
  974ms systemd-binfmt.service
  904ms initrd-switch-root.service
  849ms systemd-oomd.service
  836ms systemd-resolved.service
  830ms firewalld.service
  435ms NetworkManager.service
  269ms tuned.service
  145ms systemd-udev-trigger.service
  137ms bootloader-update.service
  131ms systemd-tmpfiles-setup.service
  128ms upower.service
  113ms systemd-tmpfiles-setup-dev-early.service
  112ms user@1000.service
  101ms systemd-udevd.service
   98ms udisks2.service
   91ms systemd-hostnamed.service
   87ms systemd-tmpfiles-clean.service
   84ms tuned-ppd.service
   83ms ModemManager.service
   77ms var-lib-nfs-rpc_pipefs.mount
   66ms systemd-nsresourced.service
   66ms polkit.service
   66ms accounts-daemon.service
   62ms systemd-journald.service
   61ms dev-zram0.swap
   55ms plymouth-switch-root.service
   54ms dbus-broker.service
   52ms systemd-logind.service
   51ms dracut-cmdline.service
   51ms chronyd.service
   50ms bluetooth.service
   45ms systemd-tmpfiles-setup-dev.service
   43ms systemd-journal-flush.service
   42ms dracut-pre-udev.service
   41ms dracut-pre-trigger.service
   36ms dev-hugepages.mount
   36ms avahi-daemon.service
   36ms lvm2-monitor.service
   35ms dev-mqueue.mount
   35ms dracut-pre-mount.service
   35ms sys-kernel-debug.mount
   34ms sys-kernel-tracing.mount
   34ms auditd.service
   32ms systemd-zram-setup@zram0.service
   31ms initrd-parse-etc.service
   29ms uresourced.service
   29ms boot-efi.mount
   28ms systemd-rfkill.service
   28ms user-runtime-dir@1000.service
   27ms switcheroo-control.service
   26ms alsa-restore.service
   25ms systemd-fsck@dev-disk-by\x2duuid-8DB5\x2d1EE3.service
   25ms proc-sys-fs-binfmt_misc.mount
   25ms plymouth-quit-wait.service
   25ms plymouth-quit.service
   25ms systemd-user-sessions.service
   24ms gssproxy.service
   24ms systemd-fsck@dev-disk-by\x2duuid-8cf5a2b5\x2d53e8\x2d495f\x2d8812\x2d208becd93011.service
   24ms plymouth-read-write.service
   24ms smartd.service
   23ms systemd-vconsole-setup.service
   21ms wpa_supplicant.service
   20ms cups.service
   20ms systemd-update-utmp-runlevel.service
   19ms boot.mount
   19ms audit-rules.service
   18ms systemd-userdbd.service
   17ms systemd-homed.service
   17ms modprobe@configfs.service
   17ms modprobe@fuse.service
   16ms plymouth-start.service
   16ms rpc-statd-notify.service
   16ms rtkit-daemon.service
   16ms kmod-static-nodes.service
   15ms dracut-pre-pivot.service
   14ms modprobe@dm_mod.service
   14ms modprobe@efi_pstore.service
   14ms modprobe@drm.service
   14ms systemd-fsck-root.service
   13ms modprobe@loop.service
   13ms tmp.mount
   13ms dracut-shutdown.service
   12ms systemd-random-seed.service
   12ms thermald.service
   11ms systemd-sysctl.service
   11ms dracut-mount.service
   11ms systemd-udev-load-credentials.service
   10ms initrd-cleanup.service
    9ms systemd-modules-load.service
    9ms systemd-network-generator.service
    8ms initrd-udevadm-cleanup-db.service
    7ms systemd-update-utmp.service
    5ms systemd-remount-fs.service
    4ms systemd-sysusers.service
    4ms ostree-remount.service
    4ms var-home.mount
    3ms var.mount
    2ms sys-fs-fuse-connections.mount
   42us systemd-homed-activate.service

I don’t really know where to even start improving these boot times, or if that’s even possible on this hardware. Considering this is my first time getting a SSD after using a HDD since forever I also wasn’t accustomed to this much speed (because yes, even with apparently slow boot times, I find this system very fast still). Can anyone give me pointers as to what to try doing to improve this? I appreciate any answers and thanks for your time!

A lot of people started counting from grub, you started counting from power button, I guess. Those times can be improved but need to be? Maybe enter LUKS password faster? :smiley:

My 6 yo ThinkPad has systemd-analyze:

Startup finished in 7.594s (firmware) + 5.279s (loader) + 2.038s (kernel) + 9.082s (initrd) + 17.458s (userspace) = 41.454s 
graphical.target reached after 12.022s in userspace.

Yeah that’s how it works, from power button to Plasma password in under a minute.

Edit: Turned off, and turned it on again:

Startup finished in 7.650s (firmware) + 5.400s (loader) + 2.024s (kernel) + 7.757s (initrd) + 13.247s (userspace) = 36.080s 
graphical.target reached after 9.406s in userspace.

My measurement was 40 secs.

I guess I improved my LUKS typing skills a bit :stuck_out_tongue:

1 Like

Ah, I guess systemd-analyze starts counting as soon as the system boots up, instead of the bootloader. Makes sense when I typed my LUKS password faster the command returned a lower number.

1 Like