2

Ever since I increased disk space on UBUNTU 18.04, the booting time has increased manifolds.I created new swap partition. As pointed out by other answers for similar question, I have Updated the UUID in /ext/fstab.

I ran systemd-analyze time on terminal and the output is as follows:

Startup finished in 5.395s (firmware) + 6.836s (loader) + 4.535s (kernel) + 52.819s (userspace) = 1min 9.588s
graphical.target reached after 49.244s in userspace

On running systemd-analyze critical-chain:

graphical.target @49.244s
└─multi-user.target @49.244s
  └─kerneloops.service @40.919s +26ms
    └─network-online.target @40.913s
      └─NetworkManager-wait-online.service @32.043s +8.869s
        └─NetworkManager.service @27.622s +4.420s
          └─dbus.service @27.316s
            └─basic.target @27.312s
              └─sockets.target @27.312s
                └─snapd.socket @27.249s +62ms
                  └─sysinit.target @27.249s
                    └─cryptsetup.target @26.626s
                      └─systemd-ask-password-wall.path @2.985s

That 52.819 sec is unusual. I have searched over internet many times but nothing seems to resolve this issue.

EDIT: Output of systemd-analyze blame | head -n 20

19.189s systemd-journal-flush.service   
17.967s plymouth-start.service
17.193s plymouth-quit-wait.service
13.703s dev-sdb7.device
11.145s plymouth-read-write.service
8.869s NetworkManager-wait-online.service
6.558s dev-loop23.device
6.530s dev-loop20.device
6.448s dev-loop16.device
6.398s dev-loop22.device
6.332s dev-loop15.device
6.223s dev-loop21.device
6.202s dev-loop24.device
6.194s snapd.service
6.117s dev-loop18.device
5.971s networkd-dispatcher.service
5.943s dev-loop14.device
5.880s dev-loop17.device
5.754s dev-loop19.device
5.414s dev-loop10.device
Naman
  • 21

2 Answers2

0

I have similar times on an XPS 9950 with a not partitioned 500 GB SSD (all of the HDD is dedicated to one OS). Ubuntu 17.10, 18.04 and 18.10 with Legacy boot was around your times. Now I have elementary OS Juno on UEFI and times did not changed much, I accepted it as normal even if I was expecting blazing fast boots in the Linux world.

Travis
  • 413
0

Last week I installed Xubuntu 18.04 on an old laptop and faced a similiar issue. For me the most working solution was to disable the plymouth in grub with

sudo nano /etc/default/grub

and change the line GRUB_CMDLINE_LINUX_DEFAULT into

GRUB_CMDLINE_LINUX_DEFAULT="noplymouth video=SVIDEO-1:d"

After saving the change you must update the grub with

sudo update-grub

and then restart the machine.

I tried different options to disable the plymouth, sometimes without anything in quotest (just "") or with "quiet splash" and also with "noplymouth" without the "video=SVIDEO-1:d" option. For me at least it was not working or I got additional delay time during booting by krms or similar.

Mr.Michael.Schulze
  • 557