Re: HPT372 bug summary [was: RE: escalation stage 2]

2003-07-18 Thread Terry Lambert
Harald Schmalzbauer wrote: Please forget that. It was because for convinience reasons I had turned the 80-pin ATA cables upside down. So the black was at the controller and the blue at the drive. I can't imagine that this makes any technical difference (as long as no slave drive is connected

Re: HPT372 bug summary [was: RE: escalation stage 2]

2003-07-18 Thread Soeren Schmidt
It seems Harald Schmalzbauer wrote: I also think the RAID configuration is stored on the disks since when I create a non-DOS compatible slice (starting at 0 not 63) the RAID configuration vanishes. Yes the Highpoint BIOS uses sector 9 to hold the RAID config, so if you use that for other

Re: HPT372 bug summary [was: RE: escalation stage 2]

2003-07-18 Thread Marcin Dalecki
Harald Schmalzbauer wrote: Harald Schmalzbauer wrote: Ok, like I thought, the disk was not defect. There seems to be a bug in ata regarding HPT372 First: Wiht BIOS version 2.342 the secondary master disk id is incorrectly detected (something liek X X X X X X X X X X X X X X X instead of

RE: HPT372 bug summary [was: RE: escalation stage 2]

2003-07-18 Thread Harald Schmalzbauer
Soeren Schmidt wrote: which is named FreeBSD) And that's why FreeBSD panics until I delete the mirror relationship. Well Highpoints way of dealing with broken arrays and lost disks are less than optimal, I've tried to do my best in the ATA driver to fool the HPT system, but its not

RE: HPT372 bug summary [was: RE: escalation stage 2]

2003-07-17 Thread Harald Schmalzbauer
Harald Schmalzbauer wrote: Ok, like I thought, the disk was not defect. There seems to be a bug in ata regarding HPT372 First: Wiht BIOS version 2.342 the secondary master disk id is incorrectly detected (something liek X X X X X X X X X X X X X X X instead of IC25N030ATCS04-0 Please