[Bug 577239] Re: crypted lvm on raid does not boot (lvm device name ... does not begin with /dev/mapper/)

[ceg]

Guys, make sure what you are seeing is not your machine saving your from
data loss. Bug #531240 (root raid_members opened as luks). Especialy if
you are only seeing this occasionally/with not all member devices
present.

The check to only open /dev/mapper/ is your last hold in preventing data
loss by opening a member device (with the same md device UUID and the
same filesystem UUID in the raid mirror case).

This seems to pevent cryptsetup to open a raid member device instead of
an assembled array.

-- 
crypted lvm on raid does not boot (lvm device name ... does not begin with /dev/mapper/)
https://bugs.launchpad.net/bugs/577239
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is a direct subscriber.

Status in “cryptsetup” package in Ubuntu: In Progress
Status in “cryptsetup” package in Debian: Invalid

Bug description:
Binary package hint: cryptsetup

I set up a crypted lvm on a raid1 with mdadm following the guide at 
http://wiki.ubuntuusers.de/System_verschl%C3%BCsseln#Partitionierung
The system I installed is Ubuntu 10.04 LTS
After installation I tried to boot, but got the message: 
"cryptsetup: lvm device name (/dev/md0) does not begin with /dev/mapper/"
same problem if I try to access the raid-device in /etc/crypttab with uuid:
"cryptsetup: lvm device name (/dev/disk/by-uuid/...) does not begin with /dev/mapper/"

I guess it is the same bug as described here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576488

the workaround described there also works for me:

"After some time a BusyBox shell is started. You can assemble the RAID
array manually by for example

        $ mdadm --assemble --scan

and log out with Ctrl + d afterward."

Version of Cryptsetup: 2:1.1.0~rc2-1ubuntu13
Version of mdadm: 2.6.7.1-1ubuntu15
Version of lvm2: 2.02.54-1ubuntu4

hopefully this is enough information to find the problem.

regards,
Carsten