Booting takes a lot of time (slow boot)

Hi,

since a while (I don’t no exactly when or if I have changed something) booting takes a lot of time.

I used systemd-analyze plot > boottime.svg to create this file:
boottime.svg

But I am far away to be an linux expert and I am not able to interpret the data. Can you give me a hint what the problem of the long booting could be?

I use Fedora Linux 40 (Workstation Edition) - Kernel Version: Linux 6.8.7-300.fc40.x86_64. And I use GRUB bootloader because there is also a Windows installation somewhere if this information is helpful.

Thanks a lot for your time. :slight_smile:

What is the output of systemd-analyze critical-chain?

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 @7.526s
└─multi-user.target @7.526s
  └─plymouth-quit-wait.service @5.568s +1.956s
    └─systemd-user-sessions.service @5.558s +7ms
      └─remote-fs.target @5.542s
        └─remote-fs-pre.target @2.634s
          └─nfs-client.target @2.634s
            └─gssproxy.service @2.598s +35ms
              └─network.target @2.585s
                └─wpa_supplicant.service @7.009s +9ms
                  └─basic.target @2.051s
                    └─dbus-broker.service @2.030s +19ms
                      └─dbus.socket @2.013s
                        └─sysinit.target @2.010s
                          └─systemd-resolved.service @1.944s +65ms
                            └─systemd-tmpfiles-setup.service @1.832s +95ms
                              └─import-state.service @1.811s +20ms
                                └─local-fs.target @1.808s
                                  └─boot-efi.mount @1.796s +11ms
                                    └─boot.mount @1.177s +34ms

I installed version 40 this morning and I was surprised with faster boot times. I did not measure it, nor did I do that with version 39 but it seems to be faster. I did compare your list with mine and every line is a few tenths of a second slower than what is written in your list.
No idea what score you had in 39, but all in all it is not bad now.

1 Like

Can you post the output of systemd-analyze blame here?

1 Like

Thanks. That does not show a slow boot time as your SVG seems to show.

Can you post the output of all three commands for the same boot please?

systemd-analyze
systemd-analyze blame
systemd-analyze critical-chain
3 Likes
stephan@fedora:~$ systemd-analyze
Startup finished in 23.061s (firmware) + 5.879s (loader) + 4.188s (kernel) + 1min 2.426s (initrd) + 10.565s (userspace) = 1min 46.122s 
graphical.target reached after 10.536s in userspace.

