A start job is running

[mike1]

Hi all,

for quite sometime when booting openSUSE Tumbleweed the process is being delayed by:

A start job is running for /dev/disk/by-uuid/bae6a13a-2994-4c28-b023-e526fc7f7668 (52s / 1min 30s)

I have not been able to find this device with lsblk or in /etc/fstab.
Does anybody have any idea where this could be located?

Not sure if the following error message is connected to this issue:

^M[   ***] A start job is running for /dev/disk/by-uuid/bae6a13a-2994-4c28-b023-e526fc7f7668 (1min 30s / 1min 30s)
^M[ TIME ] Timed out waiting for device /dev/disk/by-uuid/bae6a13a-2994-4c28-b023-e526fc7f7668.
[DEPEND] Dependency failed for Cryptography Setup for cr_usb-ST8000VN_0022-2EL112_A1EFFFFFFFFF-0:0-part1.
[DEPEND] Dependency failed for Local Encrypted Volumes.

I do not have any encrypted drive connected at the moment the system boots, but use encrypted USB drives for backup.

Thanks for your help in advance!

[nrickert]

Check whether that UUID shows up in “/etc/default/grub”.

Maybe also check “/etc/crypttab” to see if there is an entry for that encrypted USB drive.

[mike1]

It was in crypttab. Thank you!

[mike1]

After diving a bit more into /etc/crypttab: I assume you can’t simply delete the entry or can you?
I have read some threads where it was necessary to run update-initramfs which I can’t find in Tumbleweed and probably is not the right way at all?

[arvidjaar]

@mike1

I assume you can’t simply delete the entry or can you?

E-h-h … if you need it, you obviously should not delete it. We cannot know whether you need it.

@mike1

it was necessary to run update-initramfs

Normally only devices needed to mount root filesystem and swap/resume device are added to initrd (they are detected dynamically). Relatively recently dracut also started to add lines with x-initrd.attach option. Otherwise this line should not be present in initrd. You can check with

lsinitrd /path/to/your/initrd etc/crypttab

That said, rebuilding initrd is usually harmless.

[mike1]

@arvidjaar

E-h-h … if you need it, you obviously should not delete it. We cannot know whether you need it.

Not for booting, no. It is also not plugged while booting.
So simply delete the line from /etc/crypttab ?

[hcvv]

@mike1

Not for booting, no. It is also not plugged while booting.

I do not know much about crypttab, but your uttering above seems to include that the file system should still be able to mount later when the system is running for some time. I would say that you then need the entry in /etc/crypttab .

In /etc/fstab one can add the noauto option for such cases. Then a mount during boot is not tried. I have no idea if there is something like that possible in /etc/crypttab.

[arvidjaar]

@mike1

So simply delete the line from /etc/crypttab ?

Did not I already answer that?

@hcvv

the file system should still be able to mount later when the system is running for some time. I would say that you then need the entry in /etc/crypttab .

You do not need a line in /etc/fstab “to mount later”, why would you need a line in /etc/crypttab to decrypt later?

[hcvv]

@arvidjaar

You do not need a line in /etc/fstab “to mount later”, why would you need a line in /etc/crypttab to decrypt later?

Of course you can do anything by typing a lot, but an entry in /etc/fstab comes very handy because you then only have to type the mount command with the device or the mountpoint and all other things, including options, will be filled in automagically,

[nrickert]

@hcvv

In /etc/fstab one can add the noauto option for such cases. Then a mount during boot is not tried. I have no idea if there is something like that possible in /etc/crypttab.

Yes, you can use a “noauto” option in “crypttab”.