My Fedora boots so slow

Ask Fedora
,
1

Hello, I have a problem with my current… Fedora installation, and all of them (I have reinstalled it about 3 times). I also have a problem with slow boot times on every one one of them.

Maybe I will just paste two command outputs

systemd-analyze time && systemd-analyze blame 
Startup finished in 27.865s (firmware) + 2.615s (loader) + 4.137s (kernel) + 46.707s (initrd) + 10.381s (userspace) = 1min 31.707s 
graphical.target reached after 10.376s in userspace.
47.355s sys-module-fuse.device
47.231s sys-devices-pnp0-00:01-00:01:0-00:01:0.0-tty-ttyS0.device
47.231s dev-ttyS0.device
47.230s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
47.230s dev-ttyS1.device
47.228s dev-ttyS2.device
47.228s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
47.228s dev-ttyS3.device
47.228s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
47.210s sys-module-configfs.device
47.197s dev-disk-by\x2dlabel-fedora.device
47.197s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart3.device
47.197s sys-devices-pci0000:00-0000:00:06.0-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
47.197s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b4a93f689\x2dpart3.device
47.197s dev-disk-by\x2did-nvme\x2dWD_Blue_SN570_1TB_SSD_232009805328_1\x2dpart3.device
47.197s dev-nvme0n1p3.device
47.197s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-fedora.device
47.197s dev-disk-by\x2ddiskseq-1\x2dpart3.device
47.197s dev-disk-by\x2dpartuuid-bcd89ae1\x2dab6c\x2d45f1\x2d864d\x2de0f7fbe06459.device
47.197s dev-disk-by\x2duuid-02c5c893\x2d4568\x2d404f\x2d81e3\x2dceb2aade2e09.device
47.197s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-3.device
47.197s dev-disk-by\x2did-nvme\x2dWD_Blue_SN570_1TB_SSD_232009805328\x2dpart3.device
47.197s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-02c5c893\x2d4568\x2d404f\x2d8>
47.197s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-bcd89ae1\x2dab6c\x2d45f1\>
47.194s dev-disk-by\x2ddesignator-esp.device
47.194s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
47.194s dev-disk-by\x2ddiskseq-1\x2dpart1.device
47.194s dev-disk-by\x2did-nvme\x2dWD_Blue_SN570_1TB_SSD_232009805328_1\x2dpart1.device
47.194s dev-nvme0n1p1.device
47.194s dev-disk-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
47.194s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-EFI\x5cx20System\x5cx20P>
47.194s dev-disk-by\x2dpartuuid-5bd4b881\x2d3d07\x2d4f9d\x2d92ee\x2d86c1804a37ba.device
47.194s dev-disk-by\x2duuid-E0CC\x2d78F3.device
47.194s sys-devices-pci0000:00-0000:00:06.0-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
47.194s dev-disk-by\x2did-nvme\x2dWD_Blue_SN570_1TB_SSD_232009805328\x2dpart1.device
47.194s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart1.device
47.194s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-5bd4b881\x2d3d07\x2d4f9d\>
47.194s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-E0CC\x2d78F3.device
47.194s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b4a93f689\x2dpart1.device
47.182s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart2.device
47.182s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-8f53d3d1\x2ddb4c\x2d4844\>
47.182s sys-devices-pci0000:00-0000:00:06.0-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
47.182s dev-disk-by\x2ddiskseq-1\x2dpart2.device
47.182s dev-disk-by\x2dpartuuid-8f53d3d1\x2ddb4c\x2d4844\x2daa44\x2d68bf2542e11e.device
47.182s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-2.device
47.182s dev-disk-by\x2did-nvme\x2dWD_Blue_SN570_1TB_SSD_232009805328\x2dpart2.device
47.182s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-ca00bf72\x2db356\x2d4c6f\x2da>
47.182s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b4a93f689\x2dpart2.device
47.182s dev-disk-by\x2ddesignator-xbootldr.device
47.182s dev-nvme0n1p2.device
47.182s dev-disk-by\x2duuid-ca00bf72\x2db356\x2d4c6f\x2da484\x2d2e12193e86a6.device
47.182s dev-disk-by\x2did-nvme\x2dWD_Blue_SN570_1TB_SSD_232009805328_1\x2dpart2.device
47.164s dev-disk-by\x2did-nvme\x2dWD_Blue_SN570_1TB_SSD_232009805328_1.device
47.164s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1.device
47.164s dev-nvme0n1.device
47.164s dev-disk-by\x2did-nvme\x2dWD_Blue_SN570_1TB_SSD_232009805328.device
47.164s dev-disk-by\x2ddiskseq-1.device
47.164s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b4a93f689.device
47.164s sys-devices-pci0000:00-0000:00:06.0-0000:02:00.0-nvme-nvme0-nvme0n1.device
 6.475s NetworkManager-wait-online.service
 2.105s dnf-makecache.service
  960ms initrd-switch-root.service
  495ms akmods.service
  484ms NetworkManager.service
  457ms firewalld.service
  299ms tuned.service
  133ms systemd-udev-trigger.service
  129ms user@1000.service
  123ms tuned-ppd.service
  114ms abrtd.service
   92ms systemd-tmpfiles-clean.service
   84ms upower.service
   82ms var-lib-nfs-rpc_pipefs.mount
   75ms systemd-tmpfiles-setup.service
   74ms systemd-journal-flush.service
   71ms dev-zram0.swap
   67ms dracut-pre-pivot.service
   65ms udisks2.service
   63ms dracut-pre-udev.service
   62ms systemd-tmpfiles-setup-dev-early.service
   61ms systemd-vconsole-setup.service
   57ms plymouth-start.service
   55ms systemd-journald.service
   54ms systemd-hostnamed.service
   53ms lvm2-monitor.service
   50ms polkit.service
   50ms systemd-udevd.service
   49ms systemd-fsck@dev-disk-by\x2duuid-ca00bf72\x2db356\x2d4c6f\x2da484\x2d2e12193e86a6.service
   49ms initrd-cleanup.service
   48ms chronyd.service
   46ms ModemManager.service
   42ms systemd-fsck@dev-disk-by\x2duuid-E0CC\x2d78F3.service
   41ms plymouth-switch-root.service
   39ms systemd-resolved.service
   38ms rsyslog.service
   36ms dracut-cmdline.service
   35ms accounts-daemon.service
   34ms systemd-tmpfiles-setup-dev.service
   32ms systemd-logind.service
   32ms dbus-broker.service
   31ms smartd.service
   30ms avahi-daemon.service
   28ms systemd-zram-setup@zram0.service
   28ms plymouth-quit-wait.service
   28ms user-runtime-dir@1000.service
   28ms plymouth-quit.service
   27ms authselect-apply-changes.service
   24ms plymouth-read-write.service
   23ms initrd-parse-etc.service
   22ms systemd-sysctl.service
   22ms initrd-udevadm-cleanup-db.service
   21ms gssproxy.service
   21ms rpc-statd-notify.service
   20ms bluetooth.service
   20ms systemd-random-seed.service
   19ms systemd-fsck-root.service
   19ms wpa_supplicant.service
   19ms sys-kernel-debug.mount
   19ms dev-hugepages.mount
   19ms switcheroo-control.service
   19ms sys-kernel-tracing.mount
   19ms dev-mqueue.mount
   18ms kmod-static-nodes.service
   18ms cups.service
   17ms systemd-userdb-load-credentials.service
   17ms systemd-user-sessions.service
   17ms thermald.service
   17ms boot-efi.mount
   16ms audit-rules.service
   16ms systemd-userdbd.service
   16ms uresourced.service
   15ms dracut-shutdown.service
   15ms foomaticrip-upgrade.service
   14ms systemd-rfkill.service
   14ms rtkit-daemon.service
   13ms auditd.service
   13ms systemd-udev-load-credentials.service
   11ms systemd-network-generator.service
   11ms boot.mount
   10ms sys-fs-fuse-connections.mount
    9ms modprobe@loop.service
    9ms systemd-modules-load.service
    8ms systemd-remount-fs.service
    6ms systemd-update-utmp.service
    4ms systemd-sysusers.service
    4ms home.mount
    2ms tmp.mount
    2ms sshd-unix-local.socket
    1ms systemd-coredump.socket
  915us systemd-bootctl.socket
  835us systemd-creds.socket
  684us systemd-sysext.socket
  597us systemd-ask-password.socket
  557us systemd-factory-reset.socket
  487us lvm2-lvmpolld.socket
  456us systemd-udevd-control.socket
  436us cups.socket
  318us avahi-daemon.socket
  307us pcscd.socket
  270us dbus.socket
  222us systemd-userdbd.socket
  182us iscsid.socket
  151us dm-event.socket
  119us systemd-resolved-monitor.socket
   94us systemd-hostnamed.socket
   94us sssd-kcm.socket
   90us systemd-udevd-varlink.socket
   68us systemd-logind-varlink.socket
   63us systemd-journald-audit.socket
   41us systemd-journald-dev-log.socket
   33us systemd-resolved-varlink.socket
   30us systemd-rfkill.socket
   23us iscsiuio.socket
   21us systemd-journald.socket
    7us systemd-udevd-kernel.socket

