>
> Notice in line 2, the kernel command line does include "devfs=mount".
> Notice in lines 5-8, the initial ramdisk is detected and mounted. In
> line 9, the kernel mounts devfs. Lines 10-11 are the loading of the
> lvm driver and lines 12-14 are errors from devfs about devices that
> exist, I guess. I am not sure why I am getting these.
>
This comes because of mknod in vgscan. From devfs point of view, both
mknod and devfs_register means the same. And you are not expected to use
both at the same time (for the same device in any case). Here activating
VG tries to register devfs names that were already created by vgscan.
Strictly speaking, it is harmless.
> See on line 15, the real root filesystem (on the LVM LV) is mounted
> successfully (yay!) and on line 17, devfs is mounted again -- by the
> kernel.
>
Yes, but still devfs exists just once. Mounting it just makes it
user-visible - but as long as devfs is conpiled in kernel, *all* device
operations use devfs. It does not depend on its mounted state. So
remounting devfs should not (module bug) make any difference.
> The system boots fine onto the LVM based root filesystem. The problem
> is that the device nodes in /dev/VG (group, lvol1 and 1) are missing
> an uncreatable.
>
To make sure - is it root device? Then it could explain something.
Is it possible to download your installer with LVM root support? I would
give it a try.
-andrej
