Very slow boot on Fedora 43 - seeking advice

Hello everyone,

I’m hoping to get some guidance on an unusually slow boot on my Fedora system. I’ve gathered some information below and would appreciate any insights or suggestions.

Fedora Version and Kernel:
Fedora release 43
Kernel: 6.18.12-200.fc43.x86_64

Hardware:

  • CPU: AMD Ryzen 5 9600X
  • 1T HDD
  • Boot drive : 2T NVMe SSD Samsung 990 PRO
NAME        ROTA   SIZE TYPE MOUNTPOINT
sda            0 931.5G disk 
└─sda1         0 931.5G part /media/Data
zram0          0     8G disk [SWAP]
nvme0n1        0   1.8T disk 
├─nvme0n1p1    0   600M part /boot/efi
├─nvme0n1p2    0     1G part /boot
└─nvme0n1p3    0   1.8T part /home

Boot time summary:
Startup finished in 26.211s (firmware) + 1.879s (loader) + 1.871s (kernel) + 46.614s (initrd) + 4.759s (userspace) = 1min 21.336s
graphical.target reached after 4.759s in userspace.

Systemd-analyze plot:
Link to a high res jpg (you’ll have to right click → open in a new tab for it to be readable) : https://i.postimg.cc/z5hZF8L3/bootchart.png
And to the actual svg : https://www.svgviewer.dev/s/uT3Pmawy

