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

[Daniel Holbach]

It seems like some additional work needs to go into the fix.

I'll unsubscribe the sponsors team for now, please resubscribe when
ready.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/577239

Title:
  crypted lvm on raid does not boot (lvm device name ... does not begin with /dev/mapper/)

Status in “cryptsetup” package in Ubuntu:
  Incomplete
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