I agree that the OP is probably using LVM. A couple months ago with a minor version change LVM changed semantics. Suddendly vgchange -ay stopped creating inodes for me. Maybe the newer kernel's initramfs was created with a more recent LVM which includes this change? Regards -Sven On Thu, June 26, 2014 06:20, Arno Wagner wrote: > On Wed, Jun 25, 2014 at 16:51:40 CEST, Louis-David Mitterrand wrote: >> Hi, >> >> When booting with a 3.15 kernel I get this error message and I am not >> prompted to unlock my root device. >> >> However when booting with a 3.14 kernel I can unlock my partition and >> boot normally. >> >> I have never used lvm. > > Smart IMO, but the distro installer likely did. If it is > a sane installer, it will have asked some time during the > installation whether to use LVM or plain old partitions. > > What this means is that your LUKS container is in some LVM > container and the distro-wrapper around cryptsetup does not > manage to open it. > > LVM makes things easier for generic installations, but it > also makes it more likely that things break and more > difficult to fix when they do. > > Arno > -- > Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@xxxxxxxxxxx > GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D > 9718 > ---- > A good decision is based on knowledge and not on numbers. - Plato > _______________________________________________ > dm-crypt mailing list > dm-crypt@xxxxxxxx > http://www.saout.de/mailman/listinfo/dm-crypt > _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
