I've got a problem with Ubuntu 16.04 (fresh install beside Windows 10 installation) boot taking a very long time on my Samsung 850 EVO SSD - almost 1 minute.
The story goes like this:
- GRUB menu shows up
- after I hit enter, for about 40 seconds I can only see a default purple GRUB's background (without a menu)
- looking at the IO/disk diode I can clearly see that my disk is under heavy load during that period
- after that, the screen is turned off and on (like at the beginning of a typical reboot) and Ubuntu login screen shows up
dmesg/system log - here's the important fragment:
(...) Aug 8 19:27:15 MS-7586 systemd: Starting Unattended Upgrades Shutdown... Aug 8 19:27:15 MS-7586 systemd: Stopping Daemon for power management... Aug 8 19:27:15 MS-7586 systemd: Stopping Disk Manager... Aug 8 19:27:15 MS-7586 systemd: Stopping Session c2 of user sokol. Aug 8 19:27:15 MS-7586 rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="2378" x-info="http://www.rsyslog.com"] exiting on signal 15. Aug 8 19:31:05 MS-7586 rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="2357" x-info="http://www.rsyslog.com"] start Aug 8 19:31:05 MS-7586 rsyslogd-2222: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ] Aug 8 19:31:05 MS-7586 rsyslogd: rsyslogd's groupid changed to 108 Aug 8 19:31:05 MS-7586 rsyslogd: rsyslogd's userid changed to 104 Aug 8 19:31:05 MS-7586 systemd-modules-load: Inserted module 'lp' Aug 8 19:31:05 MS-7586 systemd-modules-load: Inserted module 'ppdev' Aug 8 19:31:05 MS-7586 systemd-modules-load: Inserted module 'parport_pc' (...)
debug kernel parameter to 'Ubuntu' GRUB entry during that reboot)
The interesting thing is that 19:30:22 (7:30:22 PM) was the time when I've selected 'Ubuntu' in the GRUB menu. I've seen Ubuntu login screen at 19:31:08. In other words, that ~40 seconds "freeze" during the boot time is not recorded in the system log.
systemd-analyze output confirms that Ubuntu startup itself is pretty fast and does not take part in that ~40 seconds period:
Startup finished in 4.704s (kernel) + 1.709s (userspace) = 6.414s
When it comes to GRUB, I've tried:
as well as the default value. No difference.
Also, UUIDs from the
blkid match those listed in
Apart from these boot issues, I cannot see any problems with the SSD in general (currently it's the only disk I'm using). I hadn't got any problem with unusually long boot time while using my previous HDD, before I've upgraded to SSD.
Haven't done anything with my BIOS (updates etc.) since then.
Many thanks for any suggestions!
GRUB_CMDLINE_LINUX_DEFAULT as suggested by @ByteCommander, but - as expected - it doesn't change much. Now I just don't need to hit Esc to see the log while the system is booting.
Nothing interesting at
/var/log/Xorg.0.log either. X Window starts - as expected - after the initial boot stuff, while the freeze occurs way before that...
GRUB_CMDLINE_LINUX_DEFAULT set to
quiet), before first
systemd output line appears on a screen during the boot, there is ~38 second freeze (purple background + high disk load).