Extremely slow boot on my Fedora32

csantaniel · June 11, 2020, 8:08pm

hello friends, i’m new here, i installed fedora32 a few weeks ago, and it has a very slow initial boot, maybe you can help me.
I will leave some information from my system for you to analyze.

graphical.target @1min 42.064s
└─multi-user.target @1min 42.063s
└─plymouth-quit-wait.service @59.822s +42.240s
└─systemd-user-sessions.service @59.583s +35ms
└─remote-fs.target @59.521s
└─remote-fs-pre.target @59.519s
└─nfs-client.target @51.672s
└─gssproxy.service @50.740s +928ms
└─network.target @50.722s
└─wpa_supplicant.service @53.532s +103ms
└─dbus-broker.service @31.675s +1.468s
└─dbus.socket @30.939s
└─sysinit.target @30.917s
└─systemd-userdbd.service @1min 2.466s +307ms
└─systemd-userdbd.socket @4.429s
└─system.slice
└─-.slice

Startup finished in 1.814s (kernel) + 4.611s (initrd) + 1min 42.077s (userspace) = 1min 48.504s
graphical.target reached after 1min 42.064s in userspace

42.240s plymouth-quit-wait.service >
24.007s systemd-journal-flush.service >
18.336s firewalld.service >
17.107s akmods.service >
16.035s upower.service >
15.069s sssd.service >
10.706s systemd-udev-settle.service >
8.733s NetworkManager-wait-online.service >
8.654s lvm2-monitor.service >
8.267s udisks2.service >
7.329s ModemManager.service >
5.562s libvirtd.service >
5.516s initrd-switch-root.service >
2.834s systemd-udevd.service >
2.827s chronyd.service >
2.654s abrtd.service >
2.611s fwupd.service >
2.416s packagekit.service >
2.239s cups.service >
2.119s avahi-daemon.service >
1.927s rtkit-daemon.service >
1.917s switcheroo-control.service >
1.916s systemd-homed.service >
lines 1-23…skipping…
42.240s plymouth-quit-wait.service
24.007s systemd-journal-flush.service
18.336s firewalld.service
17.107s akmods.service
16.035s upower.service
15.069s sssd.service
10.706s systemd-udev-settle.service
8.733s NetworkManager-wait-online.service
8.654s lvm2-monitor.service
8.267s udisks2.service
7.329s ModemManager.service
5.562s libvirtd.service
5.516s initrd-switch-root.service
2.834s systemd-udevd.service
2.827s chronyd.service
2.654s abrtd.service
2.611s fwupd.service
2.416s packagekit.service
2.239s cups.service
2.119s avahi-daemon.service
1.927s rtkit-daemon.service
1.917s switcheroo-control.service
1.916s systemd-homed.service
1.915s systemd-machined.service
1.857s user@42.service
1.662s dracut-initqueue.service
1.468s dbus-broker.service
1.239s systemd-tmpfiles-setup-dev.service
1.126s user@1000.service
1.111s polkit.service
1.106s NetworkManager.service
1.018s dmraid-activation.service
993ms systemd-fsck@dev-disk-by\x2duuid-5d4dffc3\x2d1eac\x2d47a5\x2d8f49\x2d44a2402faae2.service
928ms gssproxy.service
915ms systemd-tmpfiles-setup.service
868ms systemd-tmpfiles-clean.service
859ms systemd-fsck@dev-mapper-fedora_localhost\x2d\x2dlive\x2dhome.service
855ms systemd-modules-load.service
825ms systemd-random-seed.service
789ms systemd-journald.service
743ms lvm2-pvscan@8:5.service
42.240s plymouth-quit-wait.service
24.007s systemd-journal-flush.service
18.336s firewalld.service
17.107s akmods.service
16.035s upower.service
15.069s sssd.service
10.706s systemd-udev-settle.service
8.733s NetworkManager-wait-online.service
8.654s lvm2-monitor.service
8.267s udisks2.service
7.329s ModemManager.service
5.562s libvirtd.service
5.516s initrd-switch-root.service
2.834s systemd-udevd.service
2.827s chronyd.service
2.654s abrtd.service
2.611s fwupd.service
2.416s packagekit.service
2.239s cups.service
2.119s avahi-daemon.service
1.927s rtkit-daemon.service
1.917s switcheroo-control.service
1.916s systemd-homed.service
1.915s systemd-machined.service
1.857s user@42.service
1.662s dracut-initqueue.service
1.468s dbus-broker.service
1.239s systemd-tmpfiles-setup-dev.service
1.126s user@1000.service
1.111s polkit.service
1.106s NetworkManager.service
1.018s dmraid-activation.service
993ms systemd-fsck@dev-disk-by\x2duuid-5d4dffc3\x2d1eac\x2d47a5\x2d8f49\x2d44a2402faae2.service
928ms gssproxy.service
915ms systemd-tmpfiles-setup.service
868ms systemd-tmpfiles-clean.service
859ms systemd-fsck@dev-mapper-fedora_localhost\x2d\x2dlive\x2dhome.service
855ms systemd-modules-load.service
825ms systemd-random-seed.service

No jobs running.

NIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.

– Logs begin at Sat 2020-06-06 19:12:37 -03, end at Thu 2020-06-11 15:51:33>
jun 11 10:50:05 fedora kernel: DMAR: [Firmware Bug]: No firmware reserved re>
jun 11 13:51:44 fedora dbus-broker-launch[1460]: Activation request for 'org>
jun 11 13:51:44 fedora dbus-broker-launch[1460]: Activation request for 'org>
jun 11 13:51:48 fedora dbus-broker-launch[1460]: Activation request for 'org>
jun 11 13:51:48 fedora dbus-broker-launch[1460]: Activation request for 'org>
jun 11 13:51:50 fedora dbus-broker-launch[1460]: Activation request for 'org>
jun 11 13:51:50 fedora dbus-broker-launch[1460]: Activation request for 'org>
jun 11 13:51:50 fedora dbus-broker-launch[1460]: Activation request for 'org>
jun 11 13:51:50 fedora dbus-broker-launch[1460]: Activation request for 'org>
jun 11 13:52:01 fedora gdm-password][1796]: gkr-pam: unable to locate daemon>

csantaniel@fedora
:-------------------:: -----------------
:-----------/shhOHbmp—:\ OS: Fedora release 32 (Thirty Two) x86_6
/-----------omMMMNNNMMD —: Host: 500R5L/501R5L/500R5P P06RDM
:-----------sMMMMNMNMP. —: Kernel: 5.6.16-300.fc32.x86_64
:-----------:MMMdP------- —\ Uptime: 2 hours, 2 mins
,------------:MMMd-------- —: Packages: 2167 (rpm), 12 (flatpak)
:------------:MMMd------- .—: Shell: bash 5.0.17
:---- oNMMMMMMMMMNho .----: Resolution: 1920x1080
:-- .+shhhMMMmhhy++ .------/ DE: GNOME
:- -------:MMMd--------------: WM: Mutter
:- --------/MMMd-------------; WM Theme: Adwaita
:- ------/hMMMy------------: Theme: Adwaita [GTK2/3]
:-- :dMNdhhdNMMNo------------; Icons: Adwaita [GTK2/3]
:—:sdNMMMMNds:------------: Terminal: gnome-terminal
:------:://:-------------:: CPU: Intel i7-6500U (4) @ 3.100GHz
:---------------------:// GPU: NVIDIA GeForce 940MX
GPU: Intel Skylake GT2 [HD Graphics 520]
Memory: 3218MiB / 7868MiB

lcts · June 12, 2020, 9:55am

This seems rather a lot. It’s possible that this is related to the size of your journal files. Can you check the output of

journalctl --disk-usage

? journald also logs information on the flushing of the journal to disk during startup, you can check that as well.

plymouth-quit-wait.service in itself doesn’t do anything, it just waits for all the underlying boot process to finish, in order to keep displaying the boot screen until the login screen is ready. Something else is started in parallel with this service that takes a long time to finish. You can use systemd-analyze plot to create a graph of your boot process, that may show you what that service is waiting for.

csantaniel · June 12, 2020, 4:59pm

Thank you for helping me friend.
the second command you gave me, the result was quite extensive, I couldn’t put the whole result here for you to analyze.I’m sorry for that, I don’t know this will help you, I don’t understand anything about it.
About 272M of space occupied by Jornalctl, how can I delete these logs? … to free up space and see if the boot speed improves.

$ journalctl --disk-usage
Archived and active journals take up 272.0M in the file system.
systemd-analyze plot

