Slow Boot (3+ minutes). How to fix it?

Ask Fedora
,
1

Hi guys,
I used Fedora for 1 year now and I love it.
Since few days I face an issue: the boot needs more than 3 minutes to be completed.

Can anyone please help me? How can I fix it?

If I launch on the terminal the command systemd-analyze blame this is the output:

3min 2.998s sys-devices-pci0000:00-0000:00:0d.0-usb2-2\x2d4-2\x2d4.1-2\x2d4.1:2.0-net-enp0s13f0u4u1c2.device
 3min 2.998s sys-subsystem-net-devices-enp0s13f0u4u1c2.device
 3min 1.133s dev-ttyS10.device
 3min 1.133s sys-devices-platform-serial8250-serial8250:0-serial8250:0.10-tty-ttyS10.device
 3min 1.127s sys-module-fuse.device
 3min 1.114s sys-devices-platform-serial8250-serial8250:0-serial8250:0.12-tty-ttyS12.device
 3min 1.114s dev-ttyS12.device
 3min 1.114s dev-ttyS18.device
 3min 1.114s sys-devices-platform-serial8250-serial8250:0-serial8250:0.18-tty-ttyS18.device
 3min 1.113s sys-devices-platform-serial8250-serial8250:0-serial8250:0.15-tty-ttyS15.device
 3min 1.113s dev-ttyS15.device
 3min 1.107s dev-ttyS0.device
 3min 1.107s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
 3min 1.104s sys-devices-platform-serial8250-serial8250:0-serial8250:0.17-tty-ttyS17.device
 3min 1.104s dev-ttyS17.device
 3min 1.103s sys-devices-platform-serial8250-serial8250:0-serial8250:0.16-tty-ttyS16.device
 3min 1.103s dev-ttyS16.device
 3min 1.102s dev-ttyS19.device
 3min 1.102s sys-devices-platform-serial8250-serial8250:0-serial8250:0.19-tty-ttyS19.device
 3min 1.101s sys-devices-platform-serial8250-serial8250:0-serial8250:0.14-tty-ttyS14.device
 3min 1.101s dev-ttyS14.device
 3min 1.097s sys-devices-platform-serial8250-serial8250:0-serial8250:0.30-tty-ttyS30.device
 3min 1.097s dev-ttyS30.device
 3min 1.097s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
 3min 1.097s dev-ttyS1.device
 3min 1.096s sys-devices-platform-serial8250-serial8250:0-serial8250:0.26-tty-ttyS26.device
 3min 1.096s dev-ttyS26.device
 3min 1.095s dev-ttyS2.device
 3min 1.095s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
 3min 1.094s sys-devices-platform-serial8250-serial8250:0-serial8250:0.25-tty-ttyS25.device
 3min 1.094s dev-ttyS25.device
 3min 1.094s sys-devices-platform-serial8250-serial8250:0-serial8250:0.4-tty-ttyS4.device
 3min 1.094s dev-ttyS4.device
 3min 1.093s sys-devices-platform-serial8250-serial8250:0-serial8250:0.20-tty-ttyS20.device
 3min 1.093s dev-ttyS20.device
 3min 1.092s sys-devices-platform-serial8250-serial8250:0-serial8250:0.13-tty-ttyS13.device
 3min 1.092s dev-ttyS13.device
 3min 1.091s dev-ttyS11.device
 3min 1.091s sys-devices-platform-serial8250-serial8250:0-serial8250:0.11-tty-ttyS11.device
 3min 1.091s dev-ttyS22.device
 3min 1.091s sys-devices-platform-serial8250-serial8250:0-serial8250:0.22-tty-ttyS22.device
 3min 1.089s dev-ttyS21.device
 3min 1.089s sys-devices-platform-serial8250-serial8250:0-serial8250:0.21-tty-ttyS21.device
 3min 1.084s dev-ttyS3.device
 3min 1.084s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
 3min 1.083s sys-devices-platform-serial8250-serial8250:0-serial8250:0.23-tty-ttyS23.device
 3min 1.083s dev-ttyS23.device
 3min 1.082s sys-devices-platform-serial8250-serial8250:0-serial8250:0.5-tty-ttyS5.device
 3min 1.082s dev-ttyS5.device
 3min 1.081s sys-devices-platform-serial8250-serial8250:0-serial8250:0.27-tty-ttyS27.device
 3min 1.081s dev-ttyS27.device
 3min 1.080s sys-devices-platform-serial8250-serial8250:0-serial8250:0.8-tty-ttyS8.device
 3min 1.080s dev-ttyS8.device
 3min 1.080s sys-devices-platform-serial8250-serial8250:0-serial8250:0.6-tty-ttyS6.device
 3min 1.080s dev-ttyS6.device
 3min 1.078s dev-ttyS31.device
 3min 1.078s sys-devices-platform-serial8250-serial8250:0-serial8250:0.31-tty-ttyS31.device
 3min 1.078s sys-devices-platform-serial8250-serial8250:0-serial8250:0.24-tty-ttyS24.device
 3min 1.078s dev-ttyS24.device
 3min 1.076s sys-devices-platform-serial8250-serial8250:0-serial8250:0.28-tty-ttyS28.device
 3min 1.076s dev-ttyS28.device
 3min 1.076s dev-ttyS29.device
 3min 1.076s sys-devices-platform-serial8250-serial8250:0-serial8250:0.29-tty-ttyS29.device
 3min 1.068s sys-devices-platform-serial8250-serial8250:0-serial8250:0.7-tty-ttyS7.device
 3min 1.068s dev-ttyS7.device
 3min 1.068s dev-ttyS9.device
 3min 1.068s sys-devices-platform-serial8250-serial8250:0-serial8250:0.9-tty-ttyS9.device
 3min 1.050s sys-module-configfs.device
  3min 876ms dev-nvme0n1p4.device
  3min 876ms dev-disk-by\x2ddiskseq-1\x2dpart4.device
  3min 876ms dev-disk-by\x2dpartuuid-325bab91\x2db714\x2d42ee\x2d9bff\x2d049a796f5634.device
  3min 876ms dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB_______S65VNF0R811268_1\x2dpart4.device
  3min 876ms dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart4.device
  3min 875ms dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB_______S65VNF0R811268\x2dpart4.device
  3min 875ms sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p4.device
  3min 875ms dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB__S65VNF0R811268\x2dpart4.device
  3min 875ms dev-disk-by\x2did-nvme\x2deui.36355630528112680025384600000001\x2dpart4.device
  3min 875ms dev-disk-by\x2duuid-0E8E50DF8E50C0BF.device
  3min 873ms dev-disk-by\x2ddiskseq-1\x2dpart3.device
  3min 873ms dev-disk-by\x2did-nvme\x2deui.36355630528112680025384600000001\x2dpart3.device
  3min 873ms dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB_______S65VNF0R811268_1\x2dpart3.device
  3min 873ms sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
  3min 873ms dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB__S65VNF0R811268\x2dpart3.device
  3min 873ms dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
  3min 873ms dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB_______S65VNF0R811268\x2dpart3.device
  3min 873ms dev-disk-by\x2duuid-E0FE3E8EFE3E5CCA.device
  3min 873ms dev-disk-by\x2dpartuuid-306c3f5b\x2d8a81\x2d45b3\x2db5f7\x2d22aad2c48c4f.device
  3min 873ms dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart3.device
  3min 873ms dev-nvme0n1p3.device
  3min 872ms dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart2.device
  3min 872ms dev-disk-by\x2dpartuuid-2089c9ed\x2d4de8\x2d48a0\x2db4bc\x2dfb53a8c0b895.device
  3min 872ms dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device
  3min 872ms dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB__S65VNF0R811268\x2dpart2.device
  3min 872ms dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB_______S65VNF0R811268\x2dpart2.device
  3min 872ms dev-disk-by\x2did-nvme\x2deui.36355630528112680025384600000001\x2dpart2.device
  3min 872ms dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB_______S65VNF0R811268_1\x2dpart2.device
  3min 872ms dev-nvme0n1p2.device
  3min 871ms sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
  3min 871ms dev-disk-by\x2ddiskseq-1\x2dpart2.device
  3min 869ms dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB__S65VNF0R811268\x2dpart5.device
  3min 869ms dev-disk-by\x2did-nvme\x2deui.36355630528112680025384600000001\x2dpart5.device
  3min 869ms dev-disk-by\x2dpartuuid-1738619b\x2d5dc3\x2d4908\x2d9db0\x2db45c9fa69ee3.device
  3min 869ms sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p5.device
  3min 869ms dev-disk-by\x2ddiskseq-1\x2dpart5.device
  3min 869ms dev-nvme0n1p5.device
  3min 869ms dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB_______S65VNF0R811268_1\x2dpart5.device
  3min 869ms dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB_______S65VNF0R811268\x2dpart5.device
  3min 869ms dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart5.device
  3min 869ms dev-disk-by\x2duuid-0a227aef\x2d84f5\x2d497c\x2d8eb3\x2d918309959f96.device
  3min 864ms dev-disk-by\x2dpartuuid-f337bc51\x2d3e4a\x2d472f\x2d81bd\x2d70f5630f58c2.device
  3min 864ms dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB__S65VNF0R811268\x2dpart1.device
  3min 864ms dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB_______S65VNF0R811268\x2dpart1.device
  3min 864ms sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
  3min 864ms dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB_______S65VNF0R811268_1\x2dpart1.device
  3min 864ms dev-nvme0n1p1.device
  3min 864ms dev-disk-by\x2duuid-AA3D\x2d98B4.device
  3min 864ms dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart1.device
  3min 864ms dev-disk-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
  3min 863ms dev-disk-by\x2did-nvme\x2deui.36355630528112680025384600000001\x2dpart1.device
  3min 863ms dev-disk-by\x2ddiskseq-1\x2dpart1.device
  3min 861ms dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB_______S65VNF0R811268_1\x2dpart6.device
  3min 861ms dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB_______S65VNF0R811268\x2dpart6.device
  3min 861ms sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p6.device
  3min 861ms dev-disk-by\x2ddiskseq-1\x2dpart6.device
  3min 861ms dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart6.device
  3min 861ms dev-disk-by\x2duuid-9747a5aa\x2d0e21\x2d495c\x2dbbcd\x2dc9a6e4ef91c7.device
  3min 860ms dev-disk-by\x2did-nvme\x2deui.36355630528112680025384600000001\x2dpart6.device
  3min 860ms dev-nvme0n1p6.device
  3min 860ms dev-disk-by\x2dpartuuid-9d75ac6f\x2d79cb\x2d499d\x2db725\x2d1c025dc3719c.device
  3min 860ms dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB__S65VNF0R811268\x2dpart6.device
  3min 850ms dev-nvme0n1.device
  3min 850ms dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1.device
  3min 850ms dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB_______S65VNF0R811268_1.device
  3min 850ms sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-nvme-nvme0-nvme0n1.device
  3min 850ms dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB__S65VNF0R811268.device
  3min 850ms dev-disk-by\x2did-nvme\x2deui.36355630528112680025384600000001.device
  3min 850ms dev-disk-by\x2ddiskseq-1.device
  3min 850ms dev-disk-by\x2did-nvme\x2dPM9A1_NVMe_Samsung_1024GB_______S65VNF0R811268.device
