Long boot. Timed out waiting for device... Dependency failed for...

rihno26 · 2020-12-11 08:50:33

I got those messages during boot after I had installed udisks2 (for flash drives automount).
I need to wait a couple of minutes and press ctrl + D to continue the boot.
Photo of screen during boot, before pressing ctrl + D: https://prnt.sc/w0ckc4
#journalctl -b output: http://ix.io/2Hwf
#cat /etc/fstab output: http://ix.io/2Hwq
#lsblk -f output: http://ix.io/2Hwr

Can't understand how to solve this problem, may you help me?

Some, to my mind, relevant strings from journalctl:

laptop kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20200717/utaddress-204)
laptop kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

laptop lvm[198]:   WARNING: Device /dev/sda1 not initialized in udev database even after waiting 10000000 microseconds.
laptop lvm[198]:   WARNING: Device /dev/sda2 not initialized in udev database even after waiting 10000000 microseconds.
laptop lvm[198]:   WARNING: Device /dev/sda3 not initialized in udev database even after waiting 10000000 microseconds.
laptop lvm[198]:   WARNING: Device /dev/sda1 not initialized in udev database even after waiting 10000000 microseconds.
laptop kernel: ACPI: button: The lid device is not compliant to SW_LID.
laptop lvm[198]:   WARNING: Device /dev/sda2 not initialized in udev database even after waiting 10000000 microseconds.
laptop systemd-udevd[230]: sdv_gpio: Spawned process '/usr/bin/systemctl restart media-automount@sdv_gpio.service' [234] is taking longer than 59s to complete

Last edited by rihno26 (2020-12-11 11:12:00)

coxe87b · 2020-12-11 11:39:36

It looks as if your system has been set up to use LVM but now you are trying to use it with plain devices and partitions. Is this the case?
Here is info on setting up LVM: https://wiki.archlinux.org/index.php/LVM

rihno26 · 2020-12-11 20:09:15

Thanks for the answer, I am not sure about using lvm.

Partially solved by editing /etc/fstab.
I saw similar problem on forum and changed /etc/fstab file a little bit. I did not test If OS can use swap, but I can access /home without manual mounting.
Computer boots faster, without pressing ctrl + D each time, so without first problem (with failed dependencies messages one), but I get another errors during boot.
I see these just before login screen (here I pasted same messages from journalctl):

laptop systemd[1]: Failed to start media-automount@sdv_gpio.service.

laptop systemd[1]: Failed to start media-automount@sda.service.

laptop systemd[1]: Failed to start media-automount@sda2.service.

laptop systemd[1]: Failed to start media-automount@sda1.service.

laptop systemd[1]: Failed to start media-automount@sda3.service.

Whole output of journalctl -b: http://ix.io/2HB2
Updated /etc/fstab: http://ix.io/2HB6

May you provide some references why does it occur?

coxe87b · 2021-03-20 12:37:36

Not sure if you are still having issues with this, but you could try rebuilding your fstab file in case of errors with invalid UUID.

Cross-reference your entries in fstab with

lsblk -f

You could then either edit your fstab by hand to reflect the UUID's mounted and delete or comment any invalid entries, or if you are really stuck, you could use the genfstab command on an Arch live iso.

Arch Linux

#1 2020-12-11 08:50:33

Long boot. Timed out waiting for device... Dependency failed for...

#2 2020-12-11 11:39:36

Re: Long boot. Timed out waiting for device... Dependency failed for...

#3 2020-12-11 20:09:15

Re: Long boot. Timed out waiting for device... Dependency failed for...

#4 2021-03-20 12:37:36

Re: Long boot. Timed out waiting for device... Dependency failed for...

Board footer