On my disk I have LVM configured as such:
- One Volume Group "vg1", containing
- One Logical Volume "lv1", containing a LUKS encrypted partition which is the root of a Debian Linux installation
- One Logical Volume "00" containing another LUKS encrypted partition which is the root of a Qubes OS installation
I want the system to boot into Qubes; in other words, I need to unlock vg1/00 and then mount it as the root device.
The problem is that Grub only asks me to unlock logical volume "lv1". I can't make Grub ask to unlock the "00" logical volume no matter the kernel boot options.
Editing grub's command line at boot I can see root=/dev/mapper/luks-<UUID> as well as rd.lvm.vg=vg1/00 and rd.lvm.lv=luks.<UUID>. The UUID matches the correct logical volume.
How can I make sure that grub actually uses the rd.lvm boot options?
cryptomountcommands in grub.cfg; if not then it probably has nothing to do with grub, you'll need to make sure eachlinuxline has the appropriate DISTRO-SPECIFIC boot param for the unlocking the right device (e.g. in Arch Linux it'scryptdevice=) – Tom Yan Apr 16 '16 at 13:32rd_LUKS_UUID, but yet to no avail. – lorenzog Apr 16 '16 at 14:22