<?xml version="1.0" standalone="no"?>

sideburns · June 12, 2020, 6:00pm

Your output keeps giving the same information over and over. Please run

systemd-analyze blame

and post the results here so that we have a clean copy. Also, you can trim off anything that takes less than a second as not important.

csantaniel · June 12, 2020, 9:37pm

ok.here go
48.327s plymouth-quit-wait.service 24.348s firewalld.service 23.315s upower.service 21.840s libvirtd.service 19.313s sssd.service 18.738s systemd-journal-flush.service 16.729s akmods.service 12.831s udisks2.service 11.897s systemd-udev-settle.service 11.800s abrtd.service 10.903s NetworkManager-wait 10.829s lvm2-monitor.service 8.682s chronyd.service 8.522s ModemManager.service 7.708s avahi-daemon.service 7.080s initrd-switch-root.service 6.735s rtkit-daemon.service 3.760s systemd-logind.service 3.170s fwupd.service 2.897s cups.service 2.796s systemd-udevd.service 2.190s dracut-initqueue.service 2.170s user@42.service lines 1-23…skipping…
48.327s plymouth-quit-wait.service
24.348s firewalld.service
23.315s upower.service
21.840s libvirtd.service
19.313s sssd.service
18.738s systemd-journal-flu 16.729s akmods.service
12.831s udisks2.service
11.897s systemd-udev-settle.service
11.800s abrtd.service
10.903s NetworkManager-wait 10.829s lvm2-monitor.service
8.682s chronyd.service
8.522s ModemManager.service
7.708s avahi-daemon.service
7.080s initrd-switch-root.service
6.735s rtkit-daemon.service
3.760s systemd-logind.service
3.170s fwupd.service
2.897s cups.service
2.796s systemd-udevd.service
2.190s dracut-initqueue.service
2.170s user@42.service
2.037s packagekit.service
1.797s accounts-daemon.service
1.583s switcheroo-control.service
1.578s systemd-homed.service
1.577s systemd-machined.service
1.489s systemd-tmpfiles-set 1.287s dmraid-activation.service
1.160s polkit.service
1.133s systemd-fsck@dev-dis 1.127s dbus-broker.service
1.031s lvm2-pvscan@8:5.service
1.003s NetworkManager.service >
>
>
>
>
>
>
>
>
>
-online.service >
>
>
>
>
>
>
>
>
>
>
>
>
sh.service
-online.service
up-dev.service
k-by\x2duuid-5d4dffc3\x2d1eac\x2d47a5\x2d8f49\x2d44a2402faae2.service

sideburns · June 13, 2020, 3:27am

Why does your output keep repeating the first 23 lines? However, unless you’re actually using a modem, you can disable and mask ModemManager.service. And, if you’re not using lvm, you can get rid of that.

lcts · June 13, 2020, 7:09am

Sorry, I was imprecise. That commands generates a SVG graphic, so you’ll need to use:

systemd-analyze plot > bootchart.svg

You can then look at bootchart.svg using the image viewer of your choice. It should show you which services are started in parallel with the plymouth one, and hopefully give you an indication of what is causing the holdup.

Hm, that is not really that much. It really shouldn’t take that long to flush the journal. On my system, with ~100MB of logs, systemd-journald-flush.service takes ~130ms to start up.
And journald’s log shows that it actually only spends 8ms to flush the journal to disk:

ce@kat ~ % journalctl -b -u systemd-journald
-- Logs begin at Thu 2020-06-04 08:14:01 CEST, end at Sat 2020-06-13 08:56:39 CEST. --
Jun 13 08:34:37 kat systemd-journald[415]: Journal started
Jun 13 08:34:37 kat systemd-journald[415]: Runtime Journal (/run/log/journal/aae45fb4bac84d44a9f79c24d424e091) is 8.0M, max 100.0M, 92.0M free.
Jun 13 08:34:37 kat systemd[1]: systemd-journald.service: Succeeded.
Jun 13 08:34:37 kat systemd-journald[415]: Time spent on flushing to /var/log/journal/aae45fb4bac84d44a9f79c24d424e091 is 8.168ms for 1267 entries.
Jun 13 08:34:37 kat systemd-journald[415]: System Journal (/var/log/journal/aae45fb4bac84d44a9f79c24d424e091) is 112.0M, max 100.0M, 0B free.