Hi all,
A few days ago I reset my BIOS which caused my RAID10 to fail, two of the four disks "fell out" of the array. I'm not booting from this array, it's extra storage. No OS. This is apparently a pretty common situation, BIOS reset causing RAID to fail, so using the methods described here (TGentry post), here, and here, I recreated my RAID10 array and used TestDisk to recover the partition tables. According to BIOS the RAID array is now functioning normally. TestDisk reveals that the file structure of the original array is still intact.
But the above guides get vague for the final stages of recovery, and Windows 7 Pro isn't recognizing the array. I don't know how to fix the MBR, or if that's even the problem, but according to one of the guides, that's the likely final step. I tried using my Win 7 recovery disk, but I really wasn't sure what to do, and the problem wasn't with the boot disk, so it didn't seem to recognize it.
TestDisk indicates something is wrong. See screenshots. It shows what look like two identical partition tables, and neither is bootable. When writing the old partition table to the new array, I used P for "primary", not * for "primary bootable". That was just a guess; guides didn't specify. Perhaps I need to rewrite the partition table as bootable? It also says now that it detects an EFI GPT partition type, but I'm running Intel hardware RAID as far as I know (I'd previously been using Intel Rapid Storage Technology program to monitor the array).
Also, last screenshot, notice how Windows is detecting the array in Disk management. Very odd.
Any help would be much appreciated. I'm getting pretty stressed about this, so, please, only constructive, relevant responses. Thanks everyone.
http://s8.postimg.org/mrqyyeqph/46454541.jpg
http://s8.postimg.org/8zck2rzxx/329392232.jpg
http://s8.postimg.org/aolnaufn9/56343432.jpg
A few days ago I reset my BIOS which caused my RAID10 to fail, two of the four disks "fell out" of the array. I'm not booting from this array, it's extra storage. No OS. This is apparently a pretty common situation, BIOS reset causing RAID to fail, so using the methods described here (TGentry post), here, and here, I recreated my RAID10 array and used TestDisk to recover the partition tables. According to BIOS the RAID array is now functioning normally. TestDisk reveals that the file structure of the original array is still intact.
But the above guides get vague for the final stages of recovery, and Windows 7 Pro isn't recognizing the array. I don't know how to fix the MBR, or if that's even the problem, but according to one of the guides, that's the likely final step. I tried using my Win 7 recovery disk, but I really wasn't sure what to do, and the problem wasn't with the boot disk, so it didn't seem to recognize it.
TestDisk indicates something is wrong. See screenshots. It shows what look like two identical partition tables, and neither is bootable. When writing the old partition table to the new array, I used P for "primary", not * for "primary bootable". That was just a guess; guides didn't specify. Perhaps I need to rewrite the partition table as bootable? It also says now that it detects an EFI GPT partition type, but I'm running Intel hardware RAID as far as I know (I'd previously been using Intel Rapid Storage Technology program to monitor the array).
Also, last screenshot, notice how Windows is detecting the array in Disk management. Very odd.
Any help would be much appreciated. I'm getting pretty stressed about this, so, please, only constructive, relevant responses. Thanks everyone.
http://s8.postimg.org/mrqyyeqph/46454541.jpg
http://s8.postimg.org/8zck2rzxx/329392232.jpg
http://s8.postimg.org/aolnaufn9/56343432.jpg
Facebook
Twitter
Instagram