2min 59.978s sys-devices-pci0000:00-0000:00:02.0-drm-card1-card1\x2deDP\x2d1-intel_backlight.device
  2min 590ms dracut-initqueue.service
     30.202s dracut-pre-pivot.service
     22.319s systemd-cryptsetup@luks\x2d9747a5aa\x2d0e21\x2d495c\x2dbbcd\x2dc9a6e4ef91c7.service
      4.670s NetworkManager-wait-online.service
      2.909s plymouth-quit-wait.service
      1.743s fwupd.service
       903ms initrd-switch-root.service
       445ms thermald.service
       433ms NetworkManager.service
       414ms systemd-journal-flush.service
       410ms upower.service
       316ms firewalld.service
       198ms systemd-resolved.service
       187ms tlp.service
       176ms user@1000.service
       169ms systemd-udev-trigger.service
       146ms systemd-oomd.service
       139ms dracut-cmdline.service
       131ms udisks2.service
       116ms cups.service
       115ms iio-sensor-proxy.service
       106ms systemd-tmpfiles-setup.service
       105ms dev-zram0.swap
       103ms var-lib-nfs-rpc_pipefs.mount
       100ms accounts-daemon.service
        94ms polkit.service
        88ms abrtd.service
        84ms systemd-vconsole-setup.service
        82ms systemd-userdbd.service
        76ms systemd-logind.service
        71ms ModemManager.service
        62ms lvm2-monitor.service
        62ms chronyd.service
        60ms sssd-kcm.service
        56ms systemd-tmpfiles-clean.service
        56ms systemd-journald.service
        53ms auditd.service
        51ms systemd-fsck@dev-disk-by\x2duuid-0a227aef\x2d84f5\x2d497c\x2d8eb3\x2d918309959f96.service
        49ms avahi-daemon.service
        47ms systemd-udevd.service
        45ms systemd-tmpfiles-setup-dev-early.service
        45ms systemd-fsck@dev-disk-by\x2duuid-AA3D\x2d98B4.service
        45ms systemd-backlight@leds:dell::kbd_backlight.service
        43ms virtqemud.service
        42ms systemd-random-seed.service
        41ms bluetooth.service
        40ms plymouth-switch-root.service
        40ms bolt.service
        38ms boot.mount
        38ms import-state.service
        37ms systemd-zram-setup@zram0.service
        36ms systemd-sysctl.service
        36ms dracut-pre-udev.service
        34ms dracut-shutdown.service
        32ms switcheroo-control.service
        27ms dbus-broker.service
        25ms dev-hugepages.mount
        25ms systemd-binfmt.service
        24ms uresourced.service
        24ms rtkit-daemon.service
        24ms dev-mqueue.mount
        24ms colord.service
        22ms systemd-tmpfiles-setup-dev.service
        22ms sys-kernel-debug.mount
        21ms systemd-machined.service
        21ms sys-kernel-tracing.mount
        21ms boot-efi.mount
        20ms kmod-static-nodes.service
        20ms systemd-fsck-root.service
        19ms gssproxy.service
        14ms flatpak-system-helper.service
        14ms plymouth-start.service
        14ms plymouth-read-write.service
        13ms modprobe@dm_mod.service
        12ms systemd-update-utmp.service
        12ms initrd-cleanup.service
        11ms proc-sys-fs-binfmt_misc.mount
        10ms systemd-backlight@backlight:intel_backlight.service
        10ms initrd-parse-etc.service
        10ms modprobe@loop.service
         9ms systemd-modules-load.service
         9ms gdm.service
         8ms modprobe@drm.service
         8ms systemd-sysusers.service
         8ms tmp.mount
         7ms user-runtime-dir@1000.service
         7ms systemd-network-generator.service
         7ms systemd-update-utmp-runlevel.service
         7ms wpa_supplicant.service
         7ms sys-fs-fuse-connections.mount
         7ms systemd-remount-fs.service
         7ms systemd-user-sessions.service
         6ms modprobe@configfs.service
         5ms rpc-statd-notify.service
         4ms initrd-udevadm-cleanup-db.service
         4ms home.mount
         3ms modprobe@fuse.service