47.362s sys-module-fuse.device
47.316s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.0\x2dpart1.device
47.316s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2\x2dpart1.device
47.316s dev-sda1.device
47.316s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.0\x2dpart-by\x2dpartuuid-a4213683\x2dff0a\x2d4cac\>
47.316s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.0\x2dpart-by\x2duuid-39ce8639\x2dd6cf\x2d4a19\x2d8>
47.316s dev-disk-by\x2did-ata\x2dSamsung_SSD_860_EVO_1TB_S3Z9NB0M729640T\x2dpart1.device
47.316s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.0\x2dpart-by\x2dpartnum-1.device
47.316s dev-disk-by\x2dpartuuid-a4213683\x2dff0a\x2d4cac\x2d97a2\x2d4c0793113293.device
47.316s dev-disk-by\x2did-wwn\x2d0x5002538e4978958c\x2dpart1.device
47.316s dev-disk-by\x2duuid-39ce8639\x2dd6cf\x2d4a19\x2d81ae\x2dcf3aaee4a335.device
47.316s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.0\x2dpart-by\x2dlabel-Data.device
47.316s dev-disk-by\x2ddiskseq-1\x2dpart1.device
47.316s dev-disk-by\x2dlabel-Data.device
47.316s sys-devices-pci0000:00-0000:00:02.1-0000:05:00.0-0000:06:0d.0-0000:0a:00.0-ata2-host1-target1:0:0-1:0:>
47.306s dev-disk-by\x2ddiskseq-1.device
47.306s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.device
47.306s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.0.device
47.306s dev-disk-by\x2did-ata\x2dSamsung_SSD_860_EVO_1TB_S3Z9NB0M729640T.device
47.306s dev-disk-by\x2did-wwn\x2d0x5002538e4978958c.device
47.306s sys-devices-pci0000:00-0000:00:02.1-0000:05:00.0-0000:06:0d.0-0000:0a:00.0-ata2-host1-target1:0:0-1:0:>
47.306s dev-sda.device
47.292s dev-tpm0.device
47.292s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpm-tpm0.device
47.282s dev-ttyS2.device
47.282s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
47.282s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
47.282s dev-ttyS3.device
47.279s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
47.279s dev-ttyS1.device
47.278s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpmrm-tpmrm0.device
47.278s dev-tpmrm0.device
47.275s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
47.275s dev-ttyS0.device
47.263s sys-module-configfs.device
47.236s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7HGNJ0Y206322X\x2dpart3.device
47.236s dev-disk-by\x2dlabel-fedora.device
47.236s dev-disk-by\x2dpartuuid-0430d9c7\x2d59e8\x2d4b8a\x2d8154\x2d18aa74d357f8.device
47.236s dev-nvme0n1p3.device
47.236s dev-disk-by\x2did-nvme\x2deui.0025384251428c58\x2dpart3.device
47.236s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-3.device
47.236s dev-disk-by\x2ddiskseq-2\x2dpart3.device
47.236s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart3.device
47.236s dev-disk-by\x2duuid-0da5b969\x2dc8e9\x2d4d8d\x2da1f7\x2d7129efc9b6a1.device
47.236s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-0430d9c7\x2d59e8\x2d4b8a\x>
47.236s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-0da5b969\x2dc8e9\x2d4d8d\x2da1>
47.236s sys-devices-pci0000:00-0000:00:01.2-0000:04:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
47.236s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7HGNJ0Y206322X_1\x2dpart3.device
47.236s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-fedora.device
47.228s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-f91d942c\x2d59b9\x2d492d\x2d99>
47.227s dev-disk-by\x2did-nvme\x2deui.0025384251428c58\x2dpart2.device
47.227s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-57f6b0c9\x2dbb59\x2d4144\x>
47.227s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-2.device
47.227s dev-disk-by\x2dpartuuid-57f6b0c9\x2dbb59\x2d4144\x2d8616\x2d30887cf19c3a.device
47.227s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart2.device
47.227s dev-disk-by\x2ddiskseq-2\x2dpart2.device
47.227s dev-disk-by\x2ddesignator-xbootldr.device
47.227s sys-devices-pci0000:00-0000:00:01.2-0000:04:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
47.227s dev-nvme0n1p2.device
47.227s dev-disk-by\x2duuid-f91d942c\x2d59b9\x2d492d\x2d99bb\x2d3a2301ae5504.device
47.227s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7HGNJ0Y206322X\x2dpart2.device
47.227s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7HGNJ0Y206322X_1\x2dpart2.device
47.226s dev-disk-by\x2duuid-0E88\x2d527C.device
47.226s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-0E88\x2d527C.device
47.226s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
47.226s dev-disk-by\x2did-nvme\x2deui.0025384251428c58\x2dpart1.device
47.226s dev-disk-by\x2ddiskseq-2\x2dpart1.device
47.226s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart1.device
47.226s dev-disk-by\x2dpartuuid-f13e53c8\x2d0938\x2d45c0\x2db734\x2def25791ff7b9.device
47.226s dev-disk-by\x2ddesignator-esp.device
47.226s dev-nvme0n1p1.device
47.226s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-EFI\x5cx20System\x5cx20Pa>
47.226s dev-disk-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
47.226s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7HGNJ0Y206322X\x2dpart1.device
47.226s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7HGNJ0Y206322X_1\x2dpart1.device
47.226s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-f13e53c8\x2d0938\x2d45c0\x>
47.226s sys-devices-pci0000:00-0000:00:01.2-0000:04:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
47.223s dev-disk-by\x2did-nvme\x2deui.0025384251428c58.device
47.223s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1.device
47.223s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7HGNJ0Y206322X_1.device
47.223s dev-disk-by\x2ddiskseq-2.device
47.223s dev-nvme0n1.device
47.223s sys-devices-pci0000:00-0000:00:01.2-0000:04:00.0-nvme-nvme0-nvme0n1.device
47.223s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7HGNJ0Y206322X.device
 1.088s dkms.service
  981ms systemd-binfmt.service
  937ms systemd-oomd.service
  927ms systemd-resolved.service
  867ms initrd-switch-root.service
  528ms docker.service
  359ms firewalld.service
  335ms dnf-makecache.service
  251ms NetworkManager.service
  240ms nfs-server.service
  139ms proc-fs-nfsd.mount
  132ms upower.service
  130ms abrtd.service
  112ms user@1000.service
  111ms accounts-daemon.service
  106ms tuned.service
  100ms media-server-data.mount
   98ms systemd-udev-trigger.service
   85ms tuned-ppd.service
   81ms systemd-journal-flush.service
   81ms udisks2.service
   79ms lvm2-monitor.service
   79ms polkit.service
   78ms containerd.service
   73ms systemd-tmpfiles-setup-dev-early.service
   68ms chronyd.service
   63ms systemd-journald.service
   58ms packagekit.service
   57ms systemd-tmpfiles-setup.service
   53ms ModemManager.service
   51ms systemd-random-seed.service
   49ms systemd-sysctl.service
   49ms systemd-logind.service
   44ms systemd-tmpfiles-clean.service
   44ms plymouth-start.service
   42ms dev-zram0.swap
   38ms nfs-mountd.service
   38ms systemd-udevd.service
   37ms systemd-rfkill.service
   36ms smartd.service
   34ms media-Data.mount
   34ms switcheroo-control.service
   33ms rtkit-daemon.service
   33ms rpc-statd.service
   32ms systemd-fsck@dev-disk-by\x2duuid-39ce8639\x2dd6cf\x2d4a19\x2d81ae\x2dcf3aaee4a335.service
   30ms gssproxy.service
   28ms sssd-kcm.service
   28ms avahi-daemon.service
   27ms cups.service
   27ms systemd-hostnamed.service
   26ms systemd-vconsole-setup.service
   25ms boot.mount
   24ms plymouth-quit-wait.service
   23ms systemd-tmpfiles-setup-dev.service
   23ms virtqemud.service
   23ms rpcbind.service
   23ms plymouth-quit.service
   22ms systemd-fsck@dev-disk-by\x2duuid-0E88\x2d527C.service
   22ms auditd.service
   21ms proc-sys-fs-binfmt_misc.mount
   21ms systemd-fsck@dev-disk-by\x2duuid-f91d942c\x2d59b9\x2d492d\x2d99bb\x2d3a2301ae5504.service
   20ms media-server-jelly.mount
   19ms dracut-shutdown.service
   18ms foomaticrip-upgrade.service
   17ms var-lib-nfs-rpc_pipefs.mount
   17ms systemd-fsck-root.service
   17ms systemd-homed.service
   17ms dbus-broker.service
   17ms home.mount
   16ms plymouth-switch-root.service
   16ms initrd-udevadm-cleanup-db.service
   14ms rsyslog.service
   14ms dracut-cmdline.service
   13ms systemd-zram-setup@zram0.service
   13ms docker.socket
   13ms flatpak-system-helper.service
   12ms plymouth-read-write.service
   11ms boot-efi.mount
   11ms user-runtime-dir@1000.service
   11ms systemd-machined.service
   10ms systemd-user-sessions.service
   10ms systemd-userdbd.service
    9ms dev-hugepages.mount
    8ms dev-mqueue.mount
    8ms audit-rules.service
    8ms systemd-udev-load-credentials.service
    8ms sys-kernel-debug.mount
    8ms sys-kernel-tracing.mount
    7ms dracut-pre-udev.service
    7ms kmod-static-nodes.service
    7ms systemd-modules-load.service
    7ms uresourced.service
    7ms rpc-statd-notify.service
    6ms sys-fs-fuse-connections.mount
    6ms dracut-pre-pivot.service
    6ms modprobe@loop.service
    5ms initrd-cleanup.service
    5ms systemd-userdb-load-credentials.service
    4ms systemd-remount-fs.service
    4ms nfsdcld.service
    3ms systemd-update-utmp.service
    3ms nfs-idmapd.service
    3ms systemd-sysusers.service
    2ms rpcbind.socket
    2ms tmp.mount
    2ms initrd-parse-etc.service
    1ms sshd-unix-local.socket
    1ms systemd-coredump.socket
  725us systemd-journald-audit.socket
  697us lvm2-lvmpolld.socket
  597us systemd-udevd-control.socket
  540us systemd-ask-password.socket
  451us systemd-factory-reset.socket
  405us systemd-bootctl.socket
  322us systemd-creds.socket
  304us systemd-sysext.socket
  288us cups.socket
  280us pcscd.socket
  264us systemd-userdbd.socket
  229us avahi-daemon.socket
  175us systemd-importd.socket
  144us dbus.socket
  110us dm-event.socket
   98us systemd-machined.socket
   94us systemd-resolved-monitor.socket
   91us systemd-hostnamed.socket
   89us systemd-oomd.socket
   84us virtinterfaced.socket
   75us sssd-kcm.socket
   69us virtlockd-admin.socket
   69us iscsid.socket
   66us systemd-logind-varlink.socket
   64us virtlockd.socket
   62us systemd-udevd-varlink.socket
   58us virtqemud.socket
   56us virtnetworkd.socket
   55us virtnwfilterd.socket
   50us virtstoraged.socket
   50us virtsecretd.socket
   48us virtnodedevd.socket
   42us virtproxyd.socket
   37us systemd-homed-activate.service
   30us virtlogd.socket
   28us virtproxyd-admin.socket
   27us systemd-journald-dev-log.socket
   26us virtproxyd-ro.socket
   26us systemd-resolved-varlink.socket
   24us iscsiuio.socket
   23us virtlogd-admin.socket
   23us virtnwfilterd-admin.socket
   22us virtinterfaced-admin.socket
   22us virtnetworkd-admin.socket
   22us virtsecretd-admin.socket
   21us virtinterfaced-ro.socket
   21us virtstoraged-ro.socket
   20us virtqemud-admin.socket
   20us virtstoraged-admin.socket
   20us virtnodedevd-admin.socket
   20us virtnetworkd-ro.socket
   19us systemd-rfkill.socket
   19us virtnodedevd-ro.socket
   19us virtqemud-ro.socket
   19us virtnwfilterd-ro.socket
   19us virtsecretd-ro.socket
   12us systemd-journald.socket
    4us systemd-udevd-kernel.socket

