From: Theodore Ts'o on

The last kernel I could boot was 2.6.33-rc4, so this might be a
regression. As near as I can tell, this udev rule isn't firing:

SUBSYSTEM=="block", ACTION=="add|change", ENV{ID_FS_TYPE}=="lvm*|LVM*", \
RUN+="watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange -a y'"

So nothing is showing up in /dev/mapper, and so the root can't be
mounted. After 45 seconds, it drops me into the initramfs shell, and if
I manually run "lvm vgscan" and "lvm vgscange -ay", everything is back,
but then I can't figure out how to restart the boot process from inside
a failed initramfs. And of course, the initramfs environment is so
crappy that there are no debugging aids --- not even a working pager.

Did I mention how much I hate the whole initramfs with dynamic udev
rules as a design?

I'll probably kludge some kind of "sleep 10; lvm vgscan ; lvm vgchange
-ay" into some local initramfs script, but it would be nice to know what
happened and what the real right fix should be. Did anything change
recently that might have caused this to fail?

- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/