hpt37x RAID1 FC5 booting/initrd problem

[n03lm]

I am trying to boot Fedora 5 newly installed on a machine (2.6.15-1.2054_FC5).

I have a highpoint 370 raid card which has 2 x 80GB drives which I want to run as a RAID1. I installed onto one drive with a boroken raid (in bios level) then used the BIOS to create the raid cloning the install to the other drive. I followed http://tienstra4.flatnet.tudelft.nl/~gerte/gen2dmraid/ to get grub working.

I used the linux rescue mode on the install CD (skip to shell) and then "dmraid -ay -v"
INFO: Activating mirror RAID set "hpt37x_bbdcehjdga"
INFO: Activating partition RAID set "hpt37x_bbdcehjdga1"
INFO: Activating partition RAID set "hpt37x_bbdcehjdga2"

and mounted the resultant partition /dev/hpt37x_bbdcehjdga1 as /mnt/sysroot so I know that the array works and is recognised by dmraid.

I have had to force mkinitrd to include the array (by setting DMRAIDS="hpt37x_bbdcehjdga" as chrooting to the mounted array in the rescue mode results in dmraid not reporting anything with dmraid -s -craidname, so my initrd looks like this (i've modifed this to make it noisy and include more echos)

#!/bin/nash

echo Prepare to mount proc
mount -t proc /proc /proc
# setquiet
echo Mounting proc filesystem
echo Mounting sysfs filesystem
mount -t sysfs /sys /sys
echo Creating /dev
mount -o mode=0755 -t tmpfs /dev /dev
mkdir /dev/pts
mount -t devpts -o gid=5,mode=620 /dev/pts /dev/pts
mkdir /dev/shm
mkdir /dev/mapper
echo Creating initial device nodes
mknod /dev/null c 1 3
mknod /dev/zero c 1 5
mknod /dev/systty c 4 0
mknod /dev/tty c 5 0
mknod /dev/console c 5 1
mknod /dev/ptmx c 5 2
mknod /dev/rtc c 10 135
mknod /dev/tty0 c 4 0
mknod /dev/tty1 c 4 1
mknod /dev/tty2 c 4 2
mknod /dev/tty3 c 4 3
mknod /dev/tty4 c 4 4
mknod /dev/tty5 c 4 5
mknod /dev/tty6 c 4 6
mknod /dev/tty7 c 4 7
mknod /dev/tty8 c 4 8
mknod /dev/tty9 c 4 9
mknod /dev/tty10 c 4 10
mknod /dev/tty11 c 4 11
mknod /dev/tty12 c 4 12
mknod /dev/ttyS0 c 4 64
mknod /dev/ttyS1 c 4 65
mknod /dev/ttyS2 c 4 66
mknod /dev/ttyS3 c 4 67
echo Setting up hotplug.
hotplug
echo Creating block device nodes.
mkblkdevs
echo "Loading jbd.ko module"
insmod /lib/jbd.ko 
echo "Loading ext3.ko module"
insmod /lib/ext3.ko 
echo "Loading dm-mod.ko module"
insmod /lib/dm-mod.ko 
echo "Loading dm-mirror.ko module"
insmod /lib/dm-mirror.ko 
echo "Loading dm-zero.ko module"
insmod /lib/dm-zero.ko 
echo "Loading dm-snapshot.ko module"
insmod /lib/dm-snapshot.ko 
mkblkdevs
rmparts hdg
rmparts hde
echo Creating RAID
dm create hpt37x_bbdcehjdga 0 160086518 mirror core 2 64 nosync 2 33:0 0 34:0 10
# resume /dev/mapper/hpt37x_bbdcehjdga2
echo Creating root device.
mkrootdev -t ext3 -o defaults,ro LABEL=/raidroot
echo Mounting root filesystem.
mount /sysroot
echo Setting up other filesystems.
setuproot
echo Switching to new root and running init.
switchroot

my fstab is as follows

LABEL=/raidroot                /                       ext3    defaults        1 1
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
tmpfs                   /dev/shm                tmpfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
sysfs                   /sys                    sysfs   defaults        0 0
/dev/mapper/hpt37x_bbdcehjdga2         swap                    swap    defaults 
       0 0
/dev/hdi6               swap                    swap    defaults        0 0

the array is correctly labeled

linux # e2label /dev/mapper/hpt37x_bbdcehjdga1
/raidroot

my grub.conf is as follows

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You do not have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /, eg.
#          root (hd0,0)
#          kernel /boot/vmlinuz-version ro root=/dev/hde1
#          initrd /boot/initrd-version.img
#boot=/dev/hde
default=1
timeout=10
serial --unit=0 --speed=9600
termial serial
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.15-1.2054_FC5-raidone)
        root (hd0,0)
        kernel /boot/vmlinuz-2.6.15-1.2054_FC5 ro root=LABEL=/raidroot rhgb quiet
        initrd /boot/initrd-2.6.15-1.2054_FC5-raidone.img

title Fedora Core (2.6.15-1.2054_FC5-raid)
        root (hd0,0)
        kernel /boot/vmlinuz-2.6.15-1.2054_FC5 ro root=LABEL=/raidroot rhgb quiet
        initrd /boot/initrd-2.6.15-1.2054_FC5-raid.img

title Fedora Core (2.6.15-1.2054_FC5)
        root (hd0,0)
        kernel /boot/vmlinuz-2.6.15-1.2054_FC5 ro root=LABEL=/raidroot rhgb quiet
        initrd /boot/initrd-2.6.15-1.2054_FC5.img

raidone initrd is vanila --force-raid initrd
raid initrd is one I built above
and the other is the vanila FC5 initrd

I've tried changing root=/dev/mapper/hpt37x_bbdcehjdga1 but whatever I do I get this:

Uncompressing Linux... Ok, booting the kernel
Red Hat nash version 5.0.32 starting
mount: could not find filesystem '/dev/root'
setuproot: moving /dev failed : No such file or directory
setuproot: error mounting /proc : No such file or directory
setuproot: error mounting /sys : No such file or directory
switchroot : mount failed : No such file or directory
Kernel panic - not syncing : Attempted to kill init!

I used to have the system working in mandrake linux and I recall having to fix what used to be pivot-root by forcing the definition of /proc/sys/kernel/real-root-dev in the initrd.

the problem seems to lie with the mkrootdev which either isn't getting the right parameters or similar

Whislt there are explainations on how to get RAID1 working in FC4 the mkinitrd (https://listman.redhat.com/archives/.../msg00027.html) has changed since then, the only formu post I can find on FC5 and raid is about a problem with dm create http://www.fedoraforum.org/forum/sho...d.php?t=102408 and stripped not mirrored arrays.

Can anyone provide suggestions on what I need to do ?