Article 5RR6D Slow boot times on Kubuntu 20.04

Slow boot times on Kubuntu 20.04

by
giuuji
from LinuxQuestions.org on (#5RR6D)
I've noticed that booting into Linux takes a long time. It was like this since I installed Linux so I doubt that anything I did while using Linux resulted in slow booting.
I have two hard drives, one for Windows 10 and another for Kubuntu 20.04. I believe that one of the reasons for the slow boot times is that when I was installing Linux i unplugged my Windows 10 drive and I think that has caused some issues with Grub.
The hard drive that Linux is on is quite old and slow and the PC in general is old so I'm not excepting to boot up in under 10 seconds or something.
I ran systemd-analyze and measured boot time with a stopwatch on my phone. Here are the results.

First boot
stopwatch : 02:34
systemd-analyze : Startup finished in 5.957s (kernel) + 1min 402ms (userspace) = 1min 6.360s graphical.target reached after 58.594s in userspace
systemd-analyze blame :
33.211s man-db.service
31.407s udisks2.service
18.710s dev-sda2.device
18.678s networkd-dispatcher.service
17.797s accounts-daemon.service
11.524s NetworkManager-wait-online.service
10.971s avahi-daemon.service
10.952s NetworkManager.service
10.790s polkit.service
10.461s snapd.service
10.163s thermald.service
10.157s systemd-logind.service
10.157s wpa_supplicant.service
9.979s dev-loop0.device
9.572s dev-loop4.device
9.143s logrotate.service
8.853s dev-loop3.device
8.822s ModemManager.service
8.206s dev-loop5.device
6.985s dev-loop2.device
6.003s gpu-manager.service
4.623s systemd-resolved.service
4.522s rsyslog.service
4.481s systemd-journal-flush.service
4.345s apport.service
4.325s dev-loop1.device
3.698s packagekit.service
3.081s e2scrub_reap.service
2.988s grub-common.service
2.932s systemd-tmpfiles-setup.service
2.906s systemd-udevd.service
1.974s apparmor.service
1.567s systemd-modules-load.service
1.205s grub-initrd-fallback.service
978ms systemd-random-seed.service
954ms snapd.seeded.service
913ms pppd-dns.service
862ms alsa-restore.service
859ms keyboard-setup.service
805ms systemd-tmpfiles-setup-dev.service
774ms swapfile.swap
729ms systemd-sysusers.service
697ms systemd-sysctl.service
658ms systemd-udev-trigger.service
585ms systemd-journald.service
567ms snap-gnome\x2d3\x2d28\x2d1804-161.mount
513ms snap-core18-2246.mount

Second run
stopwatch : 02:00
systemd-analyze : Startup finished in 6.165s (kernel) + 47.689s (userspace) = 53.855s graphical.target reached after 47.676s in userspace
systemd-analyze blame :
19.958s snapd.service
19.806s dev-sda2.device
16.075s networkd-dispatcher.service
15.790s udisks2.service
13.998s accounts-daemon.service
12.496s plymouth-start.service
11.951s NetworkManager-wait-online.service
9.498s dev-loop0.device
9.478s dev-loop3.device
9.092s dev-loop5.device
8.813s dev-loop4.device
8.724s polkit.service
8.623s NetworkManager.service
8.483s dev-loop2.device
8.456s avahi-daemon.service
8.297s dev-loop6.device
7.969s thermald.service
7.967s systemd-logind.service
7.966s wpa_supplicant.service
7.756s ModemManager.service
5.554s gpu-manager.service
3.972s dev-loop1.device
3.870s systemd-journal-flush.service
3.650s packagekit.service
3.144s rsyslog.service
2.681s e2scrub_reap.service
2.595s systemd-udevd.service
2.575s apport.service
2.028s apparmor.service
1.658s grub-common.service
1.242s systemd-modules-load.service
1.171s systemd-resolved.service
887ms keyboard-setup.service
691ms systemd-tmpfiles-setup-dev.service
664ms systemd-sysusers.service
582ms systemd-sysctl.service
580ms systemd-tmpfiles-setup.service
542ms alsa-restore.service
530ms systemd-udev-trigger.service
519ms grub-initrd-fallback.service
446ms systemd-random-seed.service
417ms swapfile.swap
366ms snapd.seeded.service
344ms snapd.apparmor.service
339ms snap-bare-5.mount
331ms pppd-dns.service
314ms snap-chromium-1810.mount

Third run
stopwatch : 01:59:38
systemd-analyze : Startup finished in 5.897s (kernel) + 52.004s (userspace) = 57.902s graphical.target reached after 51.544s in userspace
systemd-analyze blame :
20.482s dev-sda2.device
19.941s snapd.service
15.252s networkd-dispatcher.service
14.922s NetworkManager-wait-online.service
14.429s udisks2.service
13.655s accounts-daemon.service
10.674s ModemManager.service
9.745s dev-loop1.device
9.664s dev-loop3.device
9.444s dev-loop4.device
9.298s polkit.service
9.100s avahi-daemon.service
9.042s NetworkManager.service
8.574s dev-loop5.device
8.396s dev-loop6.device
8.299s dev-loop2.device
8.268s systemd-logind.service
8.267s thermald.service
8.264s wpa_supplicant.service
5.452s gpu-manager.service
4.889s systemd-journal-flush.service
4.021s dev-loop0.device
3.482s packagekit.service
3.237s e2scrub_reap.service
2.999s systemd-udevd.service
2.920s rsyslog.service
2.838s apport.service
2.093s grub-common.service
2.041s apparmor.service
1.899s upower.service
1.371s systemd-modules-load.service
1.278s grub-initrd-fallback.service
1.235s systemd-resolved.service
1.032s systemd-sysctl.service
877ms alsa-restore.service
865ms keyboard-setup.service
766ms user@1000.service
724ms systemd-sysusers.service
629ms systemd-journald.service
601ms modprobe@drm.service
600ms systemd-tmpfiles-setup-dev.service
572ms pppd-dns.service
548ms systemd-udev-trigger.service
523ms systemd-tmpfiles-setup.service
469ms systemd-random-seed.service
463ms ufw.service
444ms snap-bare-5.mount

What can I do to improve the situation ?
Thank you for your help :-Dlatest?d=yIl2AUoC8zA latest?i=uQtQUSPjdJ0:PsxTZwhAgYU:F7zBnMy latest?i=uQtQUSPjdJ0:PsxTZwhAgYU:V_sGLiP latest?d=qj6IDK7rITs latest?i=uQtQUSPjdJ0:PsxTZwhAgYU:gIN9vFwuQtQUSPjdJ0
External Content
Source RSS or Atom Feed
Feed Location https://feeds.feedburner.com/linuxquestions/latest
Feed Title LinuxQuestions.org
Feed Link https://www.linuxquestions.org/questions/
Reply 0 comments