I have no idea what to do. I have a Soyo KT400 Dragon Ultra with onboard HPT372 chipset. I have installed the drives and created a raid array type 0 in the bios. Linux still detects the drives separately with "unknown partition type". I figured that this is maybe because I need to setup a software raid in linux redhat 8 but I dont know how to do that. Any help will be appreciated. Thanks

I think you're in for an uphill battle. I have a SOYO DRAGON KT333 Ultra with the HPT372 chipset, have been trying to install Redhat 8.0

First off, I have used the highpoint RAID controllers with Linux before, and had a little bit of trouble setting it up but eventually got it. Highpoint usually has some pretty good drivers and docs at their website here:
http://www.highpoint-tech.com/372drivers_down.htm

Unfortunately, they have only gotten up to the 7.3 version of RedHat and 8.0 will NOT work on these versions.
So, I have been having a huge nightmare with this install now for about 7 weeks. I did get it up and running for a bit but it had a dirty shutdown and no matter what i did with fsck, it would not get past the system check on the next reboot and here I am in the same boat again with a new install attempt.

Basically I am saying that I have had PLENTY of experience with this hardware/OS combo and I would almost say:
"abandon hope all ye who enter here"
however, all is not lost.

Basically, if you want to install Redhat 8.0 onto a RAID that you are setting up on the Highpoint bios (by using the ctrl-h access and then creating the RAID) you're most likely in for a huge battle.

My honest suggestion here is to scrap the RAID that you set up with the hpt372. Simply set one of your drives as a boot disk and then use the Redhat install to create a software RAID with the OS controlling it.

I am currently looking at a screen on the other computer that is about 40% finished this process, so I should be able to let you know by the end of the night how it went.

Thanks, I am trying my best to do the same here. The bios created array is not detected by linux. I read somewhere that software raid is the way to go howerver I cannot seem to be able to launch disk druid in RH8. I tried the terminal. cReated /etc/raidtab with
raiddev /dev/md0
raid-level 0
nr-raid-disks 3
persistent-superblock 1
chunk-size 64
device /dev/hde
raid-disk 0
device /dev/hdf
raid-disk 1
device /dev/hdg
raid-disk 2

Did a mkraid /dev/md0
Did a fdisk /dev/md0 and created a primary partition type 83
then created an ext3 partition, labeled it and inputted in fstab. It seemed to work and i can access the raid but
on startup and shutdown of the system I got a lot of errors about hde invalid drive seek or something like that. Reinstalled with Norton Ghost to try again. I am just trying to create a video storage drive for MythTV. I dont need to convert my root partition to Raid. Thanks for any help you can give me.

yeah, i hear ya.
my most recent install didn't go too smoothly with Disk Druid either. (neither did fdisk seem too happy)

in Disk Druid, I can access /dev/hde and /dev/hdg, but once i start setting up the partitions, it starts hanging.
I set a 2000 meg for /
no problem
then I set a 15000 meg for /var
it hangs for about 20 seconds, and then comes back successful
set a 25000 meg for /home and it hangs for about 2 minutes . then comes back successful
then i set a 524 meg chunk as a swap and it just hung hung hung. I took the dog out, went to the gym and came home to see the same hung screen.
hard reboot.

Next time around, i decide to just set a single "/" partition and a swap and let everything reside on the single / (just to see if it the partitioning actually works... hopefully skipping the hang in disk druid).
It didn't hang in the disk druid screen this time, however when it came time for the install procedure to actually format and install these partitions i got an error something like:

"Linux was unable to re-read the partition table on /dev/hde. This means that linux knows nothing about this drive. You should reboot before continuing."

you can't choose "ignore". and the system reboots.

"Ok" I say to myself. "forget disk druid. lets do it the old fashioned way with fdisk"

I got into the screen ok, and it showed me the disk, but once i finished setting up the partitions and hit 'w' to write the table, i got an error that it was unable to write table to /tmp/hde or something like that.

I'm not sure, but I think there is still some sort of a screw up with the highpoint drivers. I see them flash by during the bootup off CD procedure. I think I am going to take the case apart, move the disks off the blue raid IDE slots on the motherboard, plug them into the regular IDE slots and partition them there to remove any communication with anything remotely resembling highpoint.
Then I'll move the drives back onto the highpoint and see if I'm able to fly past the partitioning section of the install.

Considering this is supposed to be a production machine for a mysql/php web server, i can't say my confidence is building too fast in trusting this machine if i DO get it up and running.

ahh ok, i just tried fdisk again and got the actual error here:

command (m for help): w

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table
The new table will be used at the next reboot.
Syncing disks.

Man, good luck to you. I gave up on this raid attempt. Keep getting errors on /dev/hde. Thought my hde was bad. Almost pulled it out. One night wasted. Decided to configure LVM instead. Up and running injust a couple of hours. I guess I am still gui centric. Half the time I wasted trying to figure out how to launch a gui for raid in REdhat 8. I just needed a way to string 3 drives together for MythTV and LVM does fine. Now have a 260 gig LVM logical volume. Again good luck to you.