stephan@fedora:~$ systemd-analyze blame
1min 2.944s sys-module-fuse.device
1min 2.908s dev-sda1.device
1min 2.908s dev-disk-by\x2did-wwn\x2d0x5002538e406c0a5d\x2dpart1.device
1min 2.908s dev-disk-by\x2dpartuuid-a0aeac59\x2dae6f\x2d41c5\x2d81f4\x2d42d5ea8b25bc.device
1min 2.908s dev-disk-by\x2dpath-pci\x2d0000:02:00.1\x2data\x2d3.0\x2dpart1.device
1min 2.908s dev-disk-by\x2did-ata\x2dSamsung_SSD_860_EVO_1TB_S3Z9NB0K836346X\x2dpart1.device
1min 2.908s dev-disk-by\x2dlabel-HDD2\x5cx20Games.device
1min 2.908s dev-disk-by\x2duuid-F67F\x2d06A2.device
1min 2.908s dev-disk-by\x2dpath-pci\x2d0000:02:00.1\x2data\x2d3\x2dpart1.device
1min 2.908s dev-disk-by\x2ddiskseq-1\x2dpart1.device
1min 2.908s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.1-ata3-host2-target2:0:0-2:0:0:0-block-sda-sda1.device
1min 2.863s dev-disk-by\x2did-ata\x2dSamsung_SSD_860_EVO_1TB_S3Z9NB0K836346X.device
1min 2.863s dev-sda.device
1min 2.863s dev-disk-by\x2dpath-pci\x2d0000:02:00.1\x2data\x2d3.0.device
1min 2.863s dev-disk-by\x2dpath-pci\x2d0000:02:00.1\x2data\x2d3.device
1min 2.863s dev-disk-by\x2did-wwn\x2d0x5002538e406c0a5d.device
1min 2.863s dev-disk-by\x2ddiskseq-1.device
1min 2.863s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.1-ata3-host2-target2:0:0-2:0:0:0-block-sda.device
1min 2.848s dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
1min 2.834s dev-ttyS13.device
1min 2.834s sys-devices-platform-serial8250-serial8250:0-serial8250:0.13-tty-ttyS13.device
1min 2.829s sys-devices-platform-serial8250-serial8250:0-serial8250:0.12-tty-ttyS12.device
1min 2.829s dev-ttyS12.device
1min 2.828s sys-devices-platform-serial8250-serial8250:0-serial8250:0.11-tty-ttyS11.device
1min 2.828s dev-ttyS11.device
1min 2.825s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
1min 2.825s dev-ttyS1.device
1min 2.822s sys-devices-platform-serial8250-serial8250:0-serial8250:0.14-tty-ttyS14.device
1min 2.822s dev-ttyS14.device
1min 2.822s dev-ttyS10.device
1min 2.822s sys-devices-platform-serial8250-serial8250:0-serial8250:0.10-tty-ttyS10.device
1min 2.822s sys-devices-platform-serial8250-serial8250:0-serial8250:0.16-tty-ttyS16.device
1min 2.822s dev-ttyS16.device
1min 2.822s sys-devices-platform-serial8250-serial8250:0-serial8250:0.15-tty-ttyS15.device
1min 2.822s dev-ttyS15.device
1min 2.819s dev-ttyS19.device
1min 2.819s sys-devices-platform-serial8250-serial8250:0-serial8250:0.19-tty-ttyS19.device
1min 2.818s dev-ttyS18.device
1min 2.818s sys-devices-platform-serial8250-serial8250:0-serial8250:0.18-tty-ttyS18.device
1min 2.818s dev-ttyS23.device
1min 2.818s sys-devices-platform-serial8250-serial8250:0-serial8250:0.23-tty-ttyS23.device
1min 2.818s dev-ttyS17.device
1min 2.818s sys-devices-platform-serial8250-serial8250:0-serial8250:0.17-tty-ttyS17.device
1min 2.818s sys-devices-platform-serial8250-serial8250:0-serial8250:0.21-tty-ttyS21.device
1min 2.818s dev-ttyS21.device
1min 2.817s sys-devices-platform-serial8250-serial8250:0-serial8250:0.5-tty-ttyS5.device
1min 2.817s dev-ttyS5.device
1min 2.817s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
1min 2.817s dev-ttyS2.device
1min 2.816s sys-module-configfs.device
1min 2.816s dev-ttyS20.device
1min 2.816s sys-devices-platform-serial8250-serial8250:0-serial8250:0.20-tty-ttyS20.device
1min 2.816s dev-ttyS22.device
1min 2.816s sys-devices-platform-serial8250-serial8250:0-serial8250:0.22-tty-ttyS22.device
1min 2.815s dev-ttyS24.device
1min 2.815s sys-devices-platform-serial8250-serial8250:0-serial8250:0.24-tty-ttyS24.device
1min 2.813s dev-ttyS27.device
1min 2.813s sys-devices-platform-serial8250-serial8250:0-serial8250:0.27-tty-ttyS27.device
1min 2.813s sys-devices-platform-serial8250-serial8250:0-serial8250:0.28-tty-ttyS28.device
1min 2.813s dev-ttyS28.device
1min 2.812s dev-ttyS31.device
1min 2.812s sys-devices-platform-serial8250-serial8250:0-serial8250:0.31-tty-ttyS31.device
1min 2.812s dev-ttyS26.device
1min 2.812s sys-devices-platform-serial8250-serial8250:0-serial8250:0.26-tty-ttyS26.device
1min 2.812s sys-devices-platform-serial8250-serial8250:0-serial8250:0.8-tty-ttyS8.device
1min 2.812s dev-ttyS8.device
1min 2.812s sys-devices-platform-serial8250-serial8250:0-serial8250:0.25-tty-ttyS25.device
1min 2.812s dev-ttyS25.device
1min 2.811s dev-ttyS3.device
1min 2.811s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
1min 2.810s dev-ttyS30.device
1min 2.810s sys-devices-platform-serial8250-serial8250:0-serial8250:0.30-tty-ttyS30.device
1min 2.809s dev-ttyS4.device
1min 2.809s sys-devices-platform-serial8250-serial8250:0-serial8250:0.4-tty-ttyS4.device
1min 2.808s dev-ttyS29.device
1min 2.808s sys-devices-platform-serial8250-serial8250:0-serial8250:0.29-tty-ttyS29.device
1min 2.807s dev-ttyS6.device
1min 2.807s sys-devices-platform-serial8250-serial8250:0-serial8250:0.6-tty-ttyS6.device
1min 2.807s sys-devices-platform-serial8250-serial8250:0-serial8250:0.7-tty-ttyS7.device
1min 2.807s dev-ttyS7.device
1min 2.804s dev-ttyS9.device
1min 2.804s sys-devices-platform-serial8250-serial8250:0-serial8250:0.9-tty-ttyS9.device
1min 2.794s sys-devices-pnp0-00:04-00:04:0-00:04:0.0-tty-ttyS0.device
1min 2.794s dev-ttyS0.device
1min 2.774s dev-disk-by\x2ddiskseq-3\x2dpart1.device
1min 2.774s dev-disk-by\x2dpartuuid-378a66ee\x2da53f\x2d4a3c\x2da39d\x2de9a1005ba363.device
1min 2.774s dev-disk-by\x2dpath-pci\x2d0000:05:00.0\x2dnvme\x2d1\x2dpart1.device
1min 2.774s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.2-0000:03:04.0-0000:05:00.0-nvme-nvme1-nvme1n1-nvme1n1p1.device
1min 2.774s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b4763bfe7\x2dpart1.device
1min 2.774s dev-nvme1n1p1.device
1min 2.774s dev-disk-by\x2duuid-3412093D12090618.device
1min 2.774s dev-disk-by\x2did-nvme\x2dWD_Blue_SN580_1TB_24036S801925\x2dpart1.device
1min 2.774s dev-disk-by\x2did-nvme\x2dWD_Blue_SN580_1TB_24036S801925_1\x2dpart1.device
1min 2.768s dev-disk-by\x2ddiskseq-3.device
1min 2.768s dev-disk-by\x2dpath-pci\x2d0000:05:00.0\x2dnvme\x2d1.device
1min 2.768s dev-disk-by\x2did-nvme\x2dWD_Blue_SN580_1TB_24036S801925_1.device
1min 2.768s dev-nvme1n1.device
1min 2.768s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.2-0000:03:04.0-0000:05:00.0-nvme-nvme1-nvme1n1.device
1min 2.768s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b4763bfe7.device
1min 2.768s dev-disk-by\x2did-nvme\x2dWD_Blue_SN580_1TB_24036S801925.device
1min 2.759s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p6.device
1min 2.759s dev-nvme0n1p6.device
1min 2.759s dev-disk-by\x2duuid-9da0c55c\x2d1be3\x2d4fce\x2da799\x2d414e41e83b5f.device
1min 2.759s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b4a4dcde3\x2dpart6.device
1min 2.759s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart6.device
1min 2.759s dev-disk-by\x2did-nvme\x2dWD_Blue_SN570_1TB_231516806772_1\x2dpart6.device
1min 2.759s dev-disk-by\x2dlabel-fedora.device
1min 2.759s dev-disk-by\x2did-nvme\x2dWD_Blue_SN570_1TB_231516806772\x2dpart6.device
1min 2.759s dev-disk-by\x2dpartuuid-f6455735\x2d8e79\x2d406c\x2d8cf8\x2d048ecdc721d5.device
1min 2.759s dev-disk-by\x2ddiskseq-2\x2dpart6.device
1min 2.759s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart3.device
1min 2.759s dev-disk-by\x2dpartuuid-8676350c\x2d9e52\x2d4cc6\x2db62a\x2d7e1678f35304.device
1min 2.759s dev-disk-by\x2did-nvme\x2dWD_Blue_SN570_1TB_231516806772\x2dpart3.device
1min 2.759s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
1min 2.759s dev-disk-by\x2duuid-892ab8f7\x2d9235\x2d465f\x2d97b3\x2dfde80358e0ce.device
1min 2.759s dev-disk-by\x2ddiskseq-2\x2dpart3.device
1min 2.759s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b4a4dcde3\x2dpart3.device
1min 2.759s dev-disk-by\x2did-nvme\x2dWD_Blue_SN570_1TB_231516806772_1\x2dpart3.device
1min 2.759s dev-nvme0n1p3.device
1min 2.758s dev-nvme0n1p5.device
1min 2.758s dev-disk-by\x2duuid-b13cb210\x2d8543\x2d4424\x2d8954\x2d6f2d083bdd10.device
1min 2.758s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart5.device
1min 2.758s dev-disk-by\x2did-nvme\x2dWD_Blue_SN570_1TB_231516806772\x2dpart5.device
1min 2.758s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b4a4dcde3\x2dpart5.device
1min 2.758s dev-disk-by\x2dpartuuid-11ef16e5\x2d31ec\x2d4854\x2d928c\x2d6a25c1b43f53.device
1min 2.758s dev-disk-by\x2did-nvme\x2dWD_Blue_SN570_1TB_231516806772_1\x2dpart5.device
1min 2.758s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p5.device
1min 2.758s dev-disk-by\x2ddiskseq-2\x2dpart5.device
1min 2.756s dev-disk-by\x2did-nvme\x2dWD_Blue_SN570_1TB_231516806772\x2dpart1.device
1min 2.756s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b4a4dcde3\x2dpart1.device
1min 2.756s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
1min 2.756s dev-disk-by\x2duuid-786E\x2dC2DF.device
1min 2.756s dev-nvme0n1p1.device
1min 2.756s dev-disk-by\x2did-nvme\x2dWD_Blue_SN570_1TB_231516806772_1\x2dpart1.device
1min 2.756s dev-disk-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
1min 2.756s dev-disk-by\x2dpartuuid-8d59bc87\x2d84c0\x2d4fec\x2d8e54\x2dec321c0b0963.device
1min 2.756s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart1.device
1min 2.756s dev-disk-by\x2ddiskseq-2\x2dpart1.device
1min 2.755s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart4.device
1min 2.755s dev-disk-by\x2did-nvme\x2dWD_Blue_SN570_1TB_231516806772_1\x2dpart4.device
1min 2.755s dev-disk-by\x2did-nvme\x2dWD_Blue_SN570_1TB_231516806772\x2dpart4.device
1min 2.755s dev-nvme0n1p4.device
1min 2.755s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b4a4dcde3\x2dpart4.device
1min 2.755s dev-disk-by\x2dpartuuid-70603cac\x2d2378\x2d41e4\x2daa40\x2dacd747a711af.device
1min 2.755s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p4.device
1min 2.755s dev-disk-by\x2duuid-A29EECF09EECBE43.device
1min 2.755s dev-disk-by\x2ddiskseq-2\x2dpart4.device
1min 2.741s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
1min 2.741s dev-disk-by\x2did-nvme\x2dWD_Blue_SN570_1TB_231516806772\x2dpart2.device
1min 2.741s dev-nvme0n1p2.device
1min 2.741s dev-disk-by\x2ddiskseq-2\x2dpart2.device
1min 2.741s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart2.device
1min 2.741s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b4a4dcde3\x2dpart2.device
1min 2.741s dev-disk-by\x2did-nvme\x2dWD_Blue_SN570_1TB_231516806772_1\x2dpart2.device
1min 2.741s dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device
1min 2.741s dev-disk-by\x2dpartuuid-d376a687\x2d6407\x2d405c\x2da224\x2d1fcc156c14b5.device
1min 2.737s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.0-nvme-nvme0-nvme0n1.device
1min 2.737s dev-nvme0n1.device
1min 2.737s dev-disk-by\x2did-nvme\x2dWD_Blue_SN570_1TB_231516806772.device
1min 2.737s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1.device
1min 2.737s dev-disk-by\x2ddiskseq-2.device
1min 2.737s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b448b4a4dcde3.device
1min 2.737s dev-disk-by\x2did-nvme\x2dWD_Blue_SN570_1TB_231516806772_1.device
1min 2.724s sys-subsystem-net-devices-enp7s0.device
1min 2.724s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.2-0000:03:09.0-0000:07:00.0-net-enp7s0.device
1min 1.463s dracut-initqueue.service
     5.991s NetworkManager-wait-online.service
     1.915s plymouth-quit-wait.service
     1.048s abrtd.service
      857ms initrd-switch-root.service
      435ms fwupd.service
      255ms mullvad-early-boot-blocking.service
      228ms dkms.service
      219ms NetworkManager.service
      212ms systemd-journal-flush.service
      204ms packagekit.service
      185ms firewalld.service
      178ms systemd-udev-trigger.service
      156ms user@1000.service
      140ms udisks2.service
      122ms systemd-tmpfiles-setup-dev-early.service
      115ms upower.service
       96ms systemd-tmpfiles-setup.service
       89ms cups.service
       84ms power-profiles-daemon.service
       83ms polkit.service
       82ms accounts-daemon.service
       70ms chronyd.service
       65ms systemd-resolved.service
       64ms systemd-logind.service
       62ms systemd-fsck@dev-disk-by\x2duuid-786E\x2dC2DF.service
       61ms logrotate.service
       61ms lvm2-monitor.service
       55ms var-lib-nfs-rpc_pipefs.mount
       54ms systemd-journald.service
       53ms unbound-anchor.service
       53ms systemd-oomd.service
       52ms systemd-sysctl.service
       52ms systemd-vconsole-setup.service
       52ms mnt-892ab8f7\x2d9235\x2d465f\x2d97b3\x2dfde80358e0ce.mount
       50ms ModemManager.service
       49ms passim.service
       46ms bluetooth.service
       46ms systemd-udevd.service
       45ms systemd-random-seed.service
       44ms flatpak-system-helper.service
       41ms systemd-fsck@dev-disk-by\x2duuid-b13cb210\x2d8543\x2d4424\x2d8954\x2d6f2d083bdd10.service
       38ms dracut-cmdline.service
       38ms switcheroo-control.service
       36ms lm_sensors.service
       35ms plymouth-switch-root.service
       34ms avahi-daemon.service
       31ms sssd-kcm.service
       31ms dev-zram0.swap
       30ms colord.service
       29ms systemd-tmpfiles-setup-dev.service
       29ms dracut-pre-pivot.service
       28ms systemd-zram-setup@zram0.service
       26ms systemd-homed.service
       26ms virtqemud.service
       25ms gssproxy.service
       23ms dracut-shutdown.service
       20ms systemd-userdbd.service
       20ms import-state.service
       19ms rtkit-daemon.service
       19ms dbus-broker.service
       18ms systemd-binfmt.service
       18ms plymouth-start.service
       17ms tmp.mount
       17ms audit-rules.service
       16ms systemd-machined.service
       15ms plymouth-read-write.service
       14ms dev-hugepages.mount
       14ms dracut-pre-udev.service
       14ms dev-mqueue.mount
       14ms thermald.service
       13ms home.mount
       13ms boot-efi.mount
       13ms sys-kernel-debug.mount
       12ms uresourced.service
       12ms sys-kernel-tracing.mount
       12ms auditd.service
       12ms kmod-static-nodes.service
       11ms gdm.service
       10ms initrd-parse-etc.service
       10ms modprobe@configfs.service
        9ms systemd-fsck-root.service
        9ms systemd-remount-fs.service
        9ms initrd-cleanup.service
        8ms boot.mount
        8ms systemd-sysusers.service
        8ms systemd-rfkill.service
        8ms wpa_supplicant.service
        7ms systemd-update-utmp.service
        7ms systemd-user-sessions.service
        7ms modprobe@drm.service
        7ms proc-sys-fs-binfmt_misc.mount
        6ms systemd-modules-load.service
        6ms user-runtime-dir@1000.service
        6ms systemd-network-generator.service
        6ms initrd-udevadm-cleanup-db.service
        5ms modprobe@fuse.service
        5ms rpc-statd-notify.service
        4ms sys-fs-fuse-connections.mount
        4ms modprobe@efi_pstore.service
        4ms systemd-update-utmp-runlevel.service
        4ms modprobe@loop.service
        2ms modprobe@dm_mod.service
       85us systemd-homed-activate.service
