I have finally gotten some time to get back to my project of making
the installer install on an LVM root (and boot it afterward :-) and I
am pleased to report that my mods work! With a caveat or two that I
am hoping I can get help working out here.
First of all, I need to know, in mkinitrd if it should make an initrd
that supports LVM root mounting. Right now I have it hard coded that
it should. Not good of course.
The changes in the initrd for an LVM root are:
echo 0x3a00 > /proc/sys/kernel/real-root-dev
/sbin/vgscan
/sbin/vgchange -a y
The 0x3a00 as a root device relates to using /dev/VG/lvol1 (on my
system here anyway) as the root device:
[brian@pc brian]$ ls -l /dev/VG
total 0
brw-rw---- 1 root disk 58, 1 Sep 10 23:29 1
crw-r----- 1 root disk 109, 0 Sep 10 23:29 group
brw-rw---- 1 root disk 58, 0 Sep 10 23:29 lvol1
When mkinitrd is run, even from the installer, issuing "rdev" says
that /dev/VG/lvol1 is "/". Is this a safe test in mkinitrd to have it
follow the "LVM root" branch instead of what is there by default?
Also, in the installer, when installing on an LVM "device", when it
comes time to populating the lilo.conf file, for some reason the fully
pathed root device is prefixed with a "/dev" so that it writes
"root=/dev/dev/vg/lvol1".
I'm afraid my perl is not up to snuff enough to suss out in the
installer why this is happening. The install goes on fine if I choose
to edit the image and change the Root field to remove the duplicate
"/dev". Any ideas why this is happening? Is there some logic
somewhere that is supposed to be stripping the /dev from the root
device path that is failing in the case of an LVM device being used?
Thanx,
b.
--
Brian J. Murrell
