registry team mailing list archive

[Alastair Sherringham <sherringham@xxxxxxxxx>]

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 noticed this on Friday because I have been suspending,
not restarting my laptop.

Trying to boot the new kernel FAILS :

menuentry 'Ubuntu, with Linux 2.6.32-22-generic'

I get the error :

cryptsetup: lvm device name (/dev/disk/by-uuid/fb9559fc-
9bf7-4f74-b1a1-a44e49d82d92) does not begin with /dev/mapper/

I can boot the previous, original kernel OK :

menuentry 'Ubuntu, with Linux 2.6.32-21-generic'

Software :

initramfs-tools 0.92bubuntu78
cryptsetup 2:1.1.0~rc2-1ubuntu13
grub-pc 1.98-1ubuntu6

I will attach some information files :

/etc/crypttab
blkid (output)
fdisk -l /dev/sda (output)
/etc/fstab
/etc/default/grub
/boot/grub/grub.cfg
pvdisplay (output)
vgdisplay (output)
lvdisplay (output)
uname -a (output)


** Attachment added: "/etc/crypttab"
   http://launchpadlibrarian.net/49776159/crypttab

-- 
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 Registry
Administrators, which is the registrant for Debian.