Critical chain:

graphical.target 4.759s  
└─multi-user.target 4.759s  
  └─docker.service 4.242s +516ms  
    └─containerd.service 4.160s +80ms  
      └─network.target 4.159s  
        └─NetworkManager.service 3.950s +208ms  
          └─network-pre.target 3.949s  
            └─firewalld.service 2.935s +398ms  
              └─polkit.service 2.868s +64ms  
                └─basic.target 2.856s  
                  └─dbus-broker.service 2.830s +14ms  
                    └─dbus.socket 2.815s +140us  
                      └─sysinit.target 2.813s  
                        └─systemd-resolved.service 1.881s +932ms  
                          └─systemd-tmpfiles-setup.service 1.805s +58ms  
                            └─local-fs.target 1.803s  
                              └─boot-efi.mount 1.791s +11ms  
                                └─boot.mount 1.770s +19ms  
                                  └─systemd-fsck dev-disk-by-uuid-f91d942c-59b9-492d-99bb-3a2301ae5504.service

On my first search, I ended up in a rabbit hole about Samsung 990 Pro issues. It lead me to update my SSD firmware and add this kernel parameter : nvme_core.default_ps_max_latency_us=0

After reasearching on the forum, I also tried to add : systemd.tpm2_wait=false

I haven’t seen any major improvement from these, so i’m turning to you for guidance.

