Hello,
Very slow start, over 3 minutes...
=> cmd: sudo systemd-analyze time
Startup finished in 37.291s (kernel) + 2min 23.334s (userspace) = 3min 625ms
graphical.target reached after 2min 23.280s in userspace
After read many answers on the same slow start subjects, try few solutions without succes.
=> cmd: sudo systemd-analyze critical chain
graphical.target @2min 23.280s
└─lightdm.service @2min 22.412s +867ms
└─systemd-user-sessions.service @56.566s +494ms
└─network.target @56.562s
└─NetworkManager.service @40.913s +15.648s
└─dbus.service @32.538s
└─basic.target @31.724s
└─sockets.target @31.724s
└─snapd.socket @31.553s +170ms
└─sysinit.target @31.532s
└─snapd.apparmor.service @31.466s +64ms
└─apparmor.service @17.074s +14.228s
└─local-fs.target @17.021s
└─local-fs-pre.target @16.467s
└─keyboard-setup.service @6.033s +10.433s
└─systemd-journald.socket @6.000s
└─system.slice @5.999s
└─-.slice @5.109s
=> cmd: sudo systemd-analyze blame
1min 50.318s vboxadd.service
1min 26.211s plymouth-quit-wait.service
43.699s resolvconf-pull-resolved.service
36.044s dev-sda1.device
23.630s udisks2.service
23.536s mysql.service
23.234s snapd.service
22.225s networkd-dispatcher.service
19.626s systemd-journal-flush.service
15.648s NetworkManager.service
15.449s accounts-daemon.service
14.636s laptop-mode.service
14.228s apparmor.service
13.446s gpu-manager.service
12.104s apport.service
11.692s ModemManager.service
11.525s devolonetsvc.service
10.634s etc-setserial.service
10.433s keyboard-setup.service
9.958s lm-sensors.service
9.685s [email protected]
9.608s networking.service
9.541s console-kit-log-system-start.service
So what seems the solution at your opinion ?
(haveged solution already tested without success)
Many thanks
Laurent
Very slow start, over 3 minutes...
=> cmd: sudo systemd-analyze time
Startup finished in 37.291s (kernel) + 2min 23.334s (userspace) = 3min 625ms
graphical.target reached after 2min 23.280s in userspace
After read many answers on the same slow start subjects, try few solutions without succes.
=> cmd: sudo systemd-analyze critical chain
graphical.target @2min 23.280s
└─lightdm.service @2min 22.412s +867ms
└─systemd-user-sessions.service @56.566s +494ms
└─network.target @56.562s
└─NetworkManager.service @40.913s +15.648s
└─dbus.service @32.538s
└─basic.target @31.724s
└─sockets.target @31.724s
└─snapd.socket @31.553s +170ms
└─sysinit.target @31.532s
└─snapd.apparmor.service @31.466s +64ms
└─apparmor.service @17.074s +14.228s
└─local-fs.target @17.021s
└─local-fs-pre.target @16.467s
└─keyboard-setup.service @6.033s +10.433s
└─systemd-journald.socket @6.000s
└─system.slice @5.999s
└─-.slice @5.109s
=> cmd: sudo systemd-analyze blame
1min 50.318s vboxadd.service
1min 26.211s plymouth-quit-wait.service
43.699s resolvconf-pull-resolved.service
36.044s dev-sda1.device
23.630s udisks2.service
23.536s mysql.service
23.234s snapd.service
22.225s networkd-dispatcher.service
19.626s systemd-journal-flush.service
15.648s NetworkManager.service
15.449s accounts-daemon.service
14.636s laptop-mode.service
14.228s apparmor.service
13.446s gpu-manager.service
12.104s apport.service
11.692s ModemManager.service
11.525s devolonetsvc.service
10.634s etc-setserial.service
10.433s keyboard-setup.service
9.958s lm-sensors.service
9.685s [email protected]
9.608s networking.service
9.541s console-kit-log-system-start.service
So what seems the solution at your opinion ?
(haveged solution already tested without success)
Many thanks
Laurent