> Good question, because it probably answers why you are having problems
> in the first place.
>
> Since you are using / raid you need a initrd.img that holds and loads
> the
> (new) raid modules before / is mounted. Check your lilo.conf or
> grub.conf to verify that you did use an initrd before.
>
> Check man mkinitrd for details on how to create an initrd image.
Okay. lilo.conf uses an initrd image for both the 2.4.9-34 kernel, as well
as the 2.4.20-18.7 copy.
Really dumb question, but does the ordering of directives in lilo.conf
matter? This is what it looks like:
prompt
timeout=50
default=linux.bak
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
lba32
image=/boot/vmlinuz-2.4.9-34
label=linux.bak
initrd=/boot/initrd-2.4.9-34.img
read-only
root=/dev/md0
image=/boot/vmlinuz-2.4.20-18.7
label=linux
root=/dev/md0
read-only
initrd=/boot/initrd-2.4.20-18.7.img
I'm going to try arranging the directives for 2.4.20-18.7 in the same order
as 2.4.9-34.
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list
