• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Raid Failure

T

Thorny

Golden Member
I've never heard of this before, but was just putting together a new system after my old MB fried. I lost my Raid 0 array due to the system change so set up a Raid 1 so I'd never lose 5 years worth of data again. After installing XP and all service packs and half of my programs in an all nighter I decide to start overclocking. I had my FSB up to about 230 when I had a boot failure, but I noticed on my post that my via raid looked funny. I rebooted with stock timings and I had an UNRECOVERABLE raid failure and lost everything. How does this happen, especially with Raid 1??? Bad controller? I wouldn't think that a 230 Fsb would take out my raid.

Has anyone ever lost an array like this before. I used to think that raid 1 was flawless, but know better now. My specs are

Asus A8V Deluxe
Venice 3000+
2X512 OCZ Platinum R2
Radeon 9800 pro 256
antec 300w PS
2x160 GB Sata hd's
zalman 7000b hsf
 
The bus to the raid controller probably was run out of spec (too fast) and the data was corrupted before it hit the raid array. Garbage in , garbage out. Not the raids fault.
 
Raid 1 will only save you from a hard drive failure. The controller will faithfully copy whatever data is sent to it to both hard drives. If the data is corupted, it's corupted on both drives. Your overclock caused corrupt data to be saved and hoosed windows. It's not the raid controllers fault. Overclocking the processor can also cause the speed of the PCI bus to increase. You were also overclocking your raid card and it failed.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top