I have asked AI about it, and it told me its serial8250 & systemd-udevd fault (they wont close, and they’re having a 45 seconds timeout to wait), but I don’t know how to fix it.

2

What does systemd-analyze critical-chain report.

If the AI is right then look for logs about the serieal8250n in the system jourtnal.

FYI: I add the pre-formatted text mark up to your pastes to preserve spacing.
It’s the </> button.

1 Like
3

Oh sorry, my fault

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 @10.376s
└─sddm.service @10.376s
  └─plymouth-quit.service @10.344s +28ms
    └─systemd-user-sessions.service @10.320s +17ms
      └─remote-fs.target @10.311s
        └─remote-fs-pre.target @3.882s
          └─nfs-client.target @3.880s
            └─gssproxy.service @3.858s +21ms
              └─network.target @3.855s
                └─wpa_supplicant.service @3.835s +19ms
                  └─basic.target @2.817s
                    └─dbus-broker.service @2.770s +32ms
                      └─dbus.socket @2.765s +270us
                        └─sysinit.target @2.763s
                          └─systemd-resolved.service @2.723s +39ms
                            └─systemd-tmpfiles-setup.service @2.645s +75ms
                              └─local-fs.target @2.642s
                                └─boot-efi.mount @2.624s +17ms
                                  └─boot.mount @2.611s +11ms
                                    └─systemd-fsck@dev-disk-by\x2duuid-ca00bf72\x2db356\x2d4c6f\x2da484\x2d2e>
                                      └─dev-disk-by\x2duuid-ca00bf72\x2db356\x2d4c6f\x2da484\x2d2e12193e86a6.>
