Bug#671305: dracut: cryptsetup just hangs, making the system unbootable
Package: dracut Followup-For: Bug #671305 I just experienced the same as in the first post. Tried out the 3.8 kernel from experimental, which replaced initramfs-tools with dracut and couldn't boot anymore. here's what it looks like: http://i.imgur.com/Oe2Wb5D.jpg type in the password, hit enter. nothing. i could try it out again (if you need more logs etc) but i reverted back to initramfs-tools for now. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (102, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dracut depends on: ii cpio 2.11+dfsg-0.1 ii kbd1.15.5-1 pn kpartx ii module-init-tools 9-2 ii udev 175-7.1 ii util-linux 2.20.1-5.3 Versions of packages dracut recommends: ii cryptsetup 2:1.4.3-4 pn dmraid ii dmsetup 2:1.02.77-1 ii lvm22.02.98-1 pn mdadm Versions of packages dracut suggests: pn dracut-network -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671305: dracut: cryptsetup just hangs, making the system unbootable
Ok I have got some time to try this again.
This time, the xts module is included in the initramfs. I'm 100% sure it
wasn't present in the resulting initramfs last time (I have checked with
lsinitrd | grep xts). Something must have gone wrong last time... My
configuration changed a bit since, though (I replaced the hard drive and
added an lvm in top of luks). My apologizes about that.
However, the initial problem is still present.
I have run cryptsetup with strace in the initramfs, and it hangs inside a
semop system call. It looks like a deadlock to me.
> semop(0, {{0, 0, 0}}, 1
Bug#671305: dracut: cryptsetup just hangs, making the system unbootable
Hi, I encountered the same problem. My / is luks-encrypted with aes in mode xts-plain64:sha256. It turns out that dracut doesn't include the xts module in the initramfs, thus cryptsetup hangs. It seems it's already fixed upstream : http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.1_Technical_Notes/dracut.html > BZ#670925 >dracut now includes the kernel module aes-xts in the initramfs, adding > support for FIPS-140. -- Package: dracut Version: 018+32+geb6e141-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671305: dracut: cryptsetup just hangs, making the system unbootable
Package: dracut Version: 018+32+geb6e141-1 So, I had a bit of a bad experience yesterday evening. :-) I switched from initramfs-tools to dracut 18, because I like the idea of dracut, and I had successfully used dracut 17. But after reboot and entering a LUKS password, nothing happened. I rebooted and added [rd.luks=0 rd.shell] to the kernel command line. Trying to open any LUKS device manually showed the same behavior: it just hangs. No reaction to SIGINT. SIGQUIT gets rid of the cryptsetup process. At that point, a /dev/dm-? node has shown up, but doesn't work yet, and none of the symlinks are there. I reverted the machine to initramfs-tools for now. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
