RAID: File corruption and all sorts of funky errors

[Goateh]

Hey People,

I'm not sure if this should go in this section but its the closest I could think of regarding this issue. I have 2 x 160GB SATA drives in a RAID 0 configuration on my box (specs below). Sometimes when I download a patch or something it will say its corrupt and can't be read, if I run chkdsk it finds all sorts of index entries and removes them and it will always find problems with the security descriptors.

Before I go all gun-ho and remove RAID to run a test on each drive... can anyone think of a reason why this might be happening? This is pretty frustrating :bang head

[tuskenraider]

Lots of things to check. Bad memory, one or both HDD's going bad, to high of an OC putting bus frequencies or SATA chip out of good operation range, bad SATA cable, bad power connection.

[Goateh]

Damn, I guess I could reduce my OC to see if that helps at all ($#@%!), i could try and find some more SATA cables.. I dunno if the power connection is bad, shouldn't be :(

Cheers for the help. If worst comes to worst I'll tear it down and run tests on the HDDs seperately.

[dmitryk]

Check driver for your SATA Raid as well , try different revisions, maybe old one is more stable then new one and vs versa. Check write cache on in RAID bios as well

[uOpt]

Failed overclock (CPU or memory) or bad memory. Sorry.

[Goateh]

Well, Oddly enough.. it was neither :p

I got bored and ran a check on both HDDs, fine.
Rebuilt my RAID with a different striping this time, 512k, and everything seems fine so far... no corruptions or anything....

I'm rather new to RAID but it is strange :D

[tuskenraider]

Rebuilt my RAID with a different striping this time, 512k, and everything seems fine so far... no corruptions or anything....Well give it some time, corruption slowly seeps in with memory, power and oc'ing issues, hopefully it won't happen, but don't be suprised when it does again. It least you eliminated the drives as the problem. Good luck.

[Goateh]

Yeah, well I have had no drive troubles.. or troubles of any sort... weird :S

[shadowdr]

If you lock your agp to 66 mhz it also locks the pci bus so an oc will not affect it that way. If you use any kind of imaging software to backup your os drive, it will cause security descriptor errors. It is not harmfull to either drive.

[tuskenraider]

If you use any kind of imaging software to backup your os drive, it will cause security descriptor errors. Really? I've had no such thing happen with Drive Image 2002 or Acronis True Image 9.

[Goateh]

Cool, Cheers. I do have it locked at 66Mhz and no backup software installed, could it be a possibility that my on-board raid chip is acting up? Does that get put out of whack when OC'ing?

[shadowdr]

Really? I've had no such thing happen with Drive Image 2002 or Acronis True Image 9.

It is not the fault of any backup software but a small glitch in the NTFS file system. See http://support.microsoft.com/default.aspx?kbid=327009.


I havent seen oc'ing affect data unless the pci bus is not locked. I would lean more towards the mixed ram being the problem. I have seen corruption from the 4276 raid bios before it was pulled from SI's website that was rereleased later.

[Goateh]

Hrmm, I'll try it with better ram and see if it happens. I'm also using the 4.2.5 raid bios, although I dunno if that would make a difference

[RangerXLT8]

An unstable PCI\PCI-E bus will cause corruptions in RAID arrays.

[Goateh]

Oh,

I don't think mines unstable, I have had no problems with it while using them. I suppose I could test and lower my OC (:()

[shadowdr]

You nee not replace the ram but be sure that it passes memtest easily as well as prime and SuperPi.

[Goateh]

Yeah it does, I"ve run prime on this box for stability before. Although I could at least run it again to see if it spits the dummy