lines 247-269/269 (END)


graphical.target @10.536s
└─multi-user.target @10.536s
  └─plymouth-quit-wait.service @8.619s +1.915s
    └─systemd-user-sessions.service @8.610s +7ms
      └─remote-fs.target @8.595s
        └─remote-fs-pre.target @2.630s
          └─nfs-client.target @2.630s
            └─gssproxy.service @2.604s +25ms
              └─network.target @2.586s
                └─wpa_supplicant.service @10.025s +8ms
                  └─basic.target @2.062s
                    └─dbus-broker.service @2.041s +19ms
                      └─dbus.socket @2.026s
                        └─sysinit.target @2.023s
                          └─systemd-resolved.service @1.957s +65ms
                            └─systemd-tmpfiles-setup.service @1.839s +96ms
                              └─import-state.service @1.818s +20ms
                                └─local-fs.target @1.816s
                                  └─boot-efi.mount @1.802s +13ms
                                    └─boot.mount @1.791s +8ms
                                      └─systemd-fsck@dev-disk-by\x2duuid-b13cb210\x2d8543\x2d4424\x2d8954\x2d6f2d083bdd10.service @1.097s +41ms
                                        └─dev-disk-by\x2duuid-b13cb210\x2d8543\x2d4424\x2d8954\x2d6f2d083bdd10.device @584542y 2w 2d 20h 47.873s +1min 2.758s