lines 1-24/24 (END)
4

That took 10s to reach the graphical target.

I guess that it’s the slow initrd that is your concern?

What did you find in the system journal?

5

what do you mean? you mean journalctl?

6

Can you also show the outputs of lsblk -f and cat /etc/fstab ?

7 
NAME        FSTYPE FSVER LABEL  UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                                 
└─sda1      exfat  1.0          00E7-8685                               3,4T     5% /run/media/dean/00E7-8685
zram0       swap   1     zram0  55020fad-a261-43fa-926c-db7b069cd1ff                [SWAP]
nvme0n1                                                                             
├─nvme0n1p1 vfat   FAT32        E0CC-78F3                             579,5M     3% /boot/efi
├─nvme0n1p2 ext4   1.0          ca00bf72-b356-4c6f-a484-2e12193e86a6    1,2G    32% /boot
└─nvme0n1p3 btrfs        fedora 02c5c893-4568-404f-81e3-ceb2aade2e09  846,6G     9% /home
                                                                                    /

#
# /etc/fstab
# Created by anaconda on Mon Mar 30 23:59:47 2026
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to update systemd
# units generated from this file.
#
UUID=02c5c893-4568-404f-81e3-ceb2aade2e09 / btrfs subvol=root,compress=zstd:1 0 0
UUID=ca00bf72-b356-4c6f-a484-2e12193e86a6 /boot ext4 defaults 1 2
UUID=E0CC-78F3 /boot/efi vfat umask=0077,shortname=winnt 0 2
UUID=02c5c893-4568-404f-81e3-ceb2aade2e09 /home btrfs subvol=home,compress=zstd:1 0 0
8

The last 2 lines are truncated, ending with > (because your terminal window was not wide enough), so you may be missing a large delay. If you can’t make the terminal window wider, run systemd-analyze critical-chain |cat to get wrapped lines.

Some systems take a long time before they start booting an OS, I assume doing some hardware checks.

9

Or send the output to a file, like: systemd-analyze critical-chain > ~/chain.txt. Then it’s easy to look at the file in a text editor and paste it from there.

10

Thanks, nothing suspicious in there.

12

Okay, I have found what was wrong. I had two empty SATA cables plugged in, which caused the issue.

dean@fedora:~$ systemd-analyze time
Startup finished in 23.862s (firmware) + 2.623s (loader) + 4.113s (kernel) + 1.959s (initrd) + 14.279s (userspace) = 46.839s 
graphical.target reached after 14.276s in userspace.
dean@fedora:~$

now its perfect

2 Likes
13

They will have been acting as radio aerials picking up electrical interferences and feeding that into the sata receiver. Unterminated wires are great at doing that.

1 Like