Unregistered

[Log in to get rid of this advertisement]

Mobo: Epox 8KRA2+ Via KT600 Hpt372 Via Sata-Raid(8237)

boot options: hde=noprobe hdf=noprobe hdg=noprobe hdh=noprobe

Or your ARRAYS will be crunched, since most kernel has ide support for hpt37x. And strangely the hidden discs ca be accessed!!

You will have to compile it with FC1.

Otherwise follow the Install_Redhat9_HPT37x2.pdf

Looks as it only works with one array, my second Array as slave on the Pri & Sec interfaces were deleted, and the discs appeared as two discs after boot!!!

The Gui works..

Haven't tested it for robustness, rebuilding etc.. yet!

Upgrading to FC2 seems to be a hassle..

Tamsco

I got mine with my motherboard Abit KD7 RAID. I followed the instructions they gavce, it crashed the compuiter during install. I looked at about 30 threads on Fedora's site, couldn't figure it out.

Highpoint is tough to contact and they don't help.

Recommendation, I wouldn't use it unless you know how to recomplie your kernel and install it from source.

d_t_baker

Hi.

Got called in to fix a Red Hat 9 problem, running software raid.

00:0e.0 RAID bus controller: Triones Technologies, Inc. HPT366/368/370/370A/372 (rev 05)

You mentioned the array would be "crunched" if it didnt have those hde=noprobe kernel boot parameters.
The machine I am using to check the harddrives was having these errors:

It would recognize the partition table fine (fdisk), however not the individual partitions.

# cat /dev/hdg7
cat: /dev/hdg7: Input/output error

hdg7: bad access: block=20, count=12
end_request: I/O error, dev 22:07 (hdg), sector 20
hdg7: bad access: block=22, count=10
end_request: I/O error, dev 22:07 (hdg), sector 22
hdg7: bad access: block=24, count=8
end_request: I/O error, dev 22:07 (hdg), sector 24
hdg7: bad access: block=26, count=6
end_request: I/O error, dev 22:07 (hdg), sector 26
hdg7: bad access: block=28, count=4
end_request: I/O error, dev 22:07 (hdg), sector 28
hdg7: bad access: block=30, count=2
end_request: I/O error, dev 22:07 (hdg), sector 30
etc...

is this due to the "crunched" array ?

Also when i tried to rebuild the software array I would get errors along the lines of:

mdadm: /dev/hde1 is too small: 0K
mdadm: /dev/hdg1 is too small: 0K
mdadm: create aborted

i am unsure if this is a linux or hardware problem?

dave.

Electro

I had no problems since kernel 2.4.16 with ABIT KA7-100 and ABIT TH7II-RAID. The HPT372 is just HPT370 with software RAID.