Chris,
I ran into exactly the same problem as you did with Redhat 6.0 and did find
a solution after much searching. It seems this part is missing in the
documentation for 0.90. Your very close. Only one step to do and you'll
be up and running. You dont need to recompile the kernel and this will
work with either 2.2.5-15 or 2.2.5-22. I had it working in 2.2.5-15smp and
then upgraded after that to 2.2.5-22smp
I found the answer while searching the Redhat Knowledge base. It was:
REF#990511-0097
Installation with compaq smart array
I found it solved my problem with software Raid1 just as well. The answer
is you have to set up raid1 support into the initrd.
To do this cd into the:
/lib/modules/2.2.5-22/block
directory or the block directory for what ever version of the kernel you
have. If you have a SMP kernel then you'll want to do these same steps for
the SMP kernel and the regular kernel. If you do a 'ls' you'll see a
number of object modules. You need to run the following command
(substituting your kernel version) for raid1 support as root in that
directory:
mkinitrd -v --with=raid1 initrd-2.2.5-22raid.img 2.2.5-22
You'll see it mention raid1.o while it's creating the
initrd-2.2.5-22raid.img initrd. Next copy this to your boot dir:
mv initrd-2.2.5-22raid.img /boot
You need to refer to this new initrd in your /etc/lilo.conf file. Add a
new stanza:
image=/boot/vmlinuz-2.2.5-22
label=linux
root=/dev/hda5
initrd=/boot/initrd-2.2.5-22raid.img
read-only
Assuming above that /dev/hda5 is your root device. Note that your actual
boot kernel does not change at all, only the initrd does to reflect the new
initrd you just made. Now run:
lilo -v
to write the changes and reboot. You should come up fine now.
Kevin
>I was wondering if someone could verify that I have to patch the RH 6.0
>kernel to correctly configure and setup a RAID 1 array. The reason for
>my question is because I've setup a RAID 1 array by installing the raidtools
>0.90 rpm package only. Out of the box the RH 6.0 seemed to have /proc/mdstat
>available along with the /dev/md* devices already created. Again this was
>without me having to manually patch and recompile the kernel...
>
>However, after I changed my disk partitions with fdisk to type 0xfd, in order
>to use autodetection, it seems a though I couldn't reboot my machine and
>was always dumped into root maintenance mode...
>
>It would be greatly appreciated if someone could let me know if I really need
>to apply the kernel patches and rebuild the kernel in order for everything to
>work correctly
>
>Thanks in advance
>
>-- Chris
>
>////////////////////////////////////////////////////////////////////////////
>// //
>// Christopher A. Gantz, MTS email: [EMAIL PROTECTED] //
>// Lucent Technologies, Bell Labs Innovation //
>// Rm 37W07, 11900 N. Pecos St. voice: (303) 538-0101 //
>// Westminster, CO 80234 fax: (303) 538-3155 //
>// http://info.dr.lucent.com/~cgantz //
>// //
>////////////////////////////////////////////////////////////////////////////
>
>
