suffering data corruption on 200gb drive when drive is 110gb full

[neo149]

I have a Western Digital Cavier 200GB hard drive, which seemed to work fine until now. When the drive gets to 110gb full, the data on it (mainly movies and large files) starts getting corrupted.

I am running Windows XP Pro, on an Epox 8K5A3+ Mobo, with an AMD Athlon XP 1800+, and 1GB DDR RAM. The motherboard has two onboard RAID controllers (Highpoint 374), which the 200gb drive is running from.

This is the URL for the spec of my mobo... http://www.epox.org/products/mainboards/8k5a3plus/

I have tried flashing my BIOS, and althought the BIOS recognises the drive as a 200gb drive (i have changed it to the primary slave for the time being for testing reasons...), when I run the Western Digital testing tools in Windows, it recognises the drive as a 134gb drive (although if you right click on the drive and select properties, Windows reckons the drive is 200gb, or 186gb formatted).

Any help would be appreciated

[CCW]

I have no idea why this is happening, unless the hdd is just working slow which is why you think its corrupted. I can explain however why it would say 134gb. This is because its considered a large drive and 134GBs was the limit however this limit has gone for newer drives.

Craig

[neo149]

I've actually had a bit of luck with this problem now and taken a step forward...

I changed the 200gb to my primary master, and after flashing my BIOS to the latest version (dated 10/25/02), I managed to fill the 200gb drive to 153gb without suffering data corruption. However, when I put the hdd back onto my RAID controller, about 16gb of data got 'corrupted' again, (leaving me with 137gb of data that was uncorrupt). If I switch back to primary master on my mobo, the data is ok again; going back to RAID 'corrupts' it again.

Flashing the BIOS also updated the RAID controller to version 1.22 (from 1.21), and the driver version I'm using in Windows XP Pro is 1.22.8.12 (previously 1.21)

Any ideas...?

[neo149]

Aha!

I've just upgraded my Windows drivers to ver 1.23.0.0, and that seems to have done the trick

[robbie]

Glad to see you got it fixed. I was going to ask what your FSB was set too.
Rob

[keithwalton]

Just to let you know i've had a similar problem with mine (got two of them). i was running it off a hpt370 controller and it did the same thing on both drives really although one was slow, and the other was slow and corrupt.
I had an interim fix of creating 3x 60GB partitions and they were allrite then. I've now got one of them in my new puter, but the other died whilst i was installing an os on it for a 3rd puter, its still sitting on my shelf waiting tobe rma'd

K