[SOLVED] Dracut hangs on cryptsetup luksOpen / Udev cookie waiting for zero
by joe_2000 from LinuxQuestions.org on (#56NVS)
My void linux laptop with fully encrypted disk hangs at boot.
After about 3 minutes I get dropped into the dracut debug shell.
I tried to mount the LUKS encrypted rootfs manually and found that it hangs there.
(When I boot the laptop from a live system I can mount the cryptdisko without problems, so I think the problem must be in the initrd.)
I tried to run the cryptsetup command with the --debug flag and it got stuck saying it was waiting for a udev cookie being decremented to zero. (See first screenshot)
I searched this problem on the web and found various sources that pointed at missing udev rules.
A post in a gentoo forum specifically listed the following rules:
Code:/lib/udev/rules.d/10-dm.rules
/lib/udev/rules.d/11-dm-lvm.rules
/lib/udev/rules.d/13-dm-disk.rules
/lib/udev/rules.d/95-dm-notify.rulesSo I checked the initrd for the presence of these rules and found that they are present albeit under a different directory. (See second screenshot)
I compared this to an older initrd lying around that I know worked before. (I no longer have the kernel image so unfortunately I can't boot from it).
The udev rules are also located under the /usr/lib structure there and the /lib/udev structure is absent.
So I would be inclined to say the rules are present.
I am running out of ideas on how to diagnose this further. If you have an idea please let me know! Also do let me know if I need to supply more information.
EDIT: I forgot to mention that I did a system update today. I think (but I am not 100% sure) that the problem occurred right at the first boot after the update.
EDIT2: I can boot again! I downgraded dracut from package version 050_7 to 050_2. This makes me think the problem is with a change in the packaging instructions. I will investigate further and report back
Attached Thumbnails
After about 3 minutes I get dropped into the dracut debug shell.
I tried to mount the LUKS encrypted rootfs manually and found that it hangs there.
(When I boot the laptop from a live system I can mount the cryptdisko without problems, so I think the problem must be in the initrd.)
I tried to run the cryptsetup command with the --debug flag and it got stuck saying it was waiting for a udev cookie being decremented to zero. (See first screenshot)
I searched this problem on the web and found various sources that pointed at missing udev rules.
A post in a gentoo forum specifically listed the following rules:
Code:/lib/udev/rules.d/10-dm.rules
/lib/udev/rules.d/11-dm-lvm.rules
/lib/udev/rules.d/13-dm-disk.rules
/lib/udev/rules.d/95-dm-notify.rulesSo I checked the initrd for the presence of these rules and found that they are present albeit under a different directory. (See second screenshot)
I compared this to an older initrd lying around that I know worked before. (I no longer have the kernel image so unfortunately I can't boot from it).
The udev rules are also located under the /usr/lib structure there and the /lib/udev structure is absent.
So I would be inclined to say the rules are present.
I am running out of ideas on how to diagnose this further. If you have an idea please let me know! Also do let me know if I need to supply more information.
EDIT: I forgot to mention that I did a system update today. I think (but I am not 100% sure) that the problem occurred right at the first boot after the update.
EDIT2: I can boot again! I downgraded dracut from package version 050_7 to 050_2. This makes me think the problem is with a change in the packaging instructions. I will investigate further and report back
Attached Thumbnails