My laptop takes about a minute to boot Fedora, considerably slower than it takes to boot other operating systems. I’ve looked around on the forum and see that it’s a recurring issue but haven’t found anyone else where dracut-initqueue.service seems to be the culprit.
I’ve had slow boot for some time on Fedora 32 and it hasn’t been improved since upgrading to Fedora 33.
I’m running on SSD, Intel i7-8 gen, 16 GB RAM and boot typically takes around 60-90 seconds.
$ systemd-analyze
Startup finished in 1.106s (kernel) + 43.243s (initrd) + 14.001s (userspace) = 58.351s
graphical.target reached after 13.990s in userspace
$ systemd-analyze blame
42.301s dracut-initqueue.service
5.977s NetworkManager-wait-online.service
3.217s plymouth-quit-wait.service
3.098s systemd-udev-settle.service
1.161s fwupd.service
834ms lvm2-monitor.service
748ms upower.service
745ms firewalld.service
485ms initrd-switch-root.service
450ms udisks2.service
411ms sssd.service
370ms lvm2-pvscan@259:7.service
256ms ModemManager.service
236ms systemd-logind.service
199ms var-lib-snapd-snap-core18-1885.mount
194ms avahi-daemon.service
189ms iio-sensor-proxy.service
184ms systemd-resolved.service
181ms rtkit-daemon.service
180ms switcheroo-control.service
178ms var-lib-snapd-snap-core18-1932.mount
174ms systemd-machined.service
170ms libvirtd.service
167ms initrd-parse-etc.service
166ms var-lib-snapd-snap-spotify-42.mount
152ms abrtd.service
151ms cups.service
139ms user@1000.service
133ms var-lib-snapd-snap-snapd-9279.mount
132ms systemd-journal-flush.service
120ms systemd-vconsole-setup.service
115ms var-lib-snapd-snap-spotify-41.mount
113ms systemd-udevd.service
111ms systemd-tmpfiles-clean.service
111ms polkit.service
105ms systemd-udev-trigger.service
103ms var-lib-snapd-snap-pdfmixtool-776.mount
98ms dbus-broker.service
96ms var-lib-snapd-snap-snapd-9721.mount
89ms dracut-cmdline.service
87ms packagekit.service
68ms systemd-tmpfiles-setup.service
63ms var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1506.mount
59ms var-lib-snapd-snap-pdfmixtool-785.mount
47ms livesys.service
46ms var-lib-nfs-rpc_pipefs.mount
42ms chronyd.service
41ms vpnagentd.service
39ms systemd-journald.service
35ms NetworkManager.service
35ms systemd-tmpfiles-setup-dev.service
34ms dev-loop3.device
33ms dracut-pre-pivot.service
33ms accounts-daemon.service
33ms netcf-transaction.service
33ms systemd-fsck@dev-disk-by\x2duuid-5EBF\x2d3376.service
33ms dev-loop4.device
32ms import-state.service
32ms auditd.service
32ms dev-loop2.device
31ms dev-loop1.device
30ms sssd-kcm.service
28ms systemd-binfmt.service
28ms dracut-pre-udev.service
27ms dev-mapper-fedora_localhost\x2d\x2dlive\x2dswap.swap
27ms systemd-fsck-root.service
26ms systemd-rfkill.service
26ms dev-loop5.device
25ms colord.service
25ms swap-create@zram0.service
24ms flatpak-system-helper.service
23ms livesys-late.service
23ms systemd-fsck@dev-mapper-fedora_localhost\x2d\x2dlive\x2dhome.service
22ms gssproxy.service
21ms systemd-random-seed.service
19ms plymouth-start.service
19ms systemd-fsck@dev-disk-by\x2duuid-46ca08fd\x2dbe23\x2d4bd8\x2d9393\x2d628f467c8be2.service
18ms systemd-modules-load.service
18ms systemd-remount-fs.service
17ms plymouth-switch-root.service
16ms user-runtime-dir@1000.service
15ms dev-hugepages.mount
15ms plymouth-read-write.service
14ms boot-efi.mount
14ms dev-mqueue.mount
14ms gdm.service
13ms systemd-backlight@backlight:intel_backlight.service
13ms sys-kernel-debug.mount
13ms dev-loop6.device
13ms initrd-cleanup.service
12ms kmod-static-nodes.service
12ms systemd-sysctl.service
11ms systemd-user-sessions.service
11ms nfs-convert.service
11ms wpa_supplicant.service
11ms dev-zram0.swap
11ms home.mount
10ms dev-loop0.device
10ms proc-sys-fs-binfmt_misc.mount
9ms sysroot.mount
9ms systemd-update-utmp.service
9ms systemd-update-utmp-runlevel.service
8ms dev-loop8.device
7ms boot.mount
7ms rpc-statd-notify.service
7ms initrd-udevadm-cleanup-db.service
6ms dracut-shutdown.service
6ms tmp.mount
5ms iscsi-shutdown.service
4ms sys-fs-fuse-connections.mount
4ms docker.socket
2ms dev-loop7.device
2ms sys-kernel-config.mount
1ms snapd.socket
$ 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 @13.990s
└─multi-user.target @13.990s
└─plymouth-quit-wait.service @10.771s +3.217s
└─systemd-user-sessions.service @10.753s +11ms
└─remote-fs.target @10.748s
└─remote-fs-pre.target @10.748s
└─nfs-client.target @4.795s
└─gssproxy.service @4.771s +22ms
└─network.target @4.766s
└─wpa_supplicant.service @5.397s +11ms
└─dbus-broker.service @4.031s +98ms
└─dbus.socket @3.972s
└─sysinit.target @3.969s
└─systemd-update-utmp.service @3.957s +9ms
└─auditd.service @3.923s +32ms
└─systemd-tmpfiles-setup.service @3.852s +68ms
└─import-state.service @3.818s +32ms
└─local-fs.target @3.814s
└─var-lib-snapd-snap-core18-1885.mount @3.613s +199ms
└─dev-loop8.device @3.805s +8ms
