Switched from Ubuntu to fedora 35 and experiencing slower boot times.
Welcome to ask 
fedora.
That image is very hard to read and posting text in the </> Preformatted text tags is much easier to read while retaining the same layout as on your screen. It also makes it possible to copy&paste as well as quoting the posted text.
Thanks for resubmitting the data in text form.
It looks like it may be taking a while to connect to a remote/NFS filesystem. You can set _netdev as a mount option in fstab so it won’t delay your boot waiting for it.
I have the same issue and I cannot figure out what can be wrong in my case.
In my case I obtain this using the same commands :
[bongo@fedora ~]$ systemd-analyze
Startup finished in 9.718s (firmware) + 4.215s (loader) + 1.749s (kernel) + 18.449s (initrd) + 2min 10.586s (userspace) = 2min 44.719s
graphical.target reached after 2min 10.548s in userspace
[bongo@fedora ~]$ 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 @2min 10.548s
└─multi-user.target @2min 10.548s
└─plymouth-quit-wait.service @2min 8.099s +2.444s
└─systemd-user-sessions.service @2min 8.084s +7ms
└─remote-fs.target @2min 8.081s
└─remote-fs-pre.target @2min 8.081s
└─nfs-client.target @2min 1.688s
└─gssproxy.service @2min 1.667s +17ms
└─network.target @2min 1.661s
└─wpa_supplicant.service @2min 2.344s +13ms
└─basic.target @2min 870ms
└─dbus-broker.service @2min 847ms +19ms
└─dbus.socket @2min 815ms
└─sysinit.target @2min 787ms
└─systemd-update-utmp.service @2min 777ms +9ms
└─auditd.service @2min 739ms +35ms
└─systemd-tmpfiles-setup.service @2min 687ms +46ms
└─import-state.service @2min 667ms +17ms
└─local-fs.target @2min 664ms
└─boot-efi.mount @2min 652ms +11ms
└─boot.mount @2min 645ms +5ms
└─systemd-fsck@dev-disk-by\x2duuid-3c21cffb\x2d86fb\x2d4bed\x2d83e6\x2d57740841cace.service @2min 618ms +23ms
└─local-fs-pre.target @2min 611ms
└─lvm2-monitor.service @444ms +453ms
└─dm-event.socket @398ms
└─system.slice
└─-.slice
bongo@fedora ~]$ systemd-analyze blame
2min 12ms systemd-udev-settle.service
17.568s dracut-initqueue.service
17.238s systemd-cryptsetup@luks\x2d0d0e93a2\x2d8d3a\x2d4c85\x2d8e76\x2d9c6b71e175b5.service
6.416s NetworkManager-wait-online.service
2.444s plymouth-quit-wait.service
1.440s fwupd.service
736ms dkms.service
623ms firewalld.service
507ms initrd-switch-root.service
453ms lvm2-monitor.service
173ms systemd-resolved.service
167ms user@1000.service
166ms upower.service
151ms systemd-rfkill.service
136ms udisks2.service
121ms initrd-parse-etc.service
120ms power-profiles-daemon.service
116ms systemd-udev-trigger.service
115ms polkit.service
114ms var-lib-nfs-rpc_pipefs.mount
114ms accounts-daemon.service
112ms ModemManager.service
106ms systemd-oomd.service
102ms dev-zram0.swap
100ms packagekit.service
95ms systemd-logind.service
86ms bluetooth.service
85ms abrtd.service
84ms avahi-daemon.service
72ms dracut-cmdline.service
71ms systemd-journal-flush.service
63ms switcheroo-control.service
58ms sys-kernel-debug.mount
58ms systemd-tmpfiles-clean.service
57ms sys-kernel-tracing.mount
56ms dev-hugepages.mount
I would appreciate any advice for troubleshooting.
Thank you in advance.
bongo@fedora ~]$ systemd-analyze blame
2min 12ms systemd-udev-settle.service
17.568s dracut-initqueue.service
17.238s systemd-cryptsetup@luks\x2d0d0e93a2\x2d8d3a\x2d4c85\x2d8e76\x2d9c6b71e175b5.service
6.416s NetworkManager-wait-online.service
2.444s plymouth-quit-wait.service
1.440s fwupd.service
736ms dkms.service
623ms firewalld.service
507ms initrd-switch-root.service
453ms lvm2-monitor.service
173ms systemd-resolved.service
167ms user@1000.service
166ms upower.service
151ms systemd-rfkill.service
136ms udisks2.service
121ms initrd-parse-etc.service
120ms power-profiles-daemon.service
116ms systemd-udev-trigger.service
115ms polkit.service
114ms var-lib-nfs-rpc_pipefs.mount
114ms accounts-daemon.service
112ms ModemManager.service
106ms systemd-oomd.service
102ms dev-zram0.swap
100ms packagekit.service
95ms systemd-logind.service
86ms bluetooth.service
85ms abrtd.service
84ms avahi-daemon.service
72ms dracut-cmdline.service
71ms systemd-journal-flush.service
63ms switcheroo-control.service
58ms sys-kernel-debug.mount
58ms systemd-tmpfiles-clean.service
57ms sys-kernel-tracing.mount
56ms dev-hugepages.mount
It looks like you may have had something wrong with the file system and the automatic fsck took 2 minutes to fix it.
1 Like
I have exactly the same behavior in every single boot. And the time is also exactly the same. In total: 1min58.
I am not sure if I understood your sentence because in this line for
systemd-fsck@dev-disk-by
I can see :
618ms + 23ms indicated.
This part. 2min 611ms
And this.
The blame seems to think the systemd-udev-settle.service is using more than 2 minutes, and that may be contributing to the time for local-fs-pre.target.
What do you have attached? something USB or ? that would be causing udev to take that long?
If you have something attached external try detaching it before the next boot.
You may be able to see what is being reported in dmesg since the dmesg entries are all time stamped and should show some of what is happening during the boot. You also should be able to peruse the output of journalctl -b and parse that for the time involved in the boot to see what is reported there.