[Bug 291752] Re: [regression] cryptsetup does not work on raw encrypted drives

[Sven Berkvens-Matthijsse]

Hi,

My intrepid system was updated with cryptsetup 2:1.0.6-6ubuntu2.1 a
short while ago (via intrepid-updates).

Ever since, it will not boot with my encrypted root file system. It asks
for the password as usual, and when I enter it (correctly), it reports:
"cryptsetup: cryptsetup failed, bad password or options?".

When I boot in recovery mode, I see that something is reported about
/dev/md1 not being a block device.

I've restored the cryptoroot file in /usr/share/initramfs-tools/scripts
/local-top to what it was before (using grub to choose an initrd that
does not contain this version of cryptsetup yet), and ran update-
initramfs -u. This has solved my problem. It seems that the vol_id call
actually does something that is required for my setup.

My setup is as follows:

- 5 disks of equal size.
- First part of each disk is part of a RAID1 (using a Linux raid autodetect partition) that I use as /boot (ext3).
- Remaining space on each drive is part of a RAID5 (using a Linux raid autodetect partition).
- The RAID5 is encrypted using LUKS.
- The encrypted RAID5 contains LVM with five logical volumes of varying sizes.

If I can do anything to help sorting this out, please let me know.

With kind regards,
Sven

-- 
[regression] cryptsetup does not work on raw encrypted drives
https://bugs.launchpad.net/bugs/291752
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs