Hey. I know many people asked this question but I couldn’t find any helpful thread to solve my problem. My loading time is very high. The systemd-analyze
shows about 1 minute and 40 seconds.
Startup finished in 9.811s (firmware) + 6.627s (loader) + 1.836s (kernel) + 14.843s (initrd) + 1min 6.498s (userspace) = 1min 39.617s
graphical.target reached after 1min 6.474s in userspace
I tried to see criticals and this happened:
The time when unit became active or started is printed after the>
The time the unit took to start is printed after the "+" charact>
graphical.target @1min 6.474s
└─multi-user.target @1min 6.473s
└─crond.service @57.796s
└─systemd-user-sessions.service @57.718s +26ms [RED]
└─remote-fs.target @57.715s
└─remote-fs-pre.target @57.714s
└─iscsi-shutdown.service @57.546s +352us [RED]
└─network.target @57.540s
└─wpa_supplicant.service @1min 167ms +167ms [RED]
└─basic.target @37.020s
└─dbus-broker.service @36.317s +698ms [RED]
└─dbus.socket @36.202s
└─sysinit.target @36.188s
└─systemd-update-utmp.service @36.131s +> [RED]
└─auditd.service @35.383s +745ms [RED]
└─systemd-tmpfiles-setup.service @34> [RED]
└─import-state.service @16.239s +4> [RED]
└─local-fs.target @16.234s
└─home.mount @15.905s +328ms [RED]
└─systemd-fsck@dev-mapper-fe> [RED]
└─local-fs-pre.target @12.>
└─lvm2-monitor.service @> [RED]
└─dm-event.socket @4.0>
└─system.slice
└─-.slice
I put a [RED]
note after the ones that were colored red. I deleted all my snaps and snapd
also to maybe reduce the boot time but it’s still very high.
The systemd-analyze blame
shows this:
29.744s systemd-journal-flush.service >
19.353s firewalld.service >
17.688s sssd.service >
13.090s udisks2.service >
11.492s dracut-initqueue.service >
10.368s abrtd.service >
9.909s ModemManager.service >
9.809s systemd-cryptsetup@luks\x2d7674d04e\x2dda04\x2d4ce5\x2da>
9.373s smartd.service >
8.669s plymouth-quit-wait.service >
8.284s gssproxy.service >
7.874s lvm2-monitor.service >
7.836s NetworkManager-wait-online.service >
7.149s systemd-udev-settle.service >
6.802s switcheroo-control.service >
5.170s initrd-switch-root.service >
2.201s systemd-fsck@dev-mapper-fedora_localhost\x2d\x2dlive\x2d>
2.119s systemd-fsck@dev-disk-by\x2duuid-127f2e8c\x2d7f30\x2d4db>
1.984s lightdm.service >
1.894s systemd-fsck@dev-disk-by\x2duuid-879A\x2dB586.service >
1.580s avahi-daemon.service >
1.443s systemd-udevd.service >
1.316s rsyslog.service >
1.148s systemd-tmpfiles-setup-dev.service >
980ms cups.service >
963ms NetworkManager.service >
896ms dmraid-activation.service >
880ms polkit.service >
837ms systemd-tmpfiles-setup.service >
808ms systemd-logind.service >
793ms systemd-vconsole-setup.service >
752ms upower.service >
745ms auditd.service >
698ms dbus-broker.service >
637ms lm_sensors.service >
536ms systemd-sysctl.service >
508ms systemd-tmpfiles-clean.service >
499ms systemd-journald.service >
472ms rtkit-daemon.service >
420ms systemd-udev-trigger.service >
416ms import-state.service >
410ms bluetooth.service >
406ms dnf-makecache.service >
404ms systemd-fsck-root.service >
397ms systemd-random-seed.service >
348ms chronyd.service >
341ms accounts-daemon.service >
333ms plymouth-read-write.service >
328ms home.mount >
313ms sssd-kcm.service >
300ms user@1000.service >
284ms plymouth-switch-root.service >
268ms systemd-modules-load.service >
268ms systemd-remount-fs.service >
250ms boot-efi.mount >
236ms initrd-parse-etc.service >
208ms colord.service >
192ms dracut-cmdline.service >
176ms dev-hugepages.mount >
176ms dev-mapper-fedora_localhost\x2d\x2dlive\x2dswap.swap >
175ms dev-mqueue.mount >
173ms sys-kernel-debug.mount >
173ms kmod-static-nodes.service >
168ms dracut-shutdown.service >
168ms boot.mount >
167ms wpa_supplicant.service >
167ms nfs-convert.service >
165ms systemd-backlight@backlight:amdgpu_bl0.service >
102ms var-lib-nfs-rpc_pipefs.mount >
63ms sysroot.mount >
56ms systemd-update-utmp.service >
49ms rpc-statd-notify.service >
44ms dracut-pre-pivot.service >
39ms livesys.service >
32ms initrd-cleanup.service >
31ms dracut-pre-udev.service >
30ms systemd-rfkill.service >
29ms user-runtime-dir@1000.service >
26ms systemd-user-sessions.service >
15ms plymouth-start.service >
14ms systemd-update-utmp-runlevel.service >
14ms initrd-udevadm-cleanup-db.service >
13ms sys-fs-fuse-connections.mount >
13ms livesys-late.service >
7ms tmp.mount >
2ms sys-kernel-config.mount >
352us iscsi-shutdown.service
Is there any way to reduce boot time and have it in like 20 - 30 seconds? Or anything.