12/7/21, 1:05 PM How to diagnose/fix very slow boot on Ubuntu 18.

04 - Ask Ubuntu

Ask Ubuntu is a question and answer site

for Ubuntu users and developers. It only
takes a minute to sign up.

Sign up to join this community

Anybody can ask a question

Anybody can answer

The best answers are voted

up and rise to the top

How to diagnose/fix very slow boot on Ubuntu 18.04

Asked 3 years, 7 months ago Active 1 year, 4 months ago Viewed 136k times

There is a long time where SSD does nothing.

61 How can I find the fault and fix it ?

Already checked /etc/fstab , no swap or anything wrong there (32GB of RAM, no swap)

[ 2.173492] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
29 [ 2.173497] usb 2-1.6: Product: DW375 Bluetooth Module
[ 2.173501] usb 2-1.6: Manufacturer: Dell Computer Corp
[ 2.173511] usb 2-1.6: SerialNumber: 7CE9D3C0713B
[ 2.323728] ata4: SATA link down (SStatus 0 SControl 300)
[ 2.441062] input: AlpsPS/2 ALPS GlidePoint as
/devices/platform/i8042/serio1/input/input6
[ 2.640309] ata5: SATA link down (SStatus 0 SControl 300)
[ 2.954947] ata6: SATA link down (SStatus 0 SControl 300)
[ 3.068090] clocksource: Switched to clocksource tsc
[ 36.584826] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts:
(null)
[ 36.726117] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 36.732610] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +AC
L +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-
hierarchy=hybrid)
[ 36.751996] systemd[1]: Detected architecture x86-64.
[ 36.753867] systemd[1]: Set hostname to <latitude-e5520>.
[ 36.868561] systemd[1]: Started Forward Password Requests to Wall Directory
Watch.
[ 36.868594] systemd[1]: Reached target Remote File Systems.
[ 36.868751] systemd[1]: Created slice User and Session Slice.
[ 36.868869] systemd[1]: Created slice System Slice.
[ 36.868948] systemd[1]: Listening on udev Control Socket.
[ 36.868957] systemd[1]: Reached target Slices.
[ 36 868996] systemd[1]: Listening on udev Kernel Socket
https://askubuntu.com/questions/1030867/how-to-diagnose-fix-very-slow-boot-on-ubuntu-18-04 1/5
12/7/21, 1:05 PM How to diagnose/fix very slow boot on Ubuntu 18.04 - Ask Ubuntu
[ 36.868996] systemd[1]: Listening on udev Kernel Socket.
[ 36.895156] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[ 36.898185] lp: driver loaded but no devices found
[ 36.903941] ppdev: user-space parallel port driver

boot 18.04

Share Improve this question edited Jul 29 '18 at 18:37 asked May 2 '18 at 4:31
Follow wjandrea user105939
12.8k 4 42 87 1,189 4 13 23

3 Is this a fresh install? with lvm? perhaps this bug :

bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1768230 ? – pim May 2 '18 at 4:53

To see the WARNING:Failed to connect to lvmetad. Falling back to device scanning.

message, you should disable the spash/quiet boot (see : askubuntu.com/a/289/454520) – pim May 2
'18 at 5:46

It's about long network.service booting. Solution from this answer helped me. – gyr9i Jun 6 '18 at 7:59

6 Answers Active Oldest Votes

I upgraded to 18.04 today and encountered the same issue. I was able to fix it by booting the
kernel with the noresume parameter.
75
Like you, I also have no swap space. At some point during the upgrade, the initramfs config
was modified, adding a line pointing to a nonexistent swap partition. The slow boot was
because it was looking for this partition and then timing out after 30 seconds.

To update GRUB so that it passes this option to the kernel automatically on boot:

1. Edit the file /etc/default/grub file so that the string noresume is included in the
GRUB_CMDLINE_LINUX_DEFAULT line, for example:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noresume"

2. Run this command to update GRUB:

sudo update-grub

3. Reboot the computer

Share Improve this answer edited May 9 '18 at 15:24 answered May 3 '18 at 18:08
Follow Zanna ♦ Clifforus
64.7k 53 190 309 866 5 2

3 noresume fixed it, nothing strange in initramfs. – user105939 May 4 '18 at 7:15

2 I upgraded to 18.04 yesterday and I had the same problem (it took 52 seconds to boot). After setting
the "noresume" parameter it took 21 seconds Erol May 4 '18 at 15:06
https://askubuntu.com/questions/1030867/how-to-diagnose-fix-very-slow-boot-on-ubuntu-18-04 2/5
12/7/21, 1:05 PM How to diagnose/fix very slow boot on Ubuntu 18.04 - Ask Ubuntu
the noresume parameter, it took 21 seconds. – Erol May 4 18 at 15:06

2 You could improve your already good answer with instructions on updating grub. – WinEunuuchs2Unix
May 9 '18 at 0:44

12 Please note that this is a workaroud, since it will prevent resuming a hibernated system. – pim May 9
'18 at 13:52

4 I'm worried that this might prevent me from using hibernation. However this worked for me:
askubuntu.com/questions/1013830/… (editing /etc/initramfs-tools/conf.d/resume, changing
RESUME=none from the UUID and running update-initramfs -u) – Grey Panther Jul 11 '18 at 20:33