Thank you in advance for your time and help.

Can’t view the hi-res image you post to imgur, as it’s region blocked (I’m in the UK)

However, from the chain (preformatted </> text would have preserved the formatting) your boot process slows down as soon as you get to the firewall/networking aspect. Do you really need networking to be up before getting to the login manager?

If not, sudo systemctl disable NetworkManager-wait-online.service

If this causes you problems, you can reverse the change with enable.

Thank you for your answer, I’ve edited my post and provided a new link to the bootchart, hopefully this one will work : https://i.postimg.cc/z5hZF8L3/bootchart.png
I’ll try you proposition right away. Thank you again
Edit : Unfortunately, this didn’t solve the main 45s second issue

That image is too small to be readable.

You might try posting the .svg text file that is produced by systemd-analyze instead of the image and our browsers will be able to display the image.

I have the same model of SSD and do not have this option.
Unless you see a noticable speed up I recommend you remove it.

It looks good on my end, but I have to right click → open in a new link:
Otherwise he is the same info from systemd-analyze blame

47.362s sys-module-fuse.device
47.316s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.0\x2dpart1.device
47.316s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2\x2dpart1.device
47.316s dev-sda1.device
47.316s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.0\x2dpart-by\x2dpartuuid-a4213683\x2dff0a\x2d4cac\>
47.316s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.0\x2dpart-by\x2duuid-39ce8639\x2dd6cf\x2d4a19\x2d8>
47.316s dev-disk-by\x2did-ata\x2dSamsung_SSD_860_EVO_1TB_S3Z9NB0M729640T\x2dpart1.device
47.316s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.0\x2dpart-by\x2dpartnum-1.device
47.316s dev-disk-by\x2dpartuuid-a4213683\x2dff0a\x2d4cac\x2d97a2\x2d4c0793113293.device
47.316s dev-disk-by\x2did-wwn\x2d0x5002538e4978958c\x2dpart1.device
47.316s dev-disk-by\x2duuid-39ce8639\x2dd6cf\x2d4a19\x2d81ae\x2dcf3aaee4a335.device
47.316s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.0\x2dpart-by\x2dlabel-Data.device
47.316s dev-disk-by\x2ddiskseq-1\x2dpart1.device
47.316s dev-disk-by\x2dlabel-Data.device
47.316s sys-devices-pci0000:00-0000:00:02.1-0000:05:00.0-0000:06:0d.0-0000:0a:00.0-ata2-host1-target1:0:0-1:0:>
47.306s dev-disk-by\x2ddiskseq-1.device
47.306s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.device
47.306s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.0.device
47.306s dev-disk-by\x2did-ata\x2dSamsung_SSD_860_EVO_1TB_S3Z9NB0M729640T.device
47.306s dev-disk-by\x2did-wwn\x2d0x5002538e4978958c.device
47.306s sys-devices-pci0000:00-0000:00:02.1-0000:05:00.0-0000:06:0d.0-0000:0a:00.0-ata2-host1-target1:0:0-1:0:>
47.306s dev-sda.device
47.292s dev-tpm0.device
47.292s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpm-tpm0.device
47.282s dev-ttyS2.device
47.282s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
47.282s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
47.282s dev-ttyS3.device
47.279s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
47.279s dev-ttyS1.device
47.278s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpmrm-tpmrm0.device
47.278s dev-tpmrm0.device
47.275s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
47.275s dev-ttyS0.device
47.263s sys-module-configfs.device
47.236s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7HGNJ0Y206322X\x2dpart3.device
47.236s dev-disk-by\x2dlabel-fedora.device
47.236s dev-disk-by\x2dpartuuid-0430d9c7\x2d59e8\x2d4b8a\x2d8154\x2d18aa74d357f8.device
47.236s dev-nvme0n1p3.device
47.236s dev-disk-by\x2did-nvme\x2deui.0025384251428c58\x2dpart3.device
47.236s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-3.device
47.236s dev-disk-by\x2ddiskseq-2\x2dpart3.device
47.236s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart3.device
47.236s dev-disk-by\x2duuid-0da5b969\x2dc8e9\x2d4d8d\x2da1f7\x2d7129efc9b6a1.device
47.236s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-0430d9c7\x2d59e8\x2d4b8a\x>
47.236s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-0da5b969\x2dc8e9\x2d4d8d\x2da1>
47.236s sys-devices-pci0000:00-0000:00:01.2-0000:04:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
47.236s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7HGNJ0Y206322X_1\x2dpart3.device
47.236s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-fedora.device
47.228s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-f91d942c\x2d59b9\x2d492d\x2d99>
47.227s dev-disk-by\x2did-nvme\x2deui.0025384251428c58\x2dpart2.device
47.227s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-57f6b0c9\x2dbb59\x2d4144\x>
47.227s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-2.device
47.227s dev-disk-by\x2dpartuuid-57f6b0c9\x2dbb59\x2d4144\x2d8616\x2d30887cf19c3a.device
47.227s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart2.device
47.227s dev-disk-by\x2ddiskseq-2\x2dpart2.device
47.227s dev-disk-by\x2ddesignator-xbootldr.device
47.227s sys-devices-pci0000:00-0000:00:01.2-0000:04:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
47.227s dev-nvme0n1p2.device
47.227s dev-disk-by\x2duuid-f91d942c\x2d59b9\x2d492d\x2d99bb\x2d3a2301ae5504.device
47.227s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7HGNJ0Y206322X\x2dpart2.device
47.227s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7HGNJ0Y206322X_1\x2dpart2.device
47.226s dev-disk-by\x2duuid-0E88\x2d527C.device
47.226s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-0E88\x2d527C.device
47.226s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
47.226s dev-disk-by\x2did-nvme\x2deui.0025384251428c58\x2dpart1.device
47.226s dev-disk-by\x2ddiskseq-2\x2dpart1.device
47.226s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart1.device
47.226s dev-disk-by\x2dpartuuid-f13e53c8\x2d0938\x2d45c0\x2db734\x2def25791ff7b9.device
47.226s dev-disk-by\x2ddesignator-esp.device
47.226s dev-nvme0n1p1.device
47.226s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-EFI\x5cx20System\x5cx20Pa>
47.226s dev-disk-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
47.226s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7HGNJ0Y206322X\x2dpart1.device
47.226s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7HGNJ0Y206322X_1\x2dpart1.device
47.226s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-f13e53c8\x2d0938\x2d45c0\x>
47.226s sys-devices-pci0000:00-0000:00:01.2-0000:04:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
47.223s dev-disk-by\x2did-nvme\x2deui.0025384251428c58.device
47.223s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1.device
47.223s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7HGNJ0Y206322X_1.device
47.223s dev-disk-by\x2ddiskseq-2.device
47.223s dev-nvme0n1.device
47.223s sys-devices-pci0000:00-0000:00:01.2-0000:04:00.0-nvme-nvme0-nvme0n1.device
47.223s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7HGNJ0Y206322X.device
 1.088s dkms.service
  981ms systemd-binfmt.service
  937ms systemd-oomd.service
  927ms systemd-resolved.service
  867ms initrd-switch-root.service
  528ms docker.service
  359ms firewalld.service
  335ms dnf-makecache.service
  251ms NetworkManager.service
  240ms nfs-server.service
  139ms proc-fs-nfsd.mount
  132ms upower.service
  130ms abrtd.service
  112ms user@1000.service
  111ms accounts-daemon.service
  106ms tuned.service
  100ms media-server-data.mount
   98ms systemd-udev-trigger.service
   85ms tuned-ppd.service
   81ms systemd-journal-flush.service
   81ms udisks2.service
   79ms lvm2-monitor.service
   79ms polkit.service
   78ms containerd.service
   73ms systemd-tmpfiles-setup-dev-early.service
   68ms chronyd.service
   63ms systemd-journald.service
   58ms packagekit.service
   57ms systemd-tmpfiles-setup.service
   53ms ModemManager.service
   51ms systemd-random-seed.service
   49ms systemd-sysctl.service
   49ms systemd-logind.service
   44ms systemd-tmpfiles-clean.service
   44ms plymouth-start.service
   42ms dev-zram0.swap
   38ms nfs-mountd.service
   38ms systemd-udevd.service
   37ms systemd-rfkill.service
   36ms smartd.service
   34ms media-Data.mount
   34ms switcheroo-control.service
   33ms rtkit-daemon.service
   33ms rpc-statd.service
   32ms systemd-fsck@dev-disk-by\x2duuid-39ce8639\x2dd6cf\x2d4a19\x2d81ae\x2dcf3aaee4a335.service
   30ms gssproxy.service
   28ms sssd-kcm.service
   28ms avahi-daemon.service
   27ms cups.service
   27ms systemd-hostnamed.service
   26ms systemd-vconsole-setup.service
   25ms boot.mount
   24ms plymouth-quit-wait.service
   23ms systemd-tmpfiles-setup-dev.service
   23ms virtqemud.service
   23ms rpcbind.service
   23ms plymouth-quit.service
   22ms systemd-fsck@dev-disk-by\x2duuid-0E88\x2d527C.service
   22ms auditd.service
   21ms proc-sys-fs-binfmt_misc.mount
   21ms systemd-fsck@dev-disk-by\x2duuid-f91d942c\x2d59b9\x2d492d\x2d99bb\x2d3a2301ae5504.service
   20ms media-server-jelly.mount
   19ms dracut-shutdown.service
   18ms foomaticrip-upgrade.service
   17ms var-lib-nfs-rpc_pipefs.mount
   17ms systemd-fsck-root.service
   17ms systemd-homed.service
   17ms dbus-broker.service
   17ms home.mount
   16ms plymouth-switch-root.service
   16ms initrd-udevadm-cleanup-db.service
   14ms rsyslog.service
   14ms dracut-cmdline.service
   13ms systemd-zram-setup@zram0.service
   13ms docker.socket
   13ms flatpak-system-helper.service
   12ms plymouth-read-write.service
   11ms boot-efi.mount
   11ms user-runtime-dir@1000.service
   11ms systemd-machined.service
   10ms systemd-user-sessions.service
   10ms systemd-userdbd.service
    9ms dev-hugepages.mount
    8ms dev-mqueue.mount
    8ms audit-rules.service
    8ms systemd-udev-load-credentials.service
    8ms sys-kernel-debug.mount
    8ms sys-kernel-tracing.mount
    7ms dracut-pre-udev.service
    7ms kmod-static-nodes.service
    7ms systemd-modules-load.service
    7ms uresourced.service
    7ms rpc-statd-notify.service
    6ms sys-fs-fuse-connections.mount
    6ms dracut-pre-pivot.service
    6ms modprobe@loop.service
    5ms initrd-cleanup.service
    5ms systemd-userdb-load-credentials.service
    4ms systemd-remount-fs.service
    4ms nfsdcld.service
    3ms systemd-update-utmp.service
    3ms nfs-idmapd.service
    3ms systemd-sysusers.service
    2ms rpcbind.socket
    2ms tmp.mount
    2ms initrd-parse-etc.service
    1ms sshd-unix-local.socket
    1ms systemd-coredump.socket
  725us systemd-journald-audit.socket
  697us lvm2-lvmpolld.socket
  597us systemd-udevd-control.socket
  540us systemd-ask-password.socket
  451us systemd-factory-reset.socket
  405us systemd-bootctl.socket
  322us systemd-creds.socket
  304us systemd-sysext.socket
  288us cups.socket
  280us pcscd.socket
  264us systemd-userdbd.socket
  229us avahi-daemon.socket
  175us systemd-importd.socket
  144us dbus.socket
  110us dm-event.socket
   98us systemd-machined.socket
   94us systemd-resolved-monitor.socket
   91us systemd-hostnamed.socket
   89us systemd-oomd.socket
   84us virtinterfaced.socket
   75us sssd-kcm.socket
   69us virtlockd-admin.socket
   69us iscsid.socket
   66us systemd-logind-varlink.socket
   64us virtlockd.socket
   62us systemd-udevd-varlink.socket
   58us virtqemud.socket
   56us virtnetworkd.socket
   55us virtnwfilterd.socket
   50us virtstoraged.socket
   50us virtsecretd.socket
   48us virtnodedevd.socket
   42us virtproxyd.socket
   37us systemd-homed-activate.service
   30us virtlogd.socket
   28us virtproxyd-admin.socket
   27us systemd-journald-dev-log.socket
   26us virtproxyd-ro.socket
   26us systemd-resolved-varlink.socket
   24us iscsiuio.socket
   23us virtlogd-admin.socket
   23us virtnwfilterd-admin.socket
   22us virtinterfaced-admin.socket
   22us virtnetworkd-admin.socket
   22us virtsecretd-admin.socket
   21us virtinterfaced-ro.socket
   21us virtstoraged-ro.socket
   20us virtqemud-admin.socket
   20us virtstoraged-admin.socket
   20us virtnodedevd-admin.socket
   20us virtnetworkd-ro.socket
   19us systemd-rfkill.socket
   19us virtnodedevd-ro.socket
   19us virtqemud-ro.socket
   19us virtnwfilterd-ro.socket
   19us virtsecretd-ro.socket
   12us systemd-journald.socket
    4us systemd-udevd-kernel.socket

The svg file is produced with `systemd-analyze plot > <filename>.svg and it produces a text .svg file that can be opened by the browser (and is scaled by the browser window size).

Where do you upload an svg ? Most image uploader convert it to jpg.
The only I could find is this one, but the interface is terrible : https://www.svgviewer.dev/s/uT3Pmawy
There is a download link at the bottom-right.
Thank you for yoir patience.

I have a like-980 (PM9A1) and use that option seemingly no problems

Did it start booting slow after an update somewhere, or did it always take about that long since Fedora install?

I’m not sure what controls the disk loading speed, but my dev-disk stuff seemingly happens in 1-2s (way less than 40s)

systemd-analyze
Startup finished in 3.859s (firmware) + 555ms (loader) + 330ms (kernel) + 1.378s (initrd) + 2.457s (userspace) = 8.581s 
graphical.target reached after 2.422s in userspace.

1.415s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
1.415s dev-ttyS0.device
1.408s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
1.408s dev-ttyS2.device
1.407s dev-ttyS1.device
1.407s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
1.405s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
1.405s dev-ttyS3.device
1.404s sys-module-configfs.device
1.190s dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB_______S65VNE0NC59225_1.device
1.190s sys-devices-pci0000:00-0000:00:1d.0-0000:01:00.0-nvme-nvme0-nvme0n1.device
1.190s dev-disk-by\x2ddiskseq-1.device
1.190s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1.device
1.190s dev-disk-by\x2did-nvme\x2deui.363556304ec592250025384500000001.device
1.190s dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB__S65VNE0NC59225.device
1.190s dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB_______S65VNE0NC59225.device
1.190s dev-nvme0n1.device
1.184s dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB_______S65VNE0NC59225_1\x2dpart2.device
1.184s dev-disk-by\x2ddiskseq-1\x2dpart2.device
1.184s dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB__S65VNE0NC59225\x2dpart2.device
1.184s dev-disk-by\x2did-nvme\x2deui.363556304ec592250025384500000001\x2dpart2.device
1.184s dev-disk-by\x2duuid-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.device
1.184s dev-nvme0n1p2.device
1.184s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart2.device
1.184s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-2.device
1.184s dev-disk-by\x2dpartuuid-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.device
1.184s dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB_______S65VNE0NC59225\x2dpart2.device
1.184s sys-devices-pci0000:00-0000:00:1d.0-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
1.184s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.device
1.184s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.device
1.162s dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB__S65VNE0NC59225\x2dpart3.device
1.162s dev-nvme0n1p3.device
1.162s dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB_______S65VNE0NC59225_1\x2dpart3.device
1.162s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart3.device
1.162s dev-disk-by\x2dpartuuid-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.device
1.162s dev-disk-by\x2did-nvme\x2deui.363556304ec592250025384500000001\x2dpart3.device
1.162s dev-disk-by\x2ddiskseq-1\x2dpart3.device
1.162s sys-devices-pci0000:00-0000:00:1d.0-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
1.162s dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB_______S65VNE0NC59225\x2dpart3.device
1.162s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-3.device
1.162s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.device
1.162s dev-disk-by\x2duuid-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.device
1.162s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.device
1.156s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-0E1E\x2d2EDC.device
1.156s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart1.device
1.156s sys-devices-pci0000:00-0000:00:1d.0-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
1.156s dev-disk-by\x2duuid-0E1E\x2d2EDC.device
1.156s dev-disk-by\x2ddiskseq-1\x2dpart1.device
1.156s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.device
1.156s dev-disk-by\x2did-nvme\x2deui.363556304ec592250025384500000001\x2dpart1.device
1.156s dev-nvme0n1p1.device
1.156s dev-disk-by\x2dpartuuid-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.device
1.156s dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB_______S65VNE0NC59225\x2dpart1.device
1.156s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
1.156s dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB__S65VNE0NC59225\x2dpart1.device
1.156s dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB_______S65VNE0NC59225_1\x2dpart1.device
1.055s instsvcdrv.service
 920ms dracut-initqueue.service
 519ms display-manager-legacy.service
 317ms postfix.service
 251ms NetworkManager.service
 233ms initrd-switch-root.service
 213ms firewalld.service
 117ms upower.service
 110ms wtmpdb-update-boot.service
  83ms polkit.service
  78ms user@XXXX.service
  76ms chronyd.service
  66ms systemd-logind.service
  59ms lm_sensors.service
  58ms cups.service
  57ms systemd-udevd.service
  57ms systemd-udev-trigger.service
  49ms smartd.service
  46ms avahi-daemon.service
  45ms systemd-vconsole-setup.service
  45ms wtmpdbd.service
  44ms soft-reboot-cleanup.service
  43ms sound-extra.service
  42ms systemd-journald.service
  40ms systemd-backlight@backlight:intel_backlight.service
  40ms auditd.service
  38ms kbdsettings.service
  36ms ModemManager.service
  35ms dev-disk-by\x2duuid-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.swap
  35ms colord.service
  35ms systemd-fsck@dev-disk-by\x2duuid-0E1E\x2d2EDC.service
  33ms systemd-tmpfiles-setup.service
  31ms udisks2.service
  31ms systemd-hostnamed.service
  30ms lvm2-monitor.service
  30ms mcelog.service
  29ms dracut-cmdline.service
  28ms rtkit-daemon.service
  26ms dev-hugepages.mount
  25ms dev-mqueue.mount
  25ms accounts-daemon.service
  25ms sys-kernel-debug.mount
  25ms sys-kernel-tracing.mount
  23ms blk-availability.service
  21ms systemd-fsck-root.service
  20ms dbus-broker.service
  19ms alsa-restore.service
  19ms kmod-static-nodes.service
  19ms dracut-pre-udev.service
  18ms dracut-shutdown.service
  17ms boot-efi.mount
  17ms systemd-tmpfiles-setup-dev-early.service
  17ms modprobe@drm.service
  17ms audit-rules.service
  17ms systemd-binfmt.service
  17ms initrd-parse-etc.service
  15ms modprobe@fuse.service
  15ms systemd-remount-fs.service
  13ms user-runtime-dir@XXXX.service
  13ms modprobe@nvme_fabrics.service
  12ms systemd-modules-load.service
  11ms systemd-udev-load-credentials.service
  10ms initrd-udevadm-cleanup-db.service
  10ms systemd-tmpfiles-setup-dev.service
   9ms systemd-random-seed.service
   9ms initrd-cleanup.service
   9ms tmp.mount
   9ms modprobe@configfs.service
   9ms systemd-user-sessions.service
   7ms systemd-journal-flush.service
   7ms modprobe@dm_mod.service
   7ms modprobe@efi_pstore.service
   6ms systemd-sysctl.service
   5ms modprobe@loop.service
   5ms kernel-sysctl.service
   5ms proc-sys-fs-binfmt_misc.mount
   4ms sys-fs-fuse-connections.mount

An svg is just a text file. Any pastebin will be fine.

Steve

1 Like

It might not hurt to also post the logs..
uptime -s
to get the boot time
Then use the boot time to get the first 1 minute or so of the logs.
journalctl --no-hostname --no-pager -l -b0 --since=14:46:00 --until=14:47:00
The above is an example from my machine ..

Thanks

Edit:
This will also work
journalctl --no-pager --no-hostname -b0 -U "$(date -d "$(uptime -s) 1 minutes" +'%Y-%m-%d %H:%M:%S')"

Did you sevice compile a driver?
Is that the slow down cause?