Yes, just got it going. Basically I followed the highpoint installation instructions (found in http://www.highpoint-tech.com/372drivers_down.htm) and installed a redhat 7.2 using the highpoint supplied driver. This gave me a working system with the only disks in the system those attached to the raid controller, using Raid 0 setup using the hardware controller. So my system now boots from /dev/sda with /dev/sda1 being the root partition. Next I downloaded 2.4.18 and patched it to 2.4.19-pre7 and then applied the latest ide patch. (http://www.linuxdiskcert.org/ide-2.4.19-p7.all.convert.6.patch.bz2). >From this point I followed http://solar.murty.net/~murty from step 4. Upgrading to the latest version of lilo (version 22.2 which involved some small tweaks). This is where the problems started and I had to modifiy murty's tutorial. Because my system was using /dev/sda as its boot device and because I didn't have the ataraid code compiled into the kernel which highpoint supplied, lilo was unable to write to its boot information on to the MBR of /dev/ataraid/d0 ( as instructed in lilo.conf with boot=/dev/ataraid/d0 ) so I set boot = /dev/sda and ran lilo successfully, and rebooted. The system came up correctly and then I reverted to murty's settings and set boot = /dev/ataraid/d0 in lilo.conf and re-ran lilo. This is what worked for me, use it at your own risk .... I have a KR7A motherboard from Abit, which is using a HighPoint 372 controller, and I have RAID133A set as my boot device in my bios. Adam On Sat, 2002-04-20 at 18:47, Orlando Richards wrote: > Anyone had any luck getting a boot loader (preferably lilo for my > preference) working on a "hardware" raid device - ie, /dev/ataraid/d0p1? > > If so - how? > > Orlando > ------------- > "War doesn't determine who's right. War determines who's left." > > > > _______________________________________________ > > Ataraid-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/ataraid-list >