lines 3-25/25 (END)

And I see, that i missed some lines in my last post. I don’t know the command to show every line for systemd-analyze blame and systemd-analyze critical-chain. And I didn’t even noticed there was more lines. I pressed Return a lot now, copied and pasted it here. I hope it is complete now. Very sorry for that.

And now I see the last line (“dev-disk-by\x2d…”) that took a lot of time!?

I also want to thank everybody in this thread who takes the time to read and answer my post. I really appreciate it. :slight_smile:

That does seem to be the problem.

I noticed in the svg that you seem to need to type in a passphrase?
Is that because the disk is encrypted?
If so that is why its slow I would guess.

The only passphrase I use is to login. The disc is not encrypted.

I don’t know if it helps, but at the moment I have installed Fedora and Windows 11 on the same SSD. The other two SSD are space for files (like games). I use one for Windows and one for Fedora.

Is it possible that I messed up the disc where both OS are installed on? Or that something in the bootloader is misconfigured? Even if I have no idea what I could have done to cause that.

That it how the disc looks like now:

Sorry if this has nothing to do with my problem. I just read something about “disk” and this is what comes to my mind. And searching the WWW for “dev-disk-by\x2duuid-b13cb210\x2d8543\x2d4424\x2d8954\x2d6f2d083bdd10.device” often ends with something aboud disc, partions etc.

