I have installed Kubuntu 20.04 on several external SSDs and the boot time is about 80 seconds. Kubuntu 18.04 took around 15 seconds to boot and I would like to get closer to that.

Using my 20.04, from the grub menu I select Advanced, then the first item, then I can see loading the vmlinuz image takes 7 seconds (its 11 MB under /boot), loading the initrd.img about 60 seconds (83 MB under /boot), and then there is about 15 seconds of module loading until the graphics screen appears.

I have tried rebuilding initramfs using update-initramfs -c -k $(uname -r) but this has no effect. I have tried the 5.8 kernel and that made no difference. The delay per MB is about the same for loading vmlinuz and initrd. The SSDs have included a T3 and a T5. Could it be a block size issue? Any ideas as to what is causing the delay or how to fix it?

The output from systemd-analyze blame | head is-

30.238s apt-daily-upgrade.service
30.222s apt-daily.service
7.029s NetworkManager-wait-online.service
3.493s udisks2.service
2.754s snapd.service
2.694s networkd-dispatcher.service
2.550s accounts-daemon.service
1.988s dev-sda2.device
1.715s polkit.service
1.700s avahi-daemon.service

The output from systemd-analyze critical-

graphical.target @12.190s └─multi-user.target @12.190s └─kerneloops.service @12.164s +25ms └─network-online.target @12.158s └─NetworkManager-wait-online.service @5.128s +7.029s └─NetworkManager.service @3.438s +1.683s └─dbus.service @3.431s └─basic.target @3.396s └─sockets.target @3.395s └─snapd.socket @3.391s +2ms └─sysinit.target @3.353s └─snapd.apparmor.service @3.311s +40ms └─apparmor.service @3.113s +189ms └─local-fs.target @3.111s └─run-user-1000.mount @9.224s └─local-fs-pre.target @1.310s └─systemd-tmpfiles-setup-dev.service @1.185s +123ms └─systemd-sysusers.service @1.123s +59ms └─systemd-remount-fs.service @1.069s +30ms └─systemd-fsck-root.service @1.017s +48ms └─systemd-journald.socket @970ms └─system.slice @935ms └─-.slice @935ms

  • I am not 100% on K but can you open a terminal and type systemd-analyze blame | head then post the result please? Feb 8, 2021 at 7:49
  • I have added this output to the original question. Feb 9, 2021 at 3:25

1 Answer 1


To remove the 2x30 second boot process for apt
open a terminal and type

sudo systemctl disable apt-daily.service
sudo systemctl disable apt-daily.timer

sudo systemctl disable apt-daily-upgrade.timer
sudo systemctl disable apt-daily-upgrade.service

Assumung systemctl works in Kubuntu which I am unable to test ATM.
  • Thanks, this did remove the two 30 second tasks, but the boot time remains the same with "Loading the initial RAM disk" taking 60 seconds. Feb 10, 2021 at 3:07
  • It's not unusual if you have lots of modules so unless you are having other problems I wouldn't worry. And remember that the systemd-analyze includes the time it takes to type your password. So you could go hunting for modules using 'dmesg' or you could try 'sudo time update-initramfs -u' after you backup. Feb 10, 2021 at 6:20
  • Thanks Darth. the update-initramfs did not change anything. The 60 second delay comes after the message about loading the initial RAM disk, can modules be loaded at this point or is the only thing happening loading of the ram disk? Feb 11, 2021 at 9:30
  • I am sure this is because grub is not on the SSD but it is not a problem it's just a slow boot. Unless you want to reload and configure grub you can live with it and no harm is done. You could experiment with some of the grub paramaters at GRUB_CMDLINE_LINUX_DEFAULT= and start with quietsplash etc and note the differences. Feb 11, 2021 at 10:52
  • Thanks again, the only disk in the system is the external disk. Loading of vmlinuz and then the initial ram disk take place at about 1.5 MB/sec from a drive capable of hundreds of MB/sec. This seems very odd. Feb 15, 2021 at 6:29

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .