This is a very old LP bug, but for completeness it worth mentioning here
that recently some patches were merged on initramfs-tools and
cryptsetup, that allow a good experience booting with LUKS-encrypted
rootfs on top of a degraded RAID1 array; for details, please check:
@Kradllit
From the bugtracker you can see that ubuntus modifications to the raid package
have been unsupported for years.
https://wiki.ubuntu.com/ReliableRaid
Ubuntus mdadm setup is in the general case not capable to degrade
gracefully on boot. Instead of fixing the disabled notification of the
I install Ubuntu Server 10.04.2 on crypted lvm over RAID1 working
(appearing to work anyway), but if the RAID is degraded (which I just
faked for testing purposes) then I get this error cryptsetup: lvm
device name (/dev/disk/by-uuid/...) does not begin with /dev/mapper/ .
--
You received this
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/577239
Title:
I think this bug should be addressed along with 531240. I'm not
comfortable changing the symlink following in cryptsetup if there is a
chance it will lead to data loss.
** Changed in: cryptsetup (Ubuntu)
Status: In Progress = Incomplete
--
You received this bug notification because you
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
** Branch linked: lp:~csurbhi/+junk/cryptsetup-initramfs.fix
--
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
Bugs, which is subscribed to
The error message that you get here
cryptsetup: lvm device name (/dev/disk/by-uuid/...) does not begin with
/dev/mapper/ comes due to the fact that the
conf/conf.d/cryptroot in initramfs contains a line with source=UUID=uuid
instead of the intended source=/dev/mapper/vol-group-path if there is
Testing by wider audience is appreciated. Please consider this patch for
maverick updates.
** Attachment added: patch for adding the correct
source=/dev/mapper/vol-group in initramfs/conf/conf.d/cryptroot file.
** Changed in: cryptsetup (Ubuntu)
Status: Confirmed = In Progress
--
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
Bugs, which is
After upgrade I've got the same problem.
Can't boot anymore, because of '...does not begin with /dev/mapper/...' error.
--
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
I've tried solution from #13, but doesn't work. Probably change should be done
in initrd?
The other problem is that I can't even choose which kernel I want to boot, it's
just silent. I've tried already to press TAB.
--
crypted lvm on raid does not boot (lvm device name ... does not begin with
r...@ubuntu:/etc# cat crypttab
sda1_crypt /dev/sda1 none luks
--
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
Bugs, which is subscribed to
Not sure where the -u comes from now (looking at : man mkinitramfs),
but the mkinitramfs should recreate the initrd's (used from the
recovery mode).
To get a GRUB menu, try pressing SHIFT. You have to be quick sometimes.
--
crypted lvm on raid does not boot (lvm device name ... does not begin
Well, I had to fix this for myself today because I did an update and
some linux-image stuff was removed (no longer used) and I couldn't
boot any kernel afterwards. Previously, only the 2.6.32-23 kernel gave
me the error and the 2.6.32-22 kernel was OK. I set GRUB to default to
.22 because I was
I also seem to have this problem but it is not RAID/MD, just encrypted
LVM. I installed Lucid on my Thinkpad laptop a few weeks ago - a small
/boot partition (/dev/sda1), the rest of the disk encrypted LVM
(/dev/sda5). Everything worked. But a recent update has caused a boot
failure. I only
** Attachment added: blkid
http://launchpadlibrarian.net/49776209/blkid
--
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
Bugs, which is
** Attachment added: fdisk -l /dev/sda
http://launchpadlibrarian.net/49776224/fdisk
--
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
Bugs,
** Attachment added: /etc/default/grub
http://launchpadlibrarian.net/49776226/grub
--
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
Bugs,
** Attachment added: /boot/grub/grub.cfg
http://launchpadlibrarian.net/49776228/grub.cfg
--
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
** Attachment added: vgdisplay
http://launchpadlibrarian.net/49776239/vgdisplay
--
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
Bugs,
** Attachment added: uname -a
http://launchpadlibrarian.net/49776233/uname-a
--
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
Bugs, which
** Attachment added: pvdisplay
http://launchpadlibrarian.net/49776237/pvdisplay
--
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
Bugs,
** Attachment added: lvdisplay
http://launchpadlibrarian.net/49776241/lvdisplay
--
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
Bugs,
I have crypted / over RAID1 working (appearing to work anyway), but if
the RAID is degraded (which I just faked for testing purposes) then I
get this error cryptsetup: lvm device name (/dev/disk/by-uuid/...) does
not begin with /dev/mapper/ .
The error message is odd given that, when the RAID is
Debian bug #576488 is reported to be fixed by a patch taken *from*
Ubuntu, so this is not the same bug.
Please post your /etc/crypttab.
** Changed in: cryptsetup (Debian)
Importance: Unknown = Undecided
** Changed in: cryptsetup (Debian)
Status: Fix Released = New
** Changed in:
** Changed in: cryptsetup (Debian)
Status: Unknown = Fix Released
--
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
Bugs, which is
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.
** Changed in: cryptsetup (Ubuntu)
Status: New =
28 matches
Mail list logo
