Bug 451844 – sys-fs/udev-197-r2 breaks LVM boot

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description Martin von Gagern 2013-01-13 18:37:03 UTC]

Today I upgraded udev from 196-r1 to 197-r2. Upon the next reboot, the lvm init script from sys-fs/lvm2-2.02.97-r1 printed the following message and then stopped:

* Setting up the Logical Volume Manager...
The link /dev/VgName/usr should have been created by udev but it was not found. Falling back to direct link creation.

Using the interactive boot feature of OpenRC, I was able to switch to a shell in the situation where that init script is run. The message appears to be printed by the "vgscan --mknodes" command. But it is the subsequent "vgchange --sysinit -a ly" command which blocks, after printing something about 14 logical volumes having been activated. Not sure what it is waiting for.

I'm using /usr on LVM, and sys-kernel/dracut-024-r4 to create an initramfs which mounts that partition. After dracut is done, /dev/VgName/usr does exist as a symlink, just as it should, but before the lvm init script the whole directory /dev/VgName no longer exists. Don't know who's removing that.

I was able to downgrade udev back to 096-r1. I did so by using interactive boot mode to skip the lvm init script, then issued the LVM initialization commands manually, in the interactive lvm shell. The vgchange command reported the activated LVs, but did not create any device nodes. So I issued "vgscan --mknodes" again, which reported the same line as above for each LV, but created the nodes all right. After that, I could mount the remaining partitions and emerge the older udev.

[Comment 1 Alexander Tsoy 2013-01-13 18:43:34 UTC]

This is a dublicate of bug 451266.

[Comment 2 William Hubbs 2013-01-13 18:54:19 UTC]

*** This bug has been marked as a duplicate of bug 451266 ***