crypted lvm on raid does not boot (lvm device name ... does not begin with /dev/mapper/)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cryptsetup (Debian) |
Invalid
|
Undecided
|
Unassigned | ||
cryptsetup (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: cryptsetup
I set up a crypted lvm on a raid1 with mdadm following the guide at
http://
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/
I guess it is the same bug as described here:
http://
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~
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
Related branches
Changed in cryptsetup (Debian): | |
status: | Unknown → Fix Released |
Changed in cryptsetup (Ubuntu): | |
status: | Confirmed → In Progress |
Since this has been fixed in Debian, hopefully this can be fixed in time for 10.04.1, if that applies. I'm relatively certain this would not qualify for an SRU since the bug is likely to only affect a very small percentage of users.