You can find what partition the UUID refers to by using the lsblk -f command.

1 Like
stephan@fedora:~$ lsblk -f
NAME FSTYPE FSVER LABEL      UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                              
└─sda1
     exfat  1.0   HDD2 Games F67F-06A2                                           
zram0
                                                                                 [SWAP]
nvme0n1
│                                                                                
├─nvme0n1p1
│    vfat   FAT32            786E-C2DF                              50.6M    47% /boot/efi
├─nvme0n1p2
│                                                                                
├─nvme0n1p3
│    ext4   1.0              892ab8f7-9235-465f-97b3-fde80358e0ce  652.9G     0% /mnt/892ab8f7-9235-465f-97b3-fde80358e0ce
├─nvme0n1p4
│    ntfs                    A29EECF09EECBE43                                    
├─nvme0n1p5
│    ext4   1.0              b13cb210-8543-4424-8954-6f2d083bdd10    476M    44% /boot
└─nvme0n1p6
     btrfs        fedora     9da0c55c-1be3-4fce-a799-414e41e83b5f     13G    92% /home
                                                                                 /
nvme1n1
│                                                                                
└─nvme1n1p1
     ntfs                    3412093D12090618                        

Thanks. So this partition here seems to be involved in the problem:
├─nvme0n1p5
│ ext4 1.0 b13cb210-8543-4424-8954-6f2d083bdd10 476M 44% /boot

Any ideas what could be wrong? Is there a magic command that can check/repair/dowhatever this partition? There are some options in the graphical UI of fedora (like check and repair) that I cannot run, because Fedora is not able to unmount the partition (Error unmounting /dev/nvme0n1p5: target is busy (udisks-error-quark, 14). Guess because I am using it right now while I write this!?

What I did in the past when errors like this occur: reinstall everything :wink: But guess that’s not the fine art of problem solving. But if you say it could be the easiest way to solve it, I would do. :slight_smile:

You should be able to umount /boot/efi the /boot.
Then you can mount /boot again and see if it is slow or reports errors.
Do this from the command line.

sudo umount /boot/efi
sudo umount /boot
# is the mount slow?
time sudo mount /boot
# check dmesg for messages about the disk
sudo dmesg | tail -n 20

Now lets force a check of the file system:

sudo umount /boot
sudo fsck.ext4 -f /dev/nvme0n1p5
# does it want to repair anything?

And finally mount back to initial state

sudo mount /boot
sudo mount /boot/efi

Let us know what you find out

1 Like

I don’t have anything to try to improve boot times or any suggestions yet, but here’s my systemd-analyze for a reference (F40, NVMe, UEFI, no encryption, F2FS root, XFS /boot):

Startup finished in 9.716s (firmware) + 1.638s (loader) + 992ms (kernel) + 6.840s (initrd) + 10.943s (userspace) = 30.132s

Those boot times commands mentioned are pretty cool! Seems like I’ll have some fun shaving off seconds on whatever firmware is doing for 10 seconds as Windows can boot to the log-in from cold in about the same time.


Edit: openSUSE TW:

Startup finished in 4.491s (firmware) + 603ms (loader) + 452ms (kernel) + 3.874s (initrd) + 5.691s (userspace) = 15.112s

The firmware time averages 10s (doesn’t feel like it real-time) with the lid shut; if I leave the lid open, it’s around 5s. Headless mode didn’t improve it, nor did connecting my HDMI screen over a USB-C dock.

Loader seems based on the boot loader timeout; with it at 0 it takes less than a second apparently by itself. I know people say GRUB is heavy or slow or whatever, but less than a second on UEFI is pretty good :stuck_out_tongue:

Initrd would either be 2s or 4s but I’m not sure why. I tried a bunch of compression flags and found uncompressed the best, but barely (the other options compress to half the file size with barely some ms longer boots)

1 Like

That looks fine for me:

real	0m0.027s
user	0m0.004s
sys	0m0.012s


I hope it is okay just to post the output for this, because I don’t find out what to look for:

[   69.010010] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   69.010013] Bluetooth: BNEP filters: protocol multicast
[   69.010017] Bluetooth: BNEP socket layer initialized
[   69.010659] Bluetooth: MGMT ver 1.22
[   69.058057] block nvme0n1: No UUID available providing old NGUID
[   69.091607] NET: Registered PF_QIPCRTR protocol family
[   69.293264] Generic FE-GE Realtek PHY r8169-0-700:00: attached PHY driver (mii_bus:phy_addr=r8169-0-700:00, irq=MAC)
[   69.458386] r8169 0000:07:00.0 enp7s0: Link is Down
[   72.285739] r8169 0000:07:00.0 enp7s0: Link is Up - 1Gbps/Full - flow control rx/tx
[   75.571984] rfkill: input handler disabled
[   76.297038] Bluetooth: RFCOMM TTY layer initialized
[   76.297045] Bluetooth: RFCOMM socket layer initialized
[   76.297050] Bluetooth: RFCOMM ver 1.11
[   89.925597] systemd-journald[760]: /var/log/journal/09efcb325ac14bd498587a4653654d29/user-1000.journal: Journal file uses a different sequence number ID, rotating.
[   90.221583] rfkill: input handler enabled
[   91.067481] rfkill: input handler disabled
[   92.144632] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[   92.144636] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
[  289.781960] EXT4-fs (nvme0n1p5): unmounting filesystem b13cb210-8543-4424-8954-6f2d083bdd10.
[  302.625207] EXT4-fs (nvme0n1p5): mounted filesystem b13cb210-8543-4424-8954-6f2d083bdd10 r/w with ordered data mode. Quota mode: none.


