Slow Boot LM 18.3

[64dodge]

tim@tim-Satellite-C55t-A ~ $ systemd-analyze
Startup finished in 5.434s (kernel) + 1min 45.923s (userspace) = 1min 51.357s
tim@tim-Satellite-C55t-A ~ $ systemd-analyze blame
1min 17.450s vboxadd.service
1min 6.755s plymouth-quit-wait.service
24.529s dev-sda1.device
18.619s lvm2-monitor.service
17.230s systemd-udevd.service
15.716s systemd-sysctl.service
11.557s ModemManager.service
11.100s accounts-daemon.service
10.977s grub-common.service
9.371s NetworkManager.service
9.344s loadcpufreq.service
9.334s ntp.service
9.333s gpu-manager.service
9.333s rsyslog.service
9.168s snapd.service
9.158s irqbalance.service
5.504s apparmor.service
3.041s iio-sensor-proxy.service
2.961s systemd-modules-load.service
2.838s console-setup.service
2.701s thermald.service
2.321s avahi-daemon.service
2.194s keyboard-setup.service

vboxadd.service & plymouth-quit-wait.service is so long.
I use virtual box to run xp as a guest with mint cinnamon 18.3 as host.
How can I fix this to speed up boot times?

[64dodge]

My update manager just came up with a kernel update 4.15.0-29.31 16.04.1
Would this one be good?

[64dodge]

I went to update manager / view / linux kernel
At the top was
You are currently using the following kernel: 4.13.0-15

tim@tim-Satellite-C55t-A ~ $ uname -r
4.13.0-45-generic

[smurphos]

Try it and see. You can roll back fairly easily if not.

If you are on kernel 4.13 I don't think the kernel is the cause of the issue.

What version of Vbox are you using?

[64dodge]

Vbox Version 5.2.12 r122591 (Qt5.6.1)

I upgraded the kernel, it made it faster than it has been the last couple months
but not as fast as the first few months after fresh install of 18.3

tim@tim-Satellite-C55t-A ~ $ uname -a
Linux tim-Satellite-C55t-A 4.15.0-29-generic #31~16.04.1-Ubuntu SMP Wed Jul 18 08:54:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
tim@tim-Satellite-C55t-A ~ $ systemd-analyze blame
27.228s dev-sda1.device
26.753s vboxadd.service
19.360s plymouth-quit-wait.service
16.529s systemd-udevd.service
14.573s grub-common.service
14.013s snapd.service
9.652s ModemManager.service
7.622s loadcpufreq.service
7.562s apparmor.service
7.138s ntp.service
5.285s NetworkManager.service
4.379s accounts-daemon.service
4.272s thermald.service
4.100s lvm2-monitor.service
3.577s gpu-manager.service
3.481s vboxdrv.service
3.401s console-setup.service
3.230s iio-sensor-proxy.service
3.185s ondemand.service
3.176s hddtemp.service
2.949s irqbalance.service
2.687s networking.service
2.379s systemd-sysctl.service
2.366s systemd-modules-load.service
2.186s keyboard-setup.service
1.995s console-kit-log-system-start.service
1.978s systemd-journald.service
1.869s systemd-tmpfiles-setup-dev.service
1.711s alsa-restore.service
1.704s rsyslog.service
1.484s avahi-daemon.service
1.393s binfmt-support.service
1.370s systemd-tmpfiles-setup.service
1.333s polkitd.service
1.021s lm-sensors.service
940ms dev-mqueue.mount
937ms sys-kernel-debug.mount
936ms dev-hugepages.mount
753ms dns-clean.service
749ms openvpn.service
746ms wpa_supplicant.service
731ms systemd-rfkill.service
692ms systemd-update-utmp.service
682ms colord.service
lines 1-44

[smurphos]

Try a newer vbox version. The current is 5.2.16.

[64dodge]

Upgraded vbox Version 5.2.16 r123759 (Qt5.6.1)

No change

[smurphos]

I'm a bit confused why you have vboxadd.service running on the host at all.

It doesn't exist on my system running VBox 5.2.16 on Mint 19 (Linux Guests only)

Can you report back the output of dpkg -l | grep virtualbox

[Flemur]

I use virtual box to run xp as a guest with mint cinnamon 18.3 as host.

I guessed Cinnamon when I saw your slow 'service' times:

Yours: 5.504s apparmor.service vs mine
Mine: 172ms apparmor.service

Yours: 9.371s NetworkManager.service
Mine: 305ms NetworkManager.service

How can I fix this to speed up boot times?

Other than not using Cinnamon, dunno!

Usually services in the "Services w/Cinnamon take 10 to 20 times longer to start than they should" syndrome are 10 to 20 times slower, but yours are 30 times slower (my machine is a 8-year-old low-end eMachines).

Edit:
You can start vboxadd.service (and any other vbox service) just before you need them; it's silly to start them at boot unless you always run vbox.

You don't need
ModemManager.service

And ...
1min 6.755s plymouth-quit-wait.service vs 12ms plymouth-quit-wait.service
Yikes!

[64dodge]

smurphos

tim@tim-Satellite-C55t-A ~ $ dpkg -l | grep virtualbox
ii virtualbox-5.2 5.2.16-123759~Ubuntu~xenial
amd64 Oracle VM VirtualBox


Flemur

Yes this is an old Toshiba Satellite laptop with 2.13ghz dual core celeron

You can start vboxadd.service (and any other vbox service) just before you need them; it's silly to start them at boot unless you always run vbox.

You don't need
ModemManager.service

How do you turn them off or on?

[64dodge]

I may just try Mate to see.