Ironman273 Posted May 26, 2015 Share Posted May 26, 2015 I have a customer with 2 500GB drives in RAID 1, partitioned as 100GB to C: and 400GB to D:. Friday Windows started crying about bad blocks, Saturday the MFT got corrupted which rendered D: illegible. Shouldn't the fact that they are RAIDed prevent that if one drive was bad or going bad? Server Admin shows both physical drives as fine. I was able to restore the data and copy it to another drive, reformat and write it back but I'm looking for a cause now. Link to comment Share on other sites More sharing options...
Iphel Posted May 28, 2015 Share Posted May 28, 2015 Hello, Raid does not prevent system files corruption done by a hack or a virus. I know you're talking about bad blocks but since the issue was reported/seen only on the OS side it make me think about a nasty program. Only logs can talk, were you able to access system events ? Link to comment Share on other sites More sharing options...
Zinomian Posted May 28, 2015 Share Posted May 28, 2015 I have seen raid 5 and mirrors have this issue, to the point of me fully rebuilding the raid (new drives, and system image), and even after that, windows will continue to report the bad blocks. I have done full check disks to verify the disk, but the bad blocks continue to be reported. Till this day, I have not found a way to remove the bad blocks tag from windows once it reports them. Link to comment Share on other sites More sharing options...
sc302 Veteran Posted May 28, 2015 Veteran Share Posted May 28, 2015 Raid1 uses one drive and mirrors the other, in case of failure the other drive can be used or swapped for the primary if needed. If it has bad blocks and they have been written to both drives, then both sets are bad. Raid is not a backup or a fail safe in case bad data gets written or good data has been deleted, it is only a protection if a drive or multiple drives die or have complete failure. Link to comment Share on other sites More sharing options...
Recommended Posts