• 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 configuration spontaneously changed

T

Thanearchon

Member
I would love an explanation for this. I have a gaming rig based on two 10,000 rpm drives in a RAID 0 array, with a separate 2 TB drive for data, plus an old 500 gig drive in two partitions that I recently emptied onto the large drive when I bought it (thank god, as it turns out). Last week, a grinding noise started from one of the drives, which was annoying, but everything seemed to work. Then McAfee downloaded an update and demanded a restart, during which windows failed to boot, and the BIOS stuff seemed to take a long time. Looking at it more carefully, BIOS had decided I now had a RAID 5 array. I disconnected the two extra drives, and the machine booted fine. Adding them back one at a time traced the issue to the older and thankfully empty drive. Any time I connect the SATA cable, the BIOS tries to incorporate it into a RAID 5 array. The grinding noise was also coming from that drive.

I assume the drive failed but can't boot the machine with it hooked in to check. How is this happening? (Just curious at this point, as I seem to have escaped without injury).

Thanks for any thoughts.
 
I don't know what your RAID BIOS is doing, but I think you can safely assume that any disk that starts making a grinding noise needs replacement.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top