$ systemd-analyze blame

29
Look to see which processes are taking the most time of the boot process.

Share Improve this answer edited May 2 '18 at 22:47 answered May 2 '18 at 5:24

Follow fosslinux mgh

3,557 3 25 43 453 3 5

9 systemd-analyze blame will not show kernel time, and for this problem. systemd-analyse time
will show that it's the kernel that is stuck searching for the filesystem. – pim May 2 '18 at 5:36

2 good hint, but the longest process took only 1.6seconds, so this tool did not help. – user105939 May
4 '18 at 7:16

6 @Pim systemd-analyse time has a typo, it should have a z – Rob Audenaerde Nov 20 '18 at
8:18

2 systemd-analyze critical-chain is even better than blame – user535733 Dec 9 '18 at 22:14

below is the output for blame...now how do i improve the time runs of the longest running jobs ??
systemd-analyze blame 22.866s systemd-journal-flush.service 22.844s dev-sda1.device 16.689s
ufw.service 16.041s systemd-modules-load.service 15.367s keyboard-setup.service 13.714s systemd-
tmpfiles-setup-dev.service 9.229s NetworkManager-wait-online.service 7.599s snapd.service rest are
lesser than 6 seconds. pls guide, i'm a newbie – EetSandhu Mar 7 '20 at 5:27

What worked for me was to run sudo rm /etc/initramfs-tools/conf.d/resume followed by

sudo update-initramfs -u . This seems to be a regression from an upgrade (see
14 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861151).

Share Improve this answer edited May 15 '18 at 6:26 answered May 15 '18 at 6:17
Follow fosslinux user7081858
3,557 3 25 43 149 2

Worked great. Seems cleaner to me than adding the "noresume" kernel argument to GRUB (which also
worked). – hackerb9 May 18 '20 at 5:55

I upgraded to 18.04 from 16.04. Boot time was more than 10 minutes.
Tried from "No splash screen to Kernel" to find which processes are taking the most time for
10
https://askubuntu.com/questions/1030867/how-to-diagnose-fix-very-slow-boot-on-ubuntu-18-04 3/5
12/7/21, 1:05 PM How to diagnose/fix very slow boot on Ubuntu 18.04 - Ask Ubuntu
10 booting.

A start job is running for Raise network interfaces (1min 26s / 5min 24s)

So, we need to reduce time for this process to save boot time. To do so,

You have to edit,

sudo nano /etc/systemd/system/network-online.target.wants/networking.service

Find

TimeoutStartSec=5min

Change to

TimeoutStartSec=5s

and reboot

Share Improve this answer edited Jul 7 '18 at 19:49 answered May 10 '18 at 6:22

Follow lrkwz krige

296 2 18 172 1 9

1 This is where my boot was burning a lot of time, so this solution worked for me. +1 – Gnawme Nov 13
'19 at 0:42

1 It was my case... Just I had to insert the line in /etc/systemd/system/network-

online.target.wants/NetworkManager-wait-online.service file, under [Service] because
it wasn't already there. I'm on Lubuntu 20.04. thank you – funder7 Aug 21 '20 at 12:23

You can configure the timeout for Start Job and Stop Jobs.

6 Edit /etc/systemd/system.conf with elevated privileges and change/add two lines that are
commented by default from 90 seconds to 5 (or whatever you prefer) and uncomment it:

from:

#DefaultTimeoutStartSec=90s
#DefaultTimeoutStopSec=90s

to:

DefaultTimeoutStartSec=5s
DefaultTimeoutStopSec=5s

After that apply the changes by rebuilding your initramfs with the command:
https://askubuntu.com/questions/1030867/how-to-diagnose-fix-very-slow-boot-on-ubuntu-18-04 4/5
12/7/21, 1:05 PM How to diagnose/fix very slow boot on Ubuntu 18.04 - Ask Ubuntu
After that, apply the changes by rebuilding your initramfs with the command:

sudo update-initramfs -u

Share Improve this answer edited May 29 '19 at 21:41 answered Jan 27 '19 at 17:33

Follow Byte Commander ♦ markackerman8-

97.4k 40 257 395 gmail.com
1,947 20 17

this solved my problem after doing Gparted repartition operations on SSD drive which took notably
longer boot time otherwise. – doctorate Mar 6 '20 at 9:24

Not always work. On the contrary: system need to be restart in recovery mode and redo the changes.
– Julien Chau Mar 16 at 10:53

I tried a different method but nothing it worked. then I find it was the graphics driver issue. I
solved by using additional drivers for me it was Nvidia.
0
goto: software & updates -> choose listed graphics driver -> apply changes

Note: I am using kernel version 4.18.0-25-generic

Share Improve this answer Follow answered Jul 1 '19 at 16:05

habibun
603 1 7 17

Highly active question. Earn 10 reputation (not counting the association bonus) in order to answer this
question. The reputation requirement helps protect this question from spam and non-answer activity.

https://askubuntu.com/questions/1030867/how-to-diagnose-fix-very-slow-boot-on-ubuntu-18-04 5/5