"cryptsetup: lvm is not available"
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.
Where should I look?
Quoted 9 lines · Louis-David Mitterrand
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.
Where should I look?
This is probably distro dependent problem, cryptsetup itself never prints such message (it will be from some wrapper script I guess).
I would suggest you ask on your distro support channel. (It could be missing kernel module, missing or wrong info in /etc/crypttab / fstab, missing file in intramdisk etc.)
Also check lsblk output, the error message seems like you are using some lvm volume group in fact.
Milan
p.s.
Please always add information about your environment (distro, tools versions, if possible storage stack configuration like lsblk output etc.)
Quoted 9 lines · Louis-David Mitterrand
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
Signature · 4 lines
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: [email protected] 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
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
Quoted 35 lines · Arno Wagner
Quoted 9 lines · Louis-David Mitterrand
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: [email protected]
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
[email protected]
http://www.saout.de/mailman/listinfo/dm-crypt
Quoted 6 lines · Sven Eschenberg
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?
In any case the problem fixed itself with a debian dist-upgrade.
Thanks for your replies,