Clean install Mint 19 Cinnamon boot question/problem

[larryw]

I've done a clean install of Mint 19 Cinnamon on notebook with 256 SSD, 8 gb ram. Kernel is 4.15.0.36-generic and all updates are applied.

Everything works ok so far except below and a minor issue I had with 18.3 has been fixed.

My issue is the slow boot. When I time it from power on to waiting for password it takes 28 seconds which seems too long. I ran systemd-analyze and it said startup finished in 4.206s (kernel) + 4.209s (userspace) = 8.415 secs.graphical target reached reached after 4.201s in userspace

Why does systemd-analyze have such a low number when actual stopwatch reports much longer.

Running systemd-analyze blame gives a long list but it runs through the startups to line 23 and the displays ...skipping... and after that it repeats the first 23 lines. It's not trying to start twice is it?

I could post the actual results but will take awhile as I've only installed it and don't even have any email, browser, etc set up.

[overkill22]

I've done a clean install of Mint 19 Cinnamon on notebook with 256 SSD, 8 gb ram. Kernel is 4.15.0.36-generic and all updates are applied.

Everything works ok so far except below and a minor issue I had with 18.3 has been fixed.

My issue is the slow boot. When I time it from power on to waiting for password it takes 28 seconds which seems too long. I ran systemd-analyze and it said startup finished in 4.206s (kernel) + 4.209s (userspace) = 8.415 secs.graphical target reached reached after 4.201s in userspace

Why does systemd-analyze have such a low number when actual stopwatch reports much longer.

Running systemd-analyze blame gives a long list but it runs through the startups to line 23 and the displays ...skipping... and after that it repeats the first 23 lines. It's not trying to start twice is it?

I could post the actual results but will take awhile as I've only installed it and don't even have any email, browser, etc set up.

I noticed the same problem. Mint 18.3 super fast. Mint 19 damn slow.
I have it for a while now, with all the programs installed, do you mind describing the process you did to get those data? I'll try to run on my laptop to see what I get.

[larryw]

My stopwatch was on my phone.

in Terminal
systemd-analyze gives a start up time
systemd-analyze blame give a detail listing of the time for each process to load

I reinstalled after I realized I'd attempted to install Wine and wondered if that had caused the delays. Unfortunately, no. The new install is the same.

Actual program load times are acceptable. It's just that I'd like to have boot faster. Or at least as fast as my Windows 10.

[overkill22]

My stopwatch was on my phone.

in Terminal
systemd-analyze gives a start up time
systemd-analyze blame give a detail listing of the time for each process to load

I reinstalled after I realized I'd attempted to install Wine and wondered if that had caused the delays. Unfortunately, no. The new install is the same.

Actual program load times are acceptable. It's just that I'd like to have boot faster. Or at least as fast as my Windows 10.

I see. I'll try my next reboot with the stopwatch. Meanwhile here my systemd-analyze

Code: Select all

$ systemd-analyze
Startup finished in 2.402s (firmware) + 11.353s (loader) + 3.771s (kernel) + 3.475s (userspace) = 21.003s
graphical.target reached after 3.465s in userspace

and the first few services to blame

Code: Select all

systemd-analyze blame
          5.379s apt-daily.service
          1.642s NetworkManager-wait-online.service
           720ms ModemManager.service
           708ms udisks2.service
           526ms apt-daily-upgrade.service
           503ms accounts-daemon.service
           502ms dev-sda2.device
           502ms networking.service
           486ms networkd-dispatcher.service
           481ms iio-sensor-proxy.service
           470ms speech-dispatcher.service
           449ms systemd-journal-flush.service
           449ms lm-sensors.service
           442ms thermald.service
           441ms pppd-dns.service
           441ms rsyslog.service
           413ms alsa-restore.service
           413ms ubuntu-system-adjustments.service
           411ms gpu-manager.service
           310ms systemd-logind.service
           291ms NetworkManager.service
           182ms colord.service
           172ms systemd-rfkill.service
           156ms systemd-timesyncd.service
           148ms apparmor.service
           139ms systemd-resolved.service
           125ms keyboard-setup.service
           119ms lightdm.service
           119ms systemd-fsck@dev-disk-by\x2duuid-D233\x2d9A73.service
           117ms plymouth-quit-wait.service
           115ms upower.service
           114ms swapfile.swap
           107ms systemd-udevd.service
           102ms systemd-udev-trigger.service

what's apt-daily.service ? Does it takes the same in your installation?

[overkill22]

My stopwatch was on my phone.

in Terminal
systemd-analyze gives a start up time
systemd-analyze blame give a detail listing of the time for each process to load

I reinstalled after I realized I'd attempted to install Wine and wondered if that had caused the delays. Unfortunately, no. The new install is the same.

Actual program load times are acceptable. It's just that I'd like to have boot faster. Or at least as fast as my Windows 10.

