07-05-2018, 03:57 AM
Hey Jerry,
I took your advice and bought a new SSD. I even bumped up RAM to a whopping 3GB. :
However boot time is still sloooooooooooooow!
Here's the current analysis:
systemd-analyze blame
1min 11.601s plymouth-quit-wait.service
40.464s vboxadd.service
31.669s lightdm.service
5.029s NetworkManager-wait-online.service
3.071s dev-sda1.device
1.036s networkd-dispatcher.service
875ms ufw.service
756ms motd-news.service
739ms lm-sensors.service
714ms networking.service
567ms upower.service
546ms udisks2.service
540ms apparmor.service
525ms NetworkManager.service
507ms systemd-rfkill.service
487ms apport.service
469ms grub-common.service
442ms systemd-udev-trigger.service
415ms keyboard-setup.service
373ms pppd-dns.service
371ms ModemManager.service
367ms thermald.service
355ms accounts-daemon.service
354ms ubiquity.service
332ms systemd-udevd.service
330ms gpu-manager.service
308ms systemd-journald.service
290ms swapfile.swap
279ms rsyslog.service
269ms systemd-journal-flush.service
222ms wpa_supplicant.service
210ms avahi-daemon.service
178ms systemd-resolved.service
178ms systemd-modules-load.service
164ms systemd-timesyncd.service
145ms systemd-logind.service
129ms lvm2-monitor.service
120ms smbd.service
109ms packagekit.service
100ms [email protected]
100ms systemd-sysctl.service
93ms nmbd.service
90ms polkit.service
70ms blk-availability.service
67ms dev-mqueue.mount
65ms systemd-tmpfiles-setup.service
64ms dev-hugepages.mount
59ms systemd-remount-fs.service
55ms kmod-static-nodes.service
53ms sys-kernel-debug.mount
40ms hddtemp.service
39ms systemd-tmpfiles-setup-dev.service
38ms plymouth-start.service
37ms dns-clean.service
35ms systemd-random-seed.service
34ms iio-sensor-proxy.service
32ms resolvconf.service
31ms console-kit-daemon.service
30ms systemd-user-sessions.service
27ms console-setup.service
27ms sys-kernel-config.mount
27ms systemd-update-utmp.service
27ms systemd-tmpfiles-clean.service
26ms resolvconf-pull-resolved.service
25ms sys-fs-fuse-connections.mount
21ms bluetooth.service
19ms openvpn.service
16ms plymouth-read-write.service
14ms console-kit-log-system-start.service
13ms ureadahead-stop.service
13ms systemd-backlight@backlight:acpi_video0.serv
8ms systemd-backlight@backlight:intel_backlight.
8ms systemd-update-utmp-runlevel.service
7ms rtkit-daemon.service
7ms setvtrgb.service
lines 60-75/75 (END)
27ms console-setup.service
27ms sys-kernel-config.mount
27ms systemd-update-utmp.service
27ms systemd-tmpfiles-clean.service
26ms resolvconf-pull-resolved.service
25ms sys-fs-fuse-connections.mount
21ms bluetooth.service
19ms openvpn.service
16ms plymouth-read-write.service
14ms console-kit-log-system-start.service
13ms ureadahead-stop.service
13ms systemd-backlight@backlight:acpi_video0.serv
8ms systemd-backlight@backlight:intel_backlight.
8ms systemd-update-utmp-runlevel.service
7ms rtkit-daemon.service
systemd-analyze critical-chain
The time after the unit is active or started is printed after
The time the unit takes to start is printed after the "+" cha
The time after the unit is active or started is printed after
The time the unit takes to start is printed after the "+" cha
graphical.target @1min 13.708s
└─lightdm.service @42.038s +31.669s
└─systemd-user-sessions.service @2.034s +30ms
└─network.target @2.028s
└─NetworkManager.service @1.502s +525ms
└─dbus.service @1.392s
└─basic.target @1.258s
└─paths.target @1.258s
└─resolvconf-pull-resolved.path @1.250s
└─sysinit.target @1.234s
└─systemd-backlight@backlight:intel_backlig
└─system-systemd\x2dbacklight.slice @2.32
Any suggestions?
I took your advice and bought a new SSD. I even bumped up RAM to a whopping 3GB. :
However boot time is still sloooooooooooooow!
Here's the current analysis:
systemd-analyze blame
1min 11.601s plymouth-quit-wait.service
40.464s vboxadd.service
31.669s lightdm.service
5.029s NetworkManager-wait-online.service
3.071s dev-sda1.device
1.036s networkd-dispatcher.service
875ms ufw.service
756ms motd-news.service
739ms lm-sensors.service
714ms networking.service
567ms upower.service
546ms udisks2.service
540ms apparmor.service
525ms NetworkManager.service
507ms systemd-rfkill.service
487ms apport.service
469ms grub-common.service
442ms systemd-udev-trigger.service
415ms keyboard-setup.service
373ms pppd-dns.service
371ms ModemManager.service
367ms thermald.service
355ms accounts-daemon.service
354ms ubiquity.service
332ms systemd-udevd.service
330ms gpu-manager.service
308ms systemd-journald.service
290ms swapfile.swap
279ms rsyslog.service
269ms systemd-journal-flush.service
222ms wpa_supplicant.service
210ms avahi-daemon.service
178ms systemd-resolved.service
178ms systemd-modules-load.service
164ms systemd-timesyncd.service
145ms systemd-logind.service
129ms lvm2-monitor.service
120ms smbd.service
109ms packagekit.service
100ms [email protected]
100ms systemd-sysctl.service
93ms nmbd.service
90ms polkit.service
70ms blk-availability.service
67ms dev-mqueue.mount
65ms systemd-tmpfiles-setup.service
64ms dev-hugepages.mount
59ms systemd-remount-fs.service
55ms kmod-static-nodes.service
53ms sys-kernel-debug.mount
40ms hddtemp.service
39ms systemd-tmpfiles-setup-dev.service
38ms plymouth-start.service
37ms dns-clean.service
35ms systemd-random-seed.service
34ms iio-sensor-proxy.service
32ms resolvconf.service
31ms console-kit-daemon.service
30ms systemd-user-sessions.service
27ms console-setup.service
27ms sys-kernel-config.mount
27ms systemd-update-utmp.service
27ms systemd-tmpfiles-clean.service
26ms resolvconf-pull-resolved.service
25ms sys-fs-fuse-connections.mount
21ms bluetooth.service
19ms openvpn.service
16ms plymouth-read-write.service
14ms console-kit-log-system-start.service
13ms ureadahead-stop.service
13ms systemd-backlight@backlight:acpi_video0.serv
8ms systemd-backlight@backlight:intel_backlight.
8ms systemd-update-utmp-runlevel.service
7ms rtkit-daemon.service
7ms setvtrgb.service
lines 60-75/75 (END)
27ms console-setup.service
27ms sys-kernel-config.mount
27ms systemd-update-utmp.service
27ms systemd-tmpfiles-clean.service
26ms resolvconf-pull-resolved.service
25ms sys-fs-fuse-connections.mount
21ms bluetooth.service
19ms openvpn.service
16ms plymouth-read-write.service
14ms console-kit-log-system-start.service
13ms ureadahead-stop.service
13ms systemd-backlight@backlight:acpi_video0.serv
8ms systemd-backlight@backlight:intel_backlight.
8ms systemd-update-utmp-runlevel.service
7ms rtkit-daemon.service
systemd-analyze critical-chain
The time after the unit is active or started is printed after
The time the unit takes to start is printed after the "+" cha
The time after the unit is active or started is printed after
The time the unit takes to start is printed after the "+" cha
graphical.target @1min 13.708s
└─lightdm.service @42.038s +31.669s
└─systemd-user-sessions.service @2.034s +30ms
└─network.target @2.028s
└─NetworkManager.service @1.502s +525ms
└─dbus.service @1.392s
└─basic.target @1.258s
└─paths.target @1.258s
└─resolvconf-pull-resolved.path @1.250s
└─sysinit.target @1.234s
└─systemd-backlight@backlight:intel_backlig
└─system-systemd\x2dbacklight.slice @2.32
Any suggestions?