Public bug reported:
Binary package hint: yaird
I created a LUKS partition, /dev/mapper/cryptdisk,
used LVM2 to create a physical volume, volume group, and logical volume within
it, intending it to be an encrypted root partition. I used yaird to create a
boot image, and wrote it to /boot along with an appropriate GRUB entry. (I'm
skimming a complex procedure, but it's the same things that worked in feisty.)
On booting, the yaird image correctly reports loading my keyboard
settings, and prompts for the LUKS passphrase. On entry, it says:
"Unable to identify the filesystem on volume cryptdisk.
Reenter, Ignore, Shell?"
Looking at the source, I see that 1017_cryptsetup_blkid_test.patch
modifies the cryptosetup and cryptosetup_luks templates to run
/sbin/blkid on the encrypted device. If blkid's output is the empty
string, it concludes the luksOpen (in the LUKS case) failed.
I haven't tested yet whether this is an effect of the LVM2 partition
inside the LUKS, but on my working setup in feisty, blkid's output for
/dev/mapper/cryptdisk _is_ null. There's output for the logical volume
device under /dev/mapper, there's output for /dev/mapper/cryptoswap,
which has its own entry in /etc/crypttab, but none for cryptdisk.
** Affects: yaird (Ubuntu)
Importance: Undecided
Status: New
--
1017_cryptsetup_blkid_test.patch results in failure with LVM2 within LUKS
https://bugs.launchpad.net/bugs/148724
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
