SDx timeouts during boot

nixIT · 2020-01-29 15:09:11

Hey gang,

I've been chasing a random issue on my system for a couple months. Every now and then when I reboot, my system hangs on trying to start, and I have to wait the max 1min 30 secs. It appears the hangup is one of my drives. sometimes the wait timer will flip between a couple of my drives (different every time), and sometimes it will stay on one drive (different).

After the 1min 30sec I am dumped to a terminal where the suggested course of action is enter in admin password and use journalctl -xb, or CTRL-D to resume. I CTRL-D and the system appears to continue but just sits there,

I dumped the journalctl -xb to a file so I can go through it, but I am not sure what to look for. On the most recent occurrence, I did find this:

Jan 28 23:50:32 desktop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-random-seed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 28 23:50:32 desktop kernel: audit: type=1130 audit(1580273432.540:10): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-random-seed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 28 23:52:00 desktop systemd[1]: dev-sdb2.device: Job dev-sdb2.device/start timed out.
Jan 28 23:52:00 desktop systemd[1]: Timed out waiting for device /dev/sdb2.
-- Subject: A start job for unit dev-sdb2.device has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit dev-sdb2.device has finished with a failure.
-- 
-- The job identifier is 64 and the job result is timeout.
Jan 28 23:52:00 desktop systemd[1]: Dependency failed for File System Check on /dev/sdb2.
-- Subject: A start job for unit systemd-fsck@dev-sdb2.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit systemd-fsck@dev-sdb2.service has finished with a failure.

I ran smartctl on my drives, no issues.

Any ideas on what I can look for to track this down?

thanx

--nixIT

V1del · 2020-01-29 15:28:33

Don't use /dev/sdX for identifying your drives, they are unstable and can change from boot to boot depending on when they are discovered by udev, use persistent device naming in every relevant config (fstab and boot loader/initramfs root kernel parameters, most importantly)

Last edited by V1del (2020-01-29 15:31:28)

nixIT · 2020-01-29 15:57:32

V1del wrote:

Don't use /dev/sdX for identifying your drives, they are unstable and can change from boot to boot depending on when they are discovered by udev, use persistent device naming in every relevant config (fstab and boot loader/initramfs root kernel parameters, most importantly)

Thanx, never experienced this issue until a couple months ago. I always used genfstab -L for my fstab file. I change my fstab to use UUID. let's see what happens on next boot.

Arch Linux

#1 2020-01-29 15:09:11

SDx timeouts during boot

#2 2020-01-29 15:28:33

Re: SDx timeouts during boot

#3 2020-01-29 15:57:32

Re: SDx timeouts during boot

Board footer