Best regards :slight_smile:

2

So you get the Bluetooth guess because starting bluetooth takes long? I find the numbers a bit hard to read.

If there is a better way to get the seconds of each process starting, like journalctl -b that may be easier

3

I edited your file to change the blockquoted text to preformatted text for easier readability as seen on your screen.

I also suggest that you provide another file with systemd-analyze plot > plot.svg so the boot can be seen graphically.
You can view that file with your browser to see what is actually taking a long time, and could post that svg file here or someplace that could be linked to so we could view it and do a better analysis.

Another choice would be systemd-analyze critical-chain, though I prefer the graphical analysis myself.

1 Like
4

Hi Jeff, thanks for the answer.
This is the plot.svg: plot.svg - Google Drive

This is 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 @5.912s
└─multi-user.target @5.912s
  └─plymouth-quit-wait.service @3.071s +2.839s
    └─systemd-user-sessions.service @3.056s +8ms
      └─remote-fs.target @3.037s
        └─remote-fs-pre.target @3.037s
          └─nfs-client.target @3.037s
            └─gssproxy.service @3.021s +15ms
              └─network.target @3.014s
                └─wpa_supplicant.service @4.884s +6ms
                  └─basic.target @2.375s
                    └─dbus-broker.service @2.347s +25ms
                      └─dbus.socket @2.318s
                        └─sysinit.target @2.313s
                          └─systemd-resolved.service @2.120s +192ms
                            └─systemd-tmpfiles-setup.service @1.983s +105ms
                              └─import-state.service @1.924s +35ms
                                └─local-fs.target @1.912s
                                  └─boot-efi.mount @1.808s +102ms
                                    └─boot.mount @1.137s +20ms
                                      └─systemd-fsck@dev-disk-by\x2duuid-0a227aef\x2d84f5\x2d497c\x2d8eb3\x2d918309959f96.service>
                                        └─dev-disk-by\x2duuid-0a227aef\x2d84f5\x2d497c\x2d8eb3\x2d918309959f96.device @584542y 2w>
lines 1-25/25 (END)

Is possibile to understand how to fix it with this datas? :slight_smile:
Thank you for the support!

5

Hi boredsquirrel!
I tried with journalctl -b but the output is really huge.
I just posted the plot.svg, I think there is “easier” (surely not for me :melting_face: ) to understand what is causing the issue.

6

If you’re running Nvidia with the 6.8.4 kernel you may want tol look through Linux version 6.8.4-200.fc39.x86_64 takes very long time to boot

7

I just updated to the new version 6.8.5 and the issue is fixed! Thank you guys for the support!

8

We don’t seem to have access to that file.
Thanks for posting it.

It appears that the kernel upgrade fixed the issue for you.

Great! :+1: