My system has two RAID-1 arrays: Drive C is a pair of WD Raptor X's (150GB each) for the OS + programs (Win 7/Pro, 64-bit) and Drive D is a pair of WD Caviar 500GB for data.
A week after I successfully upgraded from XP/Pro to Win 7/Pro, when I booted this morning I got an usual message while the BIOS was loading:
So I went into the BIOS to see what it had to say:
All for drives (the two for the system array and the two for the data array) were enabled. I next tried to see if I could rebuild the array, but then I didn't know which of the two system drives were bad, so I loaded Macrium Reflect, and image copy/restore utility, and saw this:
It is interesting to note that with this utility you normally see two drives: (C) and (D) ... in this case, you see (C), you see Disk 2 with the disk specs in gray rather than black, and then you see (D). So I immediately made an image copy of the "good" (C) drive, and then tried to make an image copy of what I suppose is the "bad" (C) drive ... and got this screen:
Opps! An error message! "MFT corrupt - Error code = 6. Please run 'chkdisk /f' ... also got a window that said "An error has occurred. Please see the history log for more details." Thus, the history log:
My subsequent research indicates that one should never use scandisk or chkdsk on RAID arrays, and that when there is a hardware error with one of the members, I should not just try to rebuild the array.
Suggestions?
NOTE: Never could get all the screen shots to display, so I created a web page for them: [b]www.WebSquad.com/BadDisk[/b]
A week after I successfully upgraded from XP/Pro to Win 7/Pro, when I booted this morning I got an usual message while the BIOS was loading:
So I went into the BIOS to see what it had to say:
All for drives (the two for the system array and the two for the data array) were enabled. I next tried to see if I could rebuild the array, but then I didn't know which of the two system drives were bad, so I loaded Macrium Reflect, and image copy/restore utility, and saw this:
It is interesting to note that with this utility you normally see two drives: (C) and (D) ... in this case, you see (C), you see Disk 2 with the disk specs in gray rather than black, and then you see (D). So I immediately made an image copy of the "good" (C) drive, and then tried to make an image copy of what I suppose is the "bad" (C) drive ... and got this screen:
Opps! An error message! "MFT corrupt - Error code = 6. Please run 'chkdisk /f' ... also got a window that said "An error has occurred. Please see the history log for more details." Thus, the history log:
My subsequent research indicates that one should never use scandisk or chkdsk on RAID arrays, and that when there is a hardware error with one of the members, I should not just try to rebuild the array.
Suggestions?
NOTE: Never could get all the screen shots to display, so I created a web page for them: [b]www.WebSquad.com/BadDisk[/b]