Today I discovered why lvmcreate_initrd is broken. It seems that the layout of /dev has changed. In the old layout there was a symlink "ram -> ram1" (why its not "ram -> ram0" I'm not sure, should it be?) and this works fine for lvmcreate_initrd. On the new layout the format is symlinks "ram{0-16} -> rd/{0-16}" but no "ram" symlink. This is why lvmcreate_initrd breaks on boot. I would suggest adding a symlink "ram -> ram0" (unless it *NEEDS* to be "ram -> ram1", which I haven't played with yet) to baselayout. This should resolve this annoying bug. Doug Miller
Actually, this may be a problem with my local install. It worked for me twice, but no longer works. I'll report any further findings, I'm still looking into it. Doug Miller
It sounds like lvmcreate_initrd is not devfs friendly or something. The script itself should really be fixed.
lvmcreate_initrd has a -D or --devfs flag which forces it to use devfs.