Hi Quentin, Quentin Lefebvre wrote (08 Nov 2014 14:08:15 GMT) : > You can reproduce the bug easily with the following commands: > dd if=/dev/zero of=/test1.loop bs=10M count=1 > dd if=/dev/random of=/test1.key bs=64c count=1 > cryptsetup --key-file /test1.key --cipher aes-xts-plain64 --key-size 512 > --hash sha512 create test1 /test1.loop > mkfs.ext2 /dev/mapper/test1 > cryptsetup close test1
> Then add the following to /etc/crypttab: > test1 /test1.loop /test1.key > cipher=aes-xts-plain64,size=512,hash=sha512,offset=0,retry=1 > and the following to /etc/fstab: > /dev/mapper/test1 /media/TMP ext2 defaults 0 2 > Don't forget to mkdir /media/TMP... > Then run: > update-initramfs -k all -u > and reboot to observe the bug. > To finish with that, adding > init=/lib/sysvinit/init > to the kernel command line makes the bug disappear. Could you please try to pinpoint which exact option, among the many ones you're using, is badly handled? E.g. start with a plain dm-crypt device, then use an external key file, then add cipher/hash/offset/retry options one at a time. Cheers, -- intrigeri -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