Doesn’t seem so. At least there is no message about repair or something:

e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/nvme0n1p5: 52/65536 files (23.1% non-contiguous), 123076/262144 blocks


I did all the commands and there was nothing slow, nothing special (for my eyes) and all the output is above where I don’t see anything!?

I am not sure what to check next.

1 Like

Don’t worry. But thank you for your time and effort to help. :slight_smile:

I kinda solved it.

I decided to do it my usual way one last (haha) time and start with a brand new installation of fedora. (I used this also to get rid of windows. I will focus on linux completely.)

But even after the new installation the boot time was the same. That brings me to think about hardware. In another thread of this forum here, I found someone who just unplugged several usb-devices.

And here we go: after I unplugged the offical Xbox Wireless Controller Connector the system starts as it should.

Startup finished in 7.915s (firmware) + 2.049s (loader) + 4.195s (kernel) + 3.338s (initrd) + 10.558s (userspace) = 28.058s 
graphical.target reached after 10.538s in userspace.

I don’t know why exactly. Maybe I messed somethin up as I tried to get the wireless controller running. But I am glad it works now and that I learned a little bit. :wink:

Thanks again to everyone how took time to help me!

1 Like

Some months back I think Xbox One controller wireless receivers needed some module, which then had me just plug it in with a long USB-C cable :stuck_out_tongue: (the USB support is in the kernel iirc)

1 Like

And I see, that i missed some lines in my last post. I don’t know the command to show every line for systemd-analyze blame and systemd-analyze critical-chain.

This reply is outside of the “solution” itself, this is to answer how to get the entire output of systemd-analyze.

Try adding “–no-pager”

systemd-analyze --no-pager blame

the pager can be a problem when you want the entire uninterrupted output of various commands. Many other commands accept the --no-pager option, see their ‘–help’ output or manual page to see if they do.

@barryascott

Hi, I am having a similar issue and after running “time sudo mount /boot”, these are the results:

real 0m0.217s
user 0m0.005s
sys 0m0.012s

Do you have any suggestions/thoughts?