You are not logged in.
- Topics: Active | Unanswered
#1 2021-02-07 22:34:23
- wasswart
- Member
- Registered: 2021-02-07
- Posts: 3
Boot delay userspace in 1min 37sec [SOLVED] itself
Hi,
It takes about 1min 37sec before I get the login prompt. During this time on the console on the first line is output /dev/sdd2 and on the second line the cursor is blinking for the entire duration. I gather it has something to do with systemd but do not know how to proceed.
# systemd-analyze
Startup finished in 3.662s (kernel) + 1min 33.710s (userspace) = 1min 37.373s
graphical.target reached after 1min 33.710s in userspacesystem-analyze blame:
# systemd-analyze blame
31.003s lvm2-monitor.service >
22.965s dev-sdd2.device >
8.823s dhcpcd@eth0.service >
5.147s systemd-journal-flush.service >
2.034s systemd-udevd.service >
1.168s user@1000.service >
746ms systemd-tmpfiles-setup-dev.service >
596ms polkit.service >
458ms systemd-fsck@dev-disk-by\x2duuid-bed51e72\x2dfdf7\x2d4295\x2d833a\x2d5573eb10>
423ms upower.service >
399ms systemd-logind.service >
393ms systemd-fsck@dev-disk-by\x2duuid-7ca5bdd1\x2d1abd\x2d4ee8\x2d8943\x2d54ecc522>
370ms modprobe@fuse.service critical chain:
# systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @1min 33.710s
└─multi-user.target @1min 33.710s
└─getty.target @1min 33.710s
└─getty@tty1.service @1min 33.710s
└─systemd-user-sessions.service @1min 33.687s +11ms
└─network.target @1min 33.686s
└─dhcpcd@eth0.service @1min 24.862s +8.823s
└─sys-subsystem-net-devices-eth0.device @1min 24.861sDoes not show any failures:
# systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.# journalctl SYSLOG_IDENTIFIER=systemd -b
http://codepad.org/dv7eNsKN
Any help or suggestion would be much appreciated.
Last edited by wasswart (2022-02-06 21:52:13)
Offline
#2 2021-02-08 08:11:03
- seth
- Member
- From: Don't DM me only for attention
- Registered: 2012-09-03
- Posts: 74,267
Re: Boot delay userspace in 1min 37sec [SOLVED] itself
Remove the "quiet" parameter from the kernel command line.
Could be some fsck.
Last edited by seth (2021-02-08 08:11:19)
Online
#3 2021-02-08 13:43:44
- twelveeighty
- Member
- Registered: 2011-09-04
- Posts: 1,446
Re: Boot delay userspace in 1min 37sec [SOLVED] itself
Could be some fsck.
I agree - something odd / long running is going on with your HDD/SDD. It takes 18 seconds just to discover the disk:
Feb 08 10:32:19 puff systemd[1]: Finished Flush Journal to Persistent Storage.
Feb 08 10:32:37 puff systemd[1]: Found device ST31000524AS Linux\x20filesystem.Offline
#4 2021-02-14 01:55:31
- wasswart
- Member
- Registered: 2021-02-07
- Posts: 3
Re: Boot delay userspace in 1min 37sec [SOLVED] itself
Thanks very much for the replies. I disabled the 'quiet' parameter, when it boots up, it gets stuck on this:
A start job is running for: /sys/sub devices/eth0 <secs counter>/1m30Every other boot when getting to the GUI, there is no eth0 network connection and I have to reboot.
Also, when it gets to the GUI, the UI is unresponsive for about 30 secs (i.e. no mouse/keyb) and CPU sitting at 100%. When I finally get mouse/keyb activation, and I run 'top' there is probably about 20 'systemd-udevd' processes running, but I don't know if this is abnormal or not. When these finish running, the CPU gets back to normal:
top - 14:25:17 up 2 min, 1 user, load average: 28.26, 11.07, 4.09
Tasks: 213 total, 12 running, 201 sleeping, 0 stopped, 0 zombie
%Cpu(s): 21.2 us, 73.6 sy, 0.0 ni, 4.1 id, 0.0 wa, 0.1 hi, 0.9 si, 0.0 st
MiB Mem : 32032.5 total, 31536.2 free, 291.6 used, 204.7 buff/cache
MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 31375.9 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
279 root 20 0 28548 5912 4544 D 26.6 0.0 0:28.84 systemd-udevd
277 root 20 0 28608 7092 5584 R 26.2 0.0 0:29.80 systemd-udevd
293 root 20 0 38692 8144 4592 D 26.2 0.0 0:28.62 systemd-udevd
274 root 20 0 36792 6208 4788 R 25.6 0.0 0:29.18 systemd-udevd
296 root 20 0 38704 8196 4628 R 25.6 0.0 0:28.41 systemd-udevd
297 root 20 0 38704 8048 4220 R 25.6 0.0 0:28.40 systemd-udevd
295 root 20 0 38696 7028 3672 R 25.2 0.0 0:28.66 systemd-udevd
284 root 20 0 29596 7504 5100 R 24.9 0.0 0:28.56 systemd-udevd
294 root 20 0 38692 8364 4804 D 24.9 0.0 0:29.33 systemd-udevd
280 root 20 0 36788 5992 4144 D 24.6 0.0 0:28.69 systemd-udevd
302 root 20 0 38956 8520 4776 R 23.9 0.0 0:29.30 systemd-udevd
281 root 20 0 28560 5920 4492 D 23.6 0.0 0:28.46 systemd-udevd
285 root 20 0 37028 7096 5076 R 23.6 0.0 0:29.34 systemd-udevd
290 root 20 0 38680 8056 4520 D 23.6 0.0 0:28.96 systemd-udevd
298 root 20 0 38708 8596 5032 D 23.6 0.0 0:28.45 systemd-udevd
300 root 20 0 38036 6376 3764 D 23.6 0.0 0:29.67 systemd-udevd
275 root 20 0 29668 7596 5132 R 23.3 0.0 0:29.32 systemd-udevd
282 root 20 0 37096 6492 4804 D 23.3 0.0 0:28.87 systemd-udevd
276 root 20 0 36732 6264 4720 D 22.9 0.0 0:28.51 systemd-udevd
271 root 20 0 36812 5908 4444 D 22.6 0.0 0:28.92 systemd-udevd
273 root 20 0 28560 6492 5040 D 22.6 0.0 0:28.18 systemd-udevd
278 root 20 0 38756 8876 4436 D 22.6 0.0 0:28.48 systemd-udevd
283 root 20 0 28564 5848 4396 D 22.6 0.0 0:28.67 systemd-udevd
287 root 20 0 37988 7232 4600 D 22.6 0.0 0:29.20 systemd-udevd
288 root 20 0 30568 8572 5232 D 22.6 0.0 0:29.15 systemd-udevd
291 root 20 0 38004 7548 4192 R 22.6 0.0 0:28.78 systemd-udevd
301 root 20 0 38048 7940 5280 D 22.3 0.0 0:29.02 systemd-udevd
272 root 20 0 28544 6216 4776 R 21.6 0.0 0:28.21 systemd-udevd
289 root 20 0 37996 8480 5388 D 21.6 0.0 0:29.20 systemd-udevd
299 root 20 0 38032 7952 4568 D 21.6 0.0 0:28.85 systemd-udevd
292 root 20 0 38004 6280 3700 D 19.6 0.0 0:28.64 systemd-udevd
303 root 20 0 30628 8716 5316 D 19.3 0.0 0:28.43 systemd-udevdWhen I run dmesg:
[ 22.195354] usbcore: registered new interface driver usbhid
[ 22.195354] usbhid: USB HID core driver
[ 27.438669] Adding 2097148k swap on /dev/sdd3. Priority:-2 extents:1 across:2097148k FS
[ 29.058894] mc: Linux media interface: v0.10
[ 29.499267] usb 3-1: Warning! Unlikely big volume range (=32768), cval->res is probably wrong.
[ 29.499270] usb 3-1: [5] FU [PCM Playback Volume] ch = 1, val = -32768/0/1
[ 29.568516] usb 3-1: Warning! Unlikely big volume range (=32768), cval->res is probably wrong.
[ 29.568518] usb 3-1: [6] FU [Headset Capture Volume] ch = 1, val = -32768/0/1
[ 29.571076] usbcore: registered new interface driver snd-usb-audio
[ 37.077598] audit: type=1130 audit(1613266347.117:20): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 37.669515] audit: type=1130 audit(1613266347.710:21): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-by\x2duuid-bed51e72\x2dfdf7\x2d4295\x2d833a\x2d5573eb1086d1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 37.777773] audit: type=1130 audit(1613266347.817:22): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-by\x2duuid-7ca5bdd1\x2d1abd\x2d4ee8\x2d8943\x2d54ecc522f9f8 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 37.788858] EXT4-fs (sdd5): mounted filesystem with ordered data mode. Opts: (null)
[ 37.788864] ext4 filesystem being mounted at /boot supports timestamps until 2038 (0x7fffffff)
[ 37.831198] EXT4-fs (sdd4): mounted filesystem with ordered data mode. Opts: (null)
[ 38.152998] audit: type=1130 audit(1613266348.194:23): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 38.169668] audit: type=1127 audit(1613266348.210:24): pid=354 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success'
[ 38.222521] audit: type=1130 audit(1613266348.264:25): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 38.324841] audit: type=1130 audit(1613266348.364:26): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=cronie comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 38.335453] audit: type=1130 audit(1613266348.377:27): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dbus comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 38.337021] audit: type=1334 audit(1613266348.377:28): prog-id=15 op=LOAD
[ 38.368887] audit: type=1334 audit(1613266348.410:29): prog-id=16 op=LOAD
[ 89.759058] asus_wmi: ASUS WMI generic driver loaded
[ 89.769783] asus_wmi: Initialization: 0x0
[ 89.769817] asus_wmi: BIOS WMI version: 0.9
[ 89.769877] asus_wmi: SFUN value: 0x0
[ 89.769879] eeepc-wmi eeepc-wmi: Detected ASUSWMI, use DCTSAny help would be much appreciated.
Offline
#5 2021-02-14 02:47:41
- loqs
- Member
- Registered: 2014-03-06
- Posts: 18,859
Re: Boot delay userspace in 1min 37sec [SOLVED] itself
Are you dual booting the system with any other OS? dhcpcd@eth0.service taking 90 seconds to timeout and fail due to the missing eth0 would explain the long boot time.
Please provide more information about eth0, what device is it? What kernel driver does it use? To rule out another possible issues do you use any network management services other than dhcpcd?
Last edited by loqs (2021-02-14 02:48:12)
Offline
#6 2022-02-06 21:55:09
- wasswart
- Member
- Registered: 2021-02-07
- Posts: 3
Re: Boot delay userspace in 1min 37sec [SOLVED] itself
Problem solved itself after a couple of months, it was introduced after a system upgrade and a couple of months later disappeared after a system upgrade with no action on my part. System now boots up in normal time once again.
Offline