I see. I'll try my next reboot with the stopwatch. Meanwhile here my systemd-analyze

Code: Select all

$ systemd-analyze
Startup finished in 2.402s (firmware) + 11.353s (loader) + 3.771s (kernel) + 3.475s (userspace) = 21.003s
graphical.target reached after 3.465s in userspace

and the first few services to blame

Code: Select all

systemd-analyze blame
          5.379s apt-daily.service
          1.642s NetworkManager-wait-online.service
           720ms ModemManager.service
           708ms udisks2.service
           526ms apt-daily-upgrade.service
           503ms accounts-daemon.service
           502ms dev-sda2.device
           502ms networking.service
           486ms networkd-dispatcher.service
           481ms iio-sensor-proxy.service
           470ms speech-dispatcher.service
           449ms systemd-journal-flush.service
           449ms lm-sensors.service
           442ms thermald.service
           441ms pppd-dns.service
           441ms rsyslog.service
           413ms alsa-restore.service
           413ms ubuntu-system-adjustments.service
           411ms gpu-manager.service
           310ms systemd-logind.service
           291ms NetworkManager.service
           182ms colord.service
           172ms systemd-rfkill.service
           156ms systemd-timesyncd.service
           148ms apparmor.service
           139ms systemd-resolved.service
           125ms keyboard-setup.service
           119ms lightdm.service
           119ms systemd-fsck@dev-disk-by\x2duuid-D213\x7d4B23.service
           117ms plymouth-quit-wait.service
           115ms upower.service
           114ms swapfile.swap
           107ms systemd-udevd.service
           102ms systemd-udev-trigger.service

what's apt-daily.service ? Does it takes the same in your installation?

[larryw]

I don't have apt-daily-service showing in my list. Maybe the update app? I've disabled that one right now to see if what might be causing slow boots.

[overkill22]

I don't have apt-daily-service showing in my list. Maybe the update app? I've disabled that one right now to see if what might be causing slow boots.

I googled and this is what I found. Didn't go through all yet.

https://ubuntu-mate.community/t/shorten ... vice/12297

https://askubuntu.com/questions/800479/ ... ly-service

[overkill22]

Today my apt-daily.service took too long

Code: Select all

$ systemd-analyze blame
         19.598s apt-daily.service

Code: Select all

$ systemd-analyze
Startup finished in 2.389s (firmware) + 11.379s (loader) + 3.792s (kernel) + 22.941s (userspace) = 40.503s
graphical.target reached after 2.868s in userspace

Trying with this workaround:

sudo systemctl edit apt-daily.timer

and paste the following text into the editor window:

Code: Select all

# apt-daily timer configuration override
[Timer]
OnBootSec=15min
OnUnitActiveSec=1d
AccuracySec=1h
RandomizedDelaySec=30min

soruce: https://askubuntu.com/questions/800479/ ... ly-service

Workaround seems to be working:

Code: Select all

$ systemd-analyze blame
          1.475s NetworkManager-wait-online.service
           586ms dev-sda2.device
           576ms systemd-journal-flush.service
           354ms ubuntu-system-adjustments.service
           324ms systemd-logind.service
           237ms NetworkManager.service
           211ms networkd-dispatcher.service
           195ms apport.service
           193ms systemd-timesyncd.service
           186ms systemd-resolved.service
           182ms udisks2.service
           147ms systemd-rfkill.service
           143ms pppd-dns.service
           137ms accounts-daemon.service
           133ms systemd-hostnamed.service
           130ms thermald.service
           129ms keyboard-setup.service
           123ms lightdm.service
           119ms plymouth-quit-wait.service
           116ms ModemManager.service
           113ms upower.service
           109ms iio-sensor-proxy.service
           109ms wpa_supplicant.service

But still I'm not satisfied since the loader takes 11+ seconds:

Code: Select all

$ systemd-analyze
Startup finished in 2.157s (firmware) + 11.356s (loader) + 4.112s (kernel) + 3.076s (userspace) = 20.702s
graphical.target reached after 3.067s in userspace

I also noticed that now I don't have anymore the Asus welcome screen at the very beginning. I feel it is damn slow. In Mint 18.3 startup was around 5 seconds.
Any suggestion?

[overkill22]

After the second/third boot, I still have the sam problem

Code: Select all

$ systemd-analyze
Startup finished in 2.402s (firmware) + 11.363s (loader) + 4.136s (kernel) + 17.486s (userspace) = 35.388s
graphical.target reached after 3.075s in userspace

Code: Select all

$ systemd-analyze blame
         13.894s apt-daily.service
          1.499s NetworkManager-wait-online.service

The file was edited correctly.

I tried to edit the file in /etc/systemd/system/apt-daily.time instead as suggested here , let's see what happens in the next few boots.