i recently migrated by raid 1 mirror set to a new machine. initially i didnt have space for both drives so i used one of the pair for a few days, intending to start a fresh mirror at some point.
i got around to adding the second HDD, and was offered the option to rebuild the array. GREAT i thought! i wont have to wait for the whole 980GB to sync to a new drive, just the handful of unique files i created since spitting the mirror up.
so i ran the rebuild (intel rapid storage) and it took HOURS (about 5)
then when i restarted i got a warning that chkdsk needed to verify my disk. i let it. it took HOURS, finding loads (thousands) of errors and "fixing" them.
now apparently my raid array is fine, but in 2 days ive already found DOZENS of max files that refuse to open and a load of corrupted rars. not looking good. i cant imagine what proportion of my files are damaged, but im not sure what to do.
any suggestions? or am i screwed...?
moral, DONT LET RAID1 GET OUT OF SYNC THEN EXPECT IT TO FIX ITSELF>>! MAKE A NEW MIRROR.
i got around to adding the second HDD, and was offered the option to rebuild the array. GREAT i thought! i wont have to wait for the whole 980GB to sync to a new drive, just the handful of unique files i created since spitting the mirror up.
so i ran the rebuild (intel rapid storage) and it took HOURS (about 5)
then when i restarted i got a warning that chkdsk needed to verify my disk. i let it. it took HOURS, finding loads (thousands) of errors and "fixing" them.
now apparently my raid array is fine, but in 2 days ive already found DOZENS of max files that refuse to open and a load of corrupted rars. not looking good. i cant imagine what proportion of my files are damaged, but im not sure what to do.
any suggestions? or am i screwed...?
moral, DONT LET RAID1 GET OUT OF SYNC THEN EXPECT IT TO FIX ITSELF>>! MAKE A NEW MIRROR.
Comment