Public bug reported:
Binary package hint: lvm2
running an up to date feisty, I can not boot on my RAID/LVM root partition. I
previously had bug #75681 which seems fixed now (/dev/md0 is created
automatically again) but the LVM volumes are not activated by the initramfs
anymore.
In the initramfs shell I can not find "/scripts/local-top/lvm" anymore.
adding "break=mount" to the kernel options to get a shell, then running:
/scripts/local-top/mdadm
lvm vgscan
lvm vgchange -a y
does activate the RAID and the LVM volumes, I get the right files in
/dev/mapper but I can not boot further. When leaving the busybox shell I get
some messages including:
"/init:1:cannot open /dev/mapper/vg_... : No such device or address"
and I then get back to a busybox shell.
mounting my the volume by hand fails with the same message.
On another install (also feisty but a bit less up to date), I can mount
the same volume without a problem. As many updates came today for
LVM/usev/initramfs, I ran an update via chroot, but the problem is still
there.
Any hint to boot it by hand in the meantime ?
** Affects: lvm2 (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
[feisty] mounting LVM root broken
https://launchpad.net/bugs/83832
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
