Installed Ubuntu Mate 22.04 boots in 1 min and 53 seconds can the boot be shortened?

Thoughts & Feedback
,
#1

Hi, installed Ubuntu Mate 22.04. My computer boots in 1 min and 53 seconds. can the boot be shorted?

systemd-analyze
Startup finished in 5.628s (firmware) + 7.613s (loader) + 6.640s (kernel) + 1min 13.551s (userspace) = 1min 33.434s
graphical.target reached after 1min 13.411s in userspace

~$ systemd-analyze blame
38.085s plymouth-quit-wait.service
32.832s NetworkManager-wait-online.service
21.248s systemd-journal-flush.service
16.805s dev-sda2.device
16.027s apport-autoreport.service
14.912s udisks2.service
14.280s dev-loop5.device
14.245s networkd-dispatcher.service
13.786s dev-loop9.device
13.753s dev-loop10.device
13.431s dev-loop3.device
13.083s dev-loop0.device
12.779s dev-loop2.device
12.078s dev-loop6.device
11.982s dev-loop12.device
11.908s dev-loop8.device
11.902s dev-loop11.device
11.671s dev-loop4.device
11.414s dev-loop7.device
10.283s ModemManager.service
10.182s dev-loop1.device
9.114s accounts-daemon.service
7.377s cups.service
lines 1-23...skipping...
38.085s plymouth-quit-wait.service
32.832s NetworkManager-wait-online.service
21.248s systemd-journal-flush.service
16.805s dev-sda2.device
16.027s apport-autoreport.service
14.912s udisks2.service
14.280s dev-loop5.device
14.245s networkd-dispatcher.service
13.786s dev-loop9.device
13.753s dev-loop10.device
13.431s dev-loop3.device
13.083s dev-loop0.device
12.779s dev-loop2.device
12.078s dev-loop6.device
11.982s dev-loop12.device
11.908s dev-loop8.device
11.902s dev-loop11.device
11.671s dev-loop4.device
11.414s dev-loop7.device
10.283s ModemManager.service
10.182s dev-loop1.device
9.114s accounts-daemon.service
7.377s cups.service
7.165s systemd-udevd.service
6.122s power-profiles-daemon.service
5.447s polkit.service
4.991s NetworkManager.service
4.741s avahi-daemon.service
4.315s gdm.service
4.280s switcheroo-control.service
4.269s thermald.service
4.256s systemd-logind.service
4.180s wpa_supplicant.service
3.860s apparmor.service
3.763s systemd-resolved.service
3.172s rsyslog.service
3.100s xrdp.service
3.031s gpu-manager.service
2.628s secureboot-db.service
2.566s lm-sensors.service
2.471s [email protected]
2.228s e2scrub_reap.service
2.209s systemd-rfkill.service
2.092s grub-common.service
1.813s apport.service
1.726s systemd-sysctl.service
1.274s plymouth-start.service
1.232s systemd-oomd.service
1.156s colord.service
1.138s systemd-udev-trigger.service
1.063s systemd-modules-load.service
lines 1-51

3 Likes
#2

Welcome @Bots_Emperador to the community!

#3

Hi Bots,

You can shave off a good 30 seconds by disabling 'NetworkManager-wait-online.service'

sudo systemctl disable NetworkManager-wait-online.service
sudo systemctl mask NetworkManager-wait-online.service

Also this:

10.283s ModemManager.service

Do you have an old-school dial-up modem ? If no, you can disable this.

If that is not enough, you also might want to replace some or all of your snap packages for regular packages because mounting snap-images at boot takes time (these are all the dev-loopX.device entries).

Looking at your startup times (which are really really slow), it seems you are booting from a classic mechanical harddisk. If that is so you might want to change it for an SSD which will give you a significant speed boost.

Here is the top part of my 'systemd-analyze blame' output as an indication of what a reasonable cheap NVME drive could do for your boot times:

 8.823s NetworkManager-wait-online.service
 2.028s plocate-updatedb.service
  945ms snapd.service
  606ms ufw.service
  545ms apt-daily.service
  514ms snapd.seeded.service
  478ms apt-daily-upgrade.service
  270ms man-db.service
  206ms dpkg-db-backup.service
  174ms dev-loop2.device
  174ms dev-loop1.device
  174ms dev-loop4.device
  173ms dev-loop3.device
  173ms dev-loop6.device
  170ms dev-loop5.device
  166ms dev-loop0.device
  166ms rtkit-daemon.service
  148ms dev-nvme0n1p6.device
  128ms [email protected]
  118ms apparmor.service
  108ms networkd-dispatcher.service

b.t.w.: also take a look at this:

EDIT: and this:

4 Likes
#4

Use SSD instead of mechanical HDD.

1 Like