[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#702452: linux-image-3.8-trunk-amd64: LVM volume groups are not found, volumes not activated



Hello Ben,

Package: src:linux
Version: 3.8-1~experimental.1
Severity: normal

My / is on a LVM volume. Kernel 3.8 logs 'Volume group "ssd" not found'
and "/dev/mapper/ssd-debian not found" on startup

These messages do not come from the kernel.  LVM2 is a userland thing;
the kernel only provides the building blocks for it (device-mapper).

and drops me in the
initramfs shell. The LVM pv, vg and lv are visible in lvm just fine, but
the logical volume is not activated and thus not accessible to the
system.

(initramfs) lvm
lvm>  lvchange -a y ssd/debian

fixes the problem.

This works fine in 3.2.0-4 and 3.7-trunk. initrd has the same timestamp
for both 3.7 and 3.8.
[...]

I suspect this may be due to a difference in timing of device
initialisation.  AFAIK initramfs-tools still doesn't know how
to handle asynchronous device discovery and relies on you to
fudge it with the 'rootdelay' parameter.

Yeah, looks like. Even rootdelay=1 seems to be enough to fix it.

Since there are a couple of bugs filed with initramfs-tools already I'm marking this bug done.

Thanks for your quick response.

Bernhard


Reply to: