Page 1 of 1

[SOLVED] excessively slow startup > 3 mins in "userspace"

Posted: Mon Apr 03, 2017 4:55 pm
by bbaker6212
I have had this problem for a long time, many kernels have been installed/removed since. I think this problem was caused by Grub Customizer which I no longer use.
How do I understand what/why 3 minutes is being used in "userspace"? ideas? How can I capture more detailed logs?

brad@G50 ~ $ systemd-analyze
Startup finished in 2.327s (firmware) + 8.474s (loader) + 7.303s (kernel) + 3min 268ms (userspace) = 3min 18.374s

brad@G50 ~ $ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character. @1min 38.974s
└─ @1min 38.974s
└─vboxweb-service.service @1min 38.953s +9ms
└─ @1min 30.234s
└─ @1min 30.234s
└─snapd.socket @1min 30.232s +1ms
└─ @1min 30.226s
└─apparmor.service @1.314s +188ms
└─ @1.293s
└─run-user-1000-gvfs.mount @1min 49.299s
└─run-user-1000.mount @1min 48.591s
└─ @648ms
└─lvm2-monitor.service @242ms +405ms
└─lvm2-lvmetad.service @324ms
└─lvm2-lvmetad.socket @241ms
└─-.slice @215ms
brad@G50 ~ $ systemd-analyze blame
8.633s vboxdrv.service
6.214s NetworkManager-wait-online.service
1.109s libvirt-bin.service
983ms nmbd.service
921ms dev-sda5.device
886ms samba-ad-dc.service
683ms smbd.service
405ms lvm2-monitor.service
358ms ModemManager.service
352ms ufw.service
286ms console-setup.service
277ms upower.service
241ms systemd-logind.service
228ms accounts-daemon.service
222ms systemd-rfkill.service
195ms udisks2.service
188ms apparmor.service
176ms systemd-udev-trigger.service
176ms loadcpufreq.service
173ms NetworkManager.service
170ms lm-sensors.service
169ms alsa-restore.service
165ms keyboard-setup.service
155ms avahi-daemon.service
154ms qemu-kvm.service
148ms console-kit-log-system-start.service
146ms grub-common.service
140ms binfmt-support.service
139ms rpcbind.service
137ms teamviewerd.service
122ms networking.service
121ms gpu-manager.service
111ms irqbalance.service
99ms systemd-journald.service
97ms user@1000.service
96ms systemd-fsck@dev-disk-by\x2duuid-72B0\x2d4A46.service
95ms mnt-mmc\x2d00000_0x0000700f\x2dpart1.mount
90ms proc-fs-nfsd.mount
88ms ondemand.service
87ms ebtables.service
85ms pppd-dns.service
82ms thermald.service
79ms virtualbox-guest-utils.service
73ms mnt-24CEB549CEB513D0.mount
65ms systemd-modules-load.service
61ms systemd-tmpfiles-setup.service
60ms snapd.autoimport.service
56ms rsyslog.service
56ms plymouth-quit.service
55ms run-rpc_pipefs.mount
55ms systemd-udevd.service
52ms plymouth-quit-wait.service
52ms speech-dispatcher.service
51ms nfs-server.service
49ms polkitd.service
49ms systemd-update-utmp.service
47ms hddtemp.service
42ms cpufrequtils.service
41ms nfs-mountd.service
41ms dev-hugepages.mount
37ms dns-clean.service
36ms sys-kernel-debug.mount
35ms dev-mqueue.mount
34ms resolvconf.service
33ms systemd-tmpfiles-setup-dev.service
31ms dev-sda6.swap
31ms console-kit-daemon.service
26ms plymouth-read-write.service
25ms nfs-config.service
25ms sysfsutils.service
24ms systemd-backlight@backlight:radeon_bl0.service
24ms nfs-idmapd.service
22ms boot-efi.mount
22ms libvirt-guests.service
21ms rc-local.service
21ms wpa_supplicant.service
21ms openvpn.service
20ms plymouth-start.service
19ms proc-sys-fs-binfmt_misc.mount
19ms systemd-sysctl.service
16ms kmod-static-nodes.service
15ms systemd-journal-flush.service
12ms setvtrgb.service
11ms rtkit-daemon.service
11ms bluetooth.service
10ms vboxautostart-service.service
10ms vboxballoonctrl-service.service
10ms ureadahead-stop.service
9ms sys-fs-fuse-connections.mount
9ms vboxweb-service.service
9ms systemd-user-sessions.service
8ms systemd-remount-fs.service
7ms systemd-random-seed.service
7ms systemd-update-utmp-runlevel.service
1ms snapd.socket

Re: excessively slow startup > 3 mins in "userspace"

Posted: Thu May 18, 2017 6:22 pm
by bbaker6212
I suffered with this problem for a long time but just stumbled upon the cause/solution.
I had installed rEFInd to replace Grub2 and when I started up LinuxMint it shows a bunch of text lines as it is booting up.
On one of these lines it showed ..."a start job is running for dev-disk-by x2duuid..." while it counted up to 90 seconds (just sitting there doing nothing)
Further investigation led to finding out the UUID of my swap partition had been changed in my /etc/fstab file and was incorrect - no doubt due to my installing various Linux repo's over time on various partitions.
Editing this file and correcting the UUID fixed the problem.