Zorin OS boot time is extremely long (4 min?!) on ssd


I just installed Zorin core for the first time on an old pc for my parents. It is great but it takes way too much time to to boot up, despite the SSD. Laptop is an asus N56V (core I7, 6Gb RAM, Geforce GT 630M 2gb VRAM). It was running windows 7 flawlessly.

lain@alain-N56VM:~$ systemd-analyze time
Startup finished in 9.008s (firmware) + 11.524s (loader) + 3.869s (kernel) + 4min 9.786s (userspace) = 4min 34.188s
graphical.target reached after 3min 59.591s in userspace

Can someone help understanding what is wrong and how I can solve this?

alain@alain-N56VM:~$ systemd-analyze blame
4min 14.214s dev-sda2.device
1min 5.070s plymouth-quit-wait.service
31.973s apt-daily-upgrade.service
30.043s user@1000.service
26.541s systemd-rfkill.service
20.197s systemd-backlight@backlight:intel_backlight.service
12.732s gpu-manager.service
11.704s networkd-dispatcher.service
11.166s systemd-resolved.service
11.017s systemd-timesyncd.service
10.591s systemd-logind.service
10.545s systemd-user-sessions.service
10.392s systemd-update-utmp.service
10.382s snapd.apparmor.service
10.107s user-runtime-dir@1000.service
10.045s apparmor.service
9.984s systemd-tmpfiles-setup.service
9.976s systemd-update-utmp-runlevel.service
9.806s snapd.seeded.service
6.479s systemd-backlight@leds:asus::kbd_backlight.service
6.141s udisks2.service
5.139s man-db.service
4.471s modprobe@efi_pstore.service

alain@alain-N56VM:~$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

> graphical.target @3min 59.591s
> └─multi-user.target @3min 59.591s
>   └─snapd.seeded.service @2min 55.234s +9.806s
>     └─basic.target @2min 948ms
>       └─sockets.target @2min 948ms
>         └─snapd.socket @2min 947ms +734us
>           └─sysinit.target @2min 943ms
>             └─systemd-backlight@backlight:intel_backlight.service @3min 16.575s +20.197s
>               └─system-systemd\x2dbacklight.slice @3min 16.574s
>                 └─system.slice @9.791s
>                   └─-.slice @9.791s


This mostly looks to me like there is difficulty communicating with the hard drive device.
I agree with you - those are abnormally high wait times.

You might start out by just wiping and reinstalling Zorin OS. Sometimes, a simple reinstall works wonders.
You might check your BIOS /EFI settings ensuring you are set to AHCI and not RAID - and looking for any other manufacturer specific drive settings.

If readily available as an option, I would also reseat the hard drive after cleaning the contacts (hopefully it is NVMe and not a soldered in eMMC...)

I looked into the N56V model and it appears that the storage is HDD. The specifications may be different in your country, but it's worth checking again. Windows can speed up the boot by compressing data if the CPU is fast and the storage is slow, which may be the difference from Zorin OS.


Thank you both for the quick reply.

Indeed, the laptop was initially sold with a hdd but if I remember well I swapped it myself for a SSD. I hope I'm not mistaken we've had several laptops these past 10 years... I was sure this was a SSD because it is completely silent and Windows was booting in 20 sec. I'm gonna have to open the beast to be sure.

But still this looks abnormal, even for a HDD isn't it?

About reinstalling, I'll give a try to Zorin Lite maybe to see if it makes any difference...

Thanks again, will keep the community posted.

1 Like

Seems to be a HDD after all :

alain@alain-N56VM:~$ cat /sys/block/sda/queue/rotational

I'll try installing Zorin OS Lite...

1 Like

All right ! Much better now with Zorin Lite. Not sure what the problem was exactly with the HHD but it looks quite normal now IMO.

Don't know if it will help someone but worth trying if you are in the same situation

alain@alain-N56VM:~$ systemd-analyze time
Startup finished in 8.494s (firmware) + 6.987s (loader) + 4.059s (kernel) + 1min 12.121s (userspace) = 1min 31.662s 
graphical.target reached after 1min 11.803s in userspace
alain@alain-N56VM:~$ systemd-analyze blame
34.382s snapd.seeded.service                                 
34.382s snapd.seeded.service                                 
13.187s plymouth-quit-wait.service                           
12.367s gpu-manager.service                                  
10.574s systemd-rfkill.service                               
 7.999s NetworkManager-wait-online.service                   
 7.782s dev-sda2.device                                      
 7.343s apparmor.service                                     
 5.339s blueman-mechanism.service                            
 4.972s networkd-dispatcher.service                          
 4.677s modprobe@efi_pstore.service                          
 3.930s systemd-backlight@leds:asus::kbd_backlight.service   
 3.611s systemd-backlight@backlight:intel_backlight.service  
 3.364s udisks2.service                                      
 3.204s systemd-udev-trigger.service                         
 3.090s systemd-journald.service                             
 2.982s systemd-modules-load.service                         
1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.