Overclock.net › Forums › Components › Hard Drives & Storage › RAID Controllers and Software › HowTo : Recover Intel RAID "Non-Member Disk" Error..
New Posts  All Forums:Forum Nav:

HowTo : Recover Intel RAID "Non-Member Disk" Error.. - Page 15

post #141 of 278
WARNING DO NOT USE THIS GUIDE: Read this whole thread and if your OS is NOT on the raid 5 this follow what TheAssimilator said.

This guide really need to be corrected, I almost lost everything.

Test disk didnt work for me as my intel program blanked out that area of the drive.

I got my data back with ZAR 9.2 paid version. It took 10 days or so but I have my photos back.

http://www.z-a-recovery.com/data-recovery-forum/showthread.php?t=3530
i5 2500k
(13 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500k Asrock Extreme4 XFX 5870 4GB 1333mhz 
Hard DriveOptical DriveOSMonitor
750gb x 2 RAID 0 Asus Vista 32 Westinghouse 42 1080p 
PowerCaseMouse
OCZ 700W P180 G9 
  hide details  
Reply
i5 2500k
(13 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500k Asrock Extreme4 XFX 5870 4GB 1333mhz 
Hard DriveOptical DriveOSMonitor
750gb x 2 RAID 0 Asus Vista 32 Westinghouse 42 1080p 
PowerCaseMouse
OCZ 700W P180 G9 
  hide details  
Reply
post #142 of 278
Quote:
Originally Posted by TechnoSmurf View Post

WARNING DO NOT USE THIS GUIDE: Read this whole thread and if your OS is NOT on the raid 5 this follow what TheAssimilator said.

This guide really need to be corrected, I almost lost everything.

Test disk didnt work for me as my intel program blanked out that area of the drive.

I got my data back with ZAR 9.2 paid version. It took 10 days or so but I have my photos back.

http://www.z-a-recovery.com/data-recovery-forum/showthread.php?t=3530

You're right, the guide DOES need to be updated. Several others including myself have added or revised parts of it along the way, but none of these changes have appeared on the first page.

That said, it really does work. I've been able to reliably recover multiple RAIDs on multiple systems, including my own sigrig Arcane multiple times. Recovery is extremely quick, safe, and free.

I've used other recovery software in the past, and this method (with revisions made it it, as mentioned) is by far the quickest and most reliable. Other methods frequently brick drives (not just the data, the entire drive), take several hours/days, or or recover only a small portion of data, with massive corruption.

Of course, there are multiple ways for a RAID to fail. This method only works on certain issues unique to the ICH10R chipset and the way it integrates into some motherboards. If you can't identify the issues ahead of time, any fix attempt is risky.
Arcane
(33 items)
 
Sanctum
(9 items)
 
Fukurou
(15 items)
 
CPUMotherboardGraphicsGraphics
Core i7 980x GIGABYTE GA-EX58-UD5 MSI RX 480 GAMING X 4GB MSI GeForce GTX 680 Lightning 
RAMHard DriveHard DriveHard Drive
Kingston HyperX T1 Intel X25-M WD Caviar Black FASS Plextor M5S 
Hard DriveHard DriveOptical DriveOptical Drive
WD Velociraptor WD Caviar Black FALS Sony DVD Burner w/ Lightscribe LG Bluray + HDDVD 
CoolingCoolingCoolingOS
Black Ice GTX 360 Black Ice GTX 240 Panaflo High Speed - Push-Pull w/ shrouds Windows 7 Pro (64) 
OSMonitorMonitorKeyboard
Ubuntu (64) X-Star DP2710 ASUS VK266H Black 25.5" 2ms LCD X-Armor U9BL (Mech) 
PowerCaseMouseMouse Pad
EVGA 1000 P2 Cooler Master HAF 932 Razer Deathadder Chroma Cougar Control 
AudioAudioAudioAudio
ATH-A900X Maudio AV-40 Polk PSW-10 Zalman Mic-1 (Clip-on Mic) 
AudioOtherOtherOther
Sound Blaster X7 LE Logitech G13 Wacom Intuos 3 Scythe "3-Foot Switch" 
Other
Modded PS4, PS3, Xbox 360, and Logitech PC Cont... 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 MSI B350M Mortar Arctic RX Vega 64 G.Skill TridentZ  
Hard DriveHard DriveOSPower
Samsung EVO 960 Consatellation Windows 10 Pro Corsair HX 1050 
Case
Raijintek Aeneas White Window 
CPUMotherboardRAMHard Drive
Core i5-661 GA-H55-USB3 12GB DDR3 1333 WD Caviar Black AALS 640GB 
Hard DriveHard DriveOptical DriveCooling
WD Caviar Green EARS 2TB Vertex Turbo 60GB (SSD) Samsung Blu-ray, Samsung DVD Burner H50 (With push/pull nocturas) 
OSMonitorKeyboardPower
Windows 10 Professional 64 LG 47inch LED LCD Saitek Eclipse Lite-touch Wireless Seasonic X750 Gold 
CaseAudio
CM690 II Passive bookshelfspeakers + amp. 
  hide details  
Reply
Arcane
(33 items)
 
Sanctum
(9 items)
 
Fukurou
(15 items)
 
CPUMotherboardGraphicsGraphics
Core i7 980x GIGABYTE GA-EX58-UD5 MSI RX 480 GAMING X 4GB MSI GeForce GTX 680 Lightning 
RAMHard DriveHard DriveHard Drive
Kingston HyperX T1 Intel X25-M WD Caviar Black FASS Plextor M5S 
Hard DriveHard DriveOptical DriveOptical Drive
WD Velociraptor WD Caviar Black FALS Sony DVD Burner w/ Lightscribe LG Bluray + HDDVD 
CoolingCoolingCoolingOS
Black Ice GTX 360 Black Ice GTX 240 Panaflo High Speed - Push-Pull w/ shrouds Windows 7 Pro (64) 
OSMonitorMonitorKeyboard
Ubuntu (64) X-Star DP2710 ASUS VK266H Black 25.5" 2ms LCD X-Armor U9BL (Mech) 
PowerCaseMouseMouse Pad
EVGA 1000 P2 Cooler Master HAF 932 Razer Deathadder Chroma Cougar Control 
AudioAudioAudioAudio
ATH-A900X Maudio AV-40 Polk PSW-10 Zalman Mic-1 (Clip-on Mic) 
AudioOtherOtherOther
Sound Blaster X7 LE Logitech G13 Wacom Intuos 3 Scythe "3-Foot Switch" 
Other
Modded PS4, PS3, Xbox 360, and Logitech PC Cont... 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 MSI B350M Mortar Arctic RX Vega 64 G.Skill TridentZ  
Hard DriveHard DriveOSPower
Samsung EVO 960 Consatellation Windows 10 Pro Corsair HX 1050 
Case
Raijintek Aeneas White Window 
CPUMotherboardRAMHard Drive
Core i5-661 GA-H55-USB3 12GB DDR3 1333 WD Caviar Black AALS 640GB 
Hard DriveHard DriveOptical DriveCooling
WD Caviar Green EARS 2TB Vertex Turbo 60GB (SSD) Samsung Blu-ray, Samsung DVD Burner H50 (With push/pull nocturas) 
OSMonitorKeyboardPower
Windows 10 Professional 64 LG 47inch LED LCD Saitek Eclipse Lite-touch Wireless Seasonic X750 Gold 
CaseAudio
CM690 II Passive bookshelfspeakers + amp. 
  hide details  
Reply
post #143 of 278
Hi, so glad to see this thread still alive, obviously a HUGE problem, and one that should never exist from intel!

I have read the thread a few times now, alot of which seems to be based around raid 5 or raid 10, i had a raid 0 and want to know if these steps are right or not, it is still slightly a little confusing

Asus Sabertooth x58
2x WD 1.5TB drives Raid -0
1- 3TB partition

Make sure Intel software not installed
In raid setup in bios, delete the array with the non-member disk
Re create array (hopefully with same options, it was made several years ago)
Run Testdisk
this is where i get confused, in the test disk step by step it says select drive with missing partition, can you select the array or do i need to figure out somehow which drive was the 'non member'? do i run it on both drives seperatly?
start a serch, then T to change to deep search
list files
Now some posts say exit out and some say write files?
ANY help at all would be absolutly greatfully appreciated
Thanks
post #144 of 278
Quote:
Originally Posted by TheonlyReaper View Post

Hi, so glad to see this thread still alive, obviously a HUGE problem, and one that should never exist from intel!

I have read the thread a few times now, alot of which seems to be based around raid 5 or raid 10, i had a raid 0 and want to know if these steps are right or not, it is still slightly a little confusing

Asus Sabertooth x58
2x WD 1.5TB drives Raid -0
1- 3TB partition

Make sure Intel software not installed
In raid setup in bios, delete the array with the non-member disk
Re create array (hopefully with same options, it was made several years ago)
Run Testdisk
this is where i get confused, in the test disk step by step it says select drive with missing partition, can you select the array or do i need to figure out somehow which drive was the 'non member'? do i run it on both drives seperatly?
start a serch, then T to change to deep search
list files
Now some posts say exit out and some say write files?
ANY help at all would be absolutly greatfully appreciated
Thanks

You select the RAID, not the individual drive.

As for the exiting part, I don't really remember, but it should be pretty straight forward when you're actually looking at the prompt.

Oh, and if you don't get the RAID settings right, you're 100% screwed. You should be able to enter the RAID setup in bios and see what the settings are prior to deleting the RAID though, so write that down. If not, good luck.
Arcane
(33 items)
 
Sanctum
(9 items)
 
Fukurou
(15 items)
 
CPUMotherboardGraphicsGraphics
Core i7 980x GIGABYTE GA-EX58-UD5 MSI RX 480 GAMING X 4GB MSI GeForce GTX 680 Lightning 
RAMHard DriveHard DriveHard Drive
Kingston HyperX T1 Intel X25-M WD Caviar Black FASS Plextor M5S 
Hard DriveHard DriveOptical DriveOptical Drive
WD Velociraptor WD Caviar Black FALS Sony DVD Burner w/ Lightscribe LG Bluray + HDDVD 
CoolingCoolingCoolingOS
Black Ice GTX 360 Black Ice GTX 240 Panaflo High Speed - Push-Pull w/ shrouds Windows 7 Pro (64) 
OSMonitorMonitorKeyboard
Ubuntu (64) X-Star DP2710 ASUS VK266H Black 25.5" 2ms LCD X-Armor U9BL (Mech) 
PowerCaseMouseMouse Pad
EVGA 1000 P2 Cooler Master HAF 932 Razer Deathadder Chroma Cougar Control 
AudioAudioAudioAudio
ATH-A900X Maudio AV-40 Polk PSW-10 Zalman Mic-1 (Clip-on Mic) 
AudioOtherOtherOther
Sound Blaster X7 LE Logitech G13 Wacom Intuos 3 Scythe "3-Foot Switch" 
Other
Modded PS4, PS3, Xbox 360, and Logitech PC Cont... 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 MSI B350M Mortar Arctic RX Vega 64 G.Skill TridentZ  
Hard DriveHard DriveOSPower
Samsung EVO 960 Consatellation Windows 10 Pro Corsair HX 1050 
Case
Raijintek Aeneas White Window 
CPUMotherboardRAMHard Drive
Core i5-661 GA-H55-USB3 12GB DDR3 1333 WD Caviar Black AALS 640GB 
Hard DriveHard DriveOptical DriveCooling
WD Caviar Green EARS 2TB Vertex Turbo 60GB (SSD) Samsung Blu-ray, Samsung DVD Burner H50 (With push/pull nocturas) 
OSMonitorKeyboardPower
Windows 10 Professional 64 LG 47inch LED LCD Saitek Eclipse Lite-touch Wireless Seasonic X750 Gold 
CaseAudio
CM690 II Passive bookshelfspeakers + amp. 
  hide details  
Reply
Arcane
(33 items)
 
Sanctum
(9 items)
 
Fukurou
(15 items)
 
CPUMotherboardGraphicsGraphics
Core i7 980x GIGABYTE GA-EX58-UD5 MSI RX 480 GAMING X 4GB MSI GeForce GTX 680 Lightning 
RAMHard DriveHard DriveHard Drive
Kingston HyperX T1 Intel X25-M WD Caviar Black FASS Plextor M5S 
Hard DriveHard DriveOptical DriveOptical Drive
WD Velociraptor WD Caviar Black FALS Sony DVD Burner w/ Lightscribe LG Bluray + HDDVD 
CoolingCoolingCoolingOS
Black Ice GTX 360 Black Ice GTX 240 Panaflo High Speed - Push-Pull w/ shrouds Windows 7 Pro (64) 
OSMonitorMonitorKeyboard
Ubuntu (64) X-Star DP2710 ASUS VK266H Black 25.5" 2ms LCD X-Armor U9BL (Mech) 
PowerCaseMouseMouse Pad
EVGA 1000 P2 Cooler Master HAF 932 Razer Deathadder Chroma Cougar Control 
AudioAudioAudioAudio
ATH-A900X Maudio AV-40 Polk PSW-10 Zalman Mic-1 (Clip-on Mic) 
AudioOtherOtherOther
Sound Blaster X7 LE Logitech G13 Wacom Intuos 3 Scythe "3-Foot Switch" 
Other
Modded PS4, PS3, Xbox 360, and Logitech PC Cont... 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 MSI B350M Mortar Arctic RX Vega 64 G.Skill TridentZ  
Hard DriveHard DriveOSPower
Samsung EVO 960 Consatellation Windows 10 Pro Corsair HX 1050 
Case
Raijintek Aeneas White Window 
CPUMotherboardRAMHard Drive
Core i5-661 GA-H55-USB3 12GB DDR3 1333 WD Caviar Black AALS 640GB 
Hard DriveHard DriveOptical DriveCooling
WD Caviar Green EARS 2TB Vertex Turbo 60GB (SSD) Samsung Blu-ray, Samsung DVD Burner H50 (With push/pull nocturas) 
OSMonitorKeyboardPower
Windows 10 Professional 64 LG 47inch LED LCD Saitek Eclipse Lite-touch Wireless Seasonic X750 Gold 
CaseAudio
CM690 II Passive bookshelfspeakers + amp. 
  hide details  
Reply
post #145 of 278
OMG WOW THE EXCITEMENT!!

This worked exactly! took about 30sec total!

THANK YOU SO MUCH!
Quote:
Originally Posted by TheAssimilator View Post

I just registered an account here to say THANK YOU to the OP as well as the creator of TestDisk. This guide saved my bacon after I migrated my 6x 2TB RAID-5 array (non-bootable) from a Q45 to a Z68 board and the Intel RAID engine on the new board decided that 3 of the disks were no longer array members.

Here's exactly what to do to recover a "lost" RAID-5 volume:

1. Uninstall Intel RST from Windows. This step is critical! If you do not do this, you will lose all your data when you get to step (4)!
2. Reboot into the RAID console, reset all member disks to be non-member
3. Create a new array with the exact same parameters (name, stripe size) as the original one
4. Reboot into Windows, run TestDisk, start "Quick Search"
5. Stop Quick Search immediately after it has started, immediately start the "Deeper Search"
6. Wait until Deeper Search had found the correct partition (should take under 10 seconds), stop it from scanning
7. Mark the partition as Primary, write partition data to it
8. Reboot into Windows and everything should be hunky dory!

Note number (5). It seems if you have anything other than a RAID-0 setup, or a particularly large partition, the Quick Search doesn't work too well. In particular I tried running it for 4 hours, with it coming up with nothing... as soon as I went for Deeper Search my partition popped up.

2x 1.5TB Raid -0
FULL of data. cant believe it worked just like that so simple!
post #146 of 278
Not much feedback on my post, #117, Page 12. Perhaps your problem is the same as I had, the older Intel RAID software. Disks appeared to fail, but were actually OK.
post #147 of 278
Hello,

This is my system:
* i7-2700k CPU
* 16 MB Memory
* ASUS P8P67 DELUXE
* Windows 7 Professional 64 bit (6.1.7601 Service Pack 1)

I updated the BIOS for my ASUS P8P67 Deluxe motherboard and in the process the computer rebooted with the four WD Green 1.5 TB SATA RAID 10 drives set to AHCI in the BIOS. When I realized the Raid 10 volume was missing, I returned to the BIOS and reset the drives appropriately. Then, when looked in the Intel Matrix Storage Manager BIOS, I found the RAID 10 listed as Failed and the status of the last two disks were listed as Non-Raid Disk. Of course, I then panicked and dove into internet research to try to resolve the issue. I found the following (and other very similar potential solutions):

> 1. Reset both HDs to non-member using Intel BIOS utility - the utility warns that all data will be lost - in fact only metadata is lost and can be recreated using steps below.
> 2. Create a new array with identical settings as the broken array. It is critical that the HDs are in the array the same order as before. I was reconnecting the drives several times and lost track of correct order. Because of that I had to go through the steps twice (I guessed wrong the first time).
> 3. Get TestDisk from http://www.cgsecurity.org. I used Windows version (I installed a new Vista on a separate HD for this purpose).
> 4. Run TestDisk according to steps on the web site. If your HDs are connected in correct order, TestDisk should find the lost partition(s) within a few seconds. It ran for several hours, scanning my array and never found anything because I had HDs were connected in wrong order. After I changed the order and restarted from step #1 TestDisk found the missing partition immediately.
> 5. Have the TestDisk write the fixed partition table to the drive and reboot.
> 6. Now all your data on the array should be readable but the system might not boot (it didn't for me).

This is what I have done thus far:

1. Since my Windows 7 Professional 64 bit OS resides on my Corsair Force 3 SCSI Disk, which is not part of the RAID, I booted normally, stopped the Intel Rapid Storage Technology service and set it to MANUAL start, then rebooted.
2. Entered Intel Matrix Rapid Storage Manager BIOS and noted the specifics of the Failed RAID 10.
3. Reset my two Member Disks to Non-RAID Disk, so that all four were now Non-RAID Disks.
4. Created a new RAID 10 using the noted elements of the previous RAID 10 that failed. I did not unplug the physical disks, so the disk order in the new RAID 10 should be the same as the Failed RAID 10. The notable difference was the new RAID 10 was now listed as bootable, but I do not believe the Failed Raid 10 was ever bootable. I tried to find a way to set it to Non-Bootable, without success.
5. Booted normally, initialized the RAID 10 volume as GPT, downloaded TestDisk 6.14 and ran it As Administrator to Analyze GPT via Quick Search. I stopped Quick Search after ten minutes or so and continued with Deeper Search, which found the name of my RAID 10 (Imagery) within a few minutes. I marked the partition as PRIMARY, wrote it and rebooted.
6. Just after the Windows 7 screen appeared, the OS wanted to run CHKDSK, which I declined. When I tried to access the RAID 10 via Explorer, I received the following: F:/ is not accessible. The file or directory is corrupted & unreadable.
7. Restarted the Intel Rapid Storage Technology service and set it to AUTOMATIC start, then rebooted.
8. Once again, Just after the Windows 7 screen appeared, the OS wanted to run CHKDSK, which I declined. When I tried to access the RAID 10 via Explorer, I received the following: F:/ is not accessible. The file or directory is corrupted & unreadable. The volume is listed as unformatted in Partition Manager 11.
9. I ran TestDisk again to check on files in the partition and did not find anything. I am not sure where I went wrong.

Does anyone have any advice for what I should try next?

Thank you!
Intel E8600
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core 2 Duo E8600 ASUS P5Q-E LGA 775 Motherboard EVGA NVIDIA GeForce GTX 460 (Fermi) Superclocked Kingston HyperX 2GB x 4 (8GB total) DDR2-800 
Hard DriveOptical DriveOSMonitor
Western Digital Caviar Green WD20EARS 2GB x 5 LG Blu-ray GGW-H20L XP Professional x64 Dell 2209WA 
PowerCase
Corsair 1050W Thermaltake Spedo 
  hide details  
Reply
Intel E8600
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core 2 Duo E8600 ASUS P5Q-E LGA 775 Motherboard EVGA NVIDIA GeForce GTX 460 (Fermi) Superclocked Kingston HyperX 2GB x 4 (8GB total) DDR2-800 
Hard DriveOptical DriveOSMonitor
Western Digital Caviar Green WD20EARS 2GB x 5 LG Blu-ray GGW-H20L XP Professional x64 Dell 2209WA 
PowerCase
Corsair 1050W Thermaltake Spedo 
  hide details  
Reply
post #148 of 278
Beware RAID5 Configs with this recovery process

Hi All,

I too have been hit by this issue but I have a different theory about what might be going on.

Backstory:
Last night I upgraded the BIOS on my P8P67 motherboard to work around a compatibility issue.
After the BIOS updated the machine rebooted into windows successfully but my D: drive was not available.

My config is:
c_drive -> 1TB stand alone boot disk (Attached to intel controller, just not a raid member)
d_drive -> Raid5 array of 4 * 2TB with 64KB stripes

On rebooting into the BIOS I found that the RAID config had been cleared so I re-enabled raid and rebooted.
Again d_drive was not available.
Looking at the settings I found that all of my 4 2TB disks were being reported as "non-member-disks"
That started me on the google search that lead here.

The Theory
I've read all the posts here today and was almost ready to try the advice below when I started to think about the mechanism by which this works.

Clearly the creation of a new raid array is broken into 2 steps in Intel RST:

1) BIOS configuration of the RAID array
-- It seems likely from the discussion here that this does nothing but write some metadata to the start of each disk

2) Intel RST driver under windows - initialises the new array
-- This seems to be the key warning from Zero4549 in the message below. (i.e. avoid the intel rst driver under windows)

As suggested, to avoid the risk of the Intel driver starting to write to my disks before partition recovery, I installed a clean copy of windows 7 on a spare disk.
However there is a catch 22. In order for the Win7 install to work when the BIOS is configured for "RAID" mode, you must install the OS in Raid mode.
But by doing this the Intel driver is automatically installed by windows, as it needs this to even see the raid disk.
As such, even my clean OS install has the Intel RST driver as it is auto-detected. Of course it doesn't have the Intel RST GUI app installed, but from what I have read, this is primarily a front end to show you what the underlying driver is doing. i.e. The driver will start its work in any case, the GUI is just there to allow you to see what is happening and to manage events such as raid config changes, degradation etc.
I can't point to any direct evidence that this is the case, but it does seem strongly plausible. (at least to me)
On my clean Install the driver I see in driver manager is:
c:\windows\system32\drivers\iaStorV.sys (V 8.6.2.1012)
"Intel(R) ICH8R/ICH9R/ICH10R/DO SATA RAID Controller"


It does beg the obvious question, if that is the case, then how is anyone on this forum having a successful result.
The prevailing theory up to now was that if your raid was on boot drive, you were probably OK, and if it wasn't (as in my case) you had to make sure to uninstall the RST drivers before going back into windows. (Note: Windows only lets you uninstall the Intel GUI, it specifically warns that the driver itself won't be uninstalled)

However, I have a different theory. What if the difference here is more to do with the chosen RAID config.
Looking back at all the posts to date, I've noticed that the many success stories all appear to be from people with RAID 0/1/10 configs.
Also in the several cases where people have reported data loss, Raid5 is a common config. I haven't been able to find a story where a RAID5 users has had a positive outcome (short of using 3rd party data recovery tools).

I'm guessing that the Intel driver is in some way doing more damage when it sees a RAID5 config than a RAID 0/1/10.
I don't have a good explanation for that, but it could have to do with the need to calculate the parity stripe.

Bottom line is; I'm now very concerned that my RAID5 array will get corrupted as soon as I boot into windows.
Before I take that huge risk, I'd be very interested to hear from other members of this forum.
- Is my suggestion plausible?
- Can you point to evidence that contradicts it (e.g. A raid5 user for whom this worked flawlessly)

Note: I do have detailed notes and photos from when I installed the Raid Array originally, so I'm very confident that I can match the raid config exactly, if I do decide to take the chance on this.

I look forward to hearing from you.

This thread is an amazing resource and it is a real shame that this info isn't directly available on the Intel RST website.

Quote:
Originally Posted by Zero4549 View Post

Solved it a few hours ago. Was able to repair the array after carefully reading the whole guide thread over several times and making some wild-guess modifications to the procedure based on the issues people were having.

What I did, new/modified steps in green:
1) Booted into windows and uninstalled Intel Matrix / Intel Rapid Storage software!
2) Rebooted, Reset to non-raid (did not delete)
3) Build new raid identical to previous one.
4) Booted into windows and used TestDisk to analyze.
5) Quick Search with Testdisk returned no readable files/
6) Deeper search revealed the original RAID 10 partition after about 10 seconds (it continued for what would have been several hours afterwards, discovering error after error after error until I stopped it).
7) RAID 10 partition showed correct files, marked it as primary partition, wrote partition data to disk using testdisk
8) Rebooted
9) Re-established links within windows (and re-installed chrome... for whatever reason that and only that got corrupted in the process... and it wasn't even on the raid to begin with! I was on C! As soon as I reinstalled it, all the bookmarks, extensions, and settings were in place automatically. Whatever)

Note that my raid was my "d" drive and not my "c". I believe this is the key! The majority of users following this guide have had their RAID as their C drive and as such when they followed this guide, the intel software was not readable until the process was finished. For several users the method did not work due to intel software attempting to re-initialize the new raid therefore overwriting old data - these users logically had a separate C drive where the intel software was free to work while attempting this fix.

In other words, if your raid is NOT your C drive, you must first uninstall intel software to prevent erroneous re-initialization.

Anyway, thanks for your input mmiszkiel. +rep for responding helpfully even if it was a wee bit late wink.gif
post #149 of 278
This is what I did to recover my RAID 10 files after repeated attempts with TestDisk, ZAR and RAID Reconstructor failed:
1. Downloaded and used Free RAID Recovery from here: http://www.freeraidrecovery.com. The software provided the RAID 10 configuration to recover the information.
2. Paid $79.95, downloaded and used ReclaiMe File Recovery Standard from here:http://www.reclaime.com/buynow.aspx.

It is possible I could have used the configuration that Free RAID recovery provided to in step 1 with TestDisk and recovered the files for free. But, I had already invested more than a week of experimenting with various recovery attempts without any success and I had deadlines to meet.

I hope this information helps one of you recover your failed RAID 10 data. I wish you all the best.
Intel E8600
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core 2 Duo E8600 ASUS P5Q-E LGA 775 Motherboard EVGA NVIDIA GeForce GTX 460 (Fermi) Superclocked Kingston HyperX 2GB x 4 (8GB total) DDR2-800 
Hard DriveOptical DriveOSMonitor
Western Digital Caviar Green WD20EARS 2GB x 5 LG Blu-ray GGW-H20L XP Professional x64 Dell 2209WA 
PowerCase
Corsair 1050W Thermaltake Spedo 
  hide details  
Reply
Intel E8600
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core 2 Duo E8600 ASUS P5Q-E LGA 775 Motherboard EVGA NVIDIA GeForce GTX 460 (Fermi) Superclocked Kingston HyperX 2GB x 4 (8GB total) DDR2-800 
Hard DriveOptical DriveOSMonitor
Western Digital Caviar Green WD20EARS 2GB x 5 LG Blu-ray GGW-H20L XP Professional x64 Dell 2209WA 
PowerCase
Corsair 1050W Thermaltake Spedo 
  hide details  
Reply
post #150 of 278
Quote:
Originally Posted by p8p67user View Post

Beware RAID5 Configs with this recovery process

Hi All,

I too have been hit by this issue but I have a different theory about what might be going on.

Backstory:
Last night I upgraded the BIOS on my P8P67 motherboard to work around a compatibility issue.
After the BIOS updated the machine rebooted into windows successfully but my D: drive was not available.

My config is:
c_drive -> 1TB stand alone boot disk (Attached to intel controller, just not a raid member)
d_drive -> Raid5 array of 4 * 2TB with 64KB stripes

On rebooting into the BIOS I found that the RAID config had been cleared so I re-enabled raid and rebooted.
Again d_drive was not available.
Looking at the settings I found that all of my 4 2TB disks were being reported as "non-member-disks"
That started me on the google search that lead here.

The Theory
I've read all the posts here today and was almost ready to try the advice below when I started to think about the mechanism by which this works.

Clearly the creation of a new raid array is broken into 2 steps in Intel RST:

1) BIOS configuration of the RAID array
-- It seems likely from the discussion here that this does nothing but write some metadata to the start of each disk

2) Intel RST driver under windows - initialises the new array
-- This seems to be the key warning from Zero4549 in the message below. (i.e. avoid the intel rst driver under windows)

As suggested, to avoid the risk of the Intel driver starting to write to my disks before partition recovery, I installed a clean copy of windows 7 on a spare disk.
However there is a catch 22. In order for the Win7 install to work when the BIOS is configured for "RAID" mode, you must install the OS in Raid mode.
But by doing this the Intel driver is automatically installed by windows, as it needs this to even see the raid disk.
As such, even my clean OS install has the Intel RST driver as it is auto-detected. Of course it doesn't have the Intel RST GUI app installed, but from what I have read, this is primarily a front end to show you what the underlying driver is doing. i.e. The driver will start its work in any case, the GUI is just there to allow you to see what is happening and to manage events such as raid config changes, degradation etc.
I can't point to any direct evidence that this is the case, but it does seem strongly plausible. (at least to me)
On my clean Install the driver I see in driver manager is:
c:\windows\system32\drivers\iaStorV.sys (V 8.6.2.1012)
"Intel(R) ICH8R/ICH9R/ICH10R/DO SATA RAID Controller"


It does beg the obvious question, if that is the case, then how is anyone on this forum having a successful result.
The prevailing theory up to now was that if your raid was on boot drive, you were probably OK, and if it wasn't (as in my case) you had to make sure to uninstall the RST drivers before going back into windows. (Note: Windows only lets you uninstall the Intel GUI, it specifically warns that the driver itself won't be uninstalled)

However, I have a different theory. What if the difference here is more to do with the chosen RAID config.
Looking back at all the posts to date, I've noticed that the many success stories all appear to be from people with RAID 0/1/10 configs.
Also in the several cases where people have reported data loss, Raid5 is a common config. I haven't been able to find a story where a RAID5 users has had a positive outcome (short of using 3rd party data recovery tools).

I'm guessing that the Intel driver is in some way doing more damage when it sees a RAID5 config than a RAID 0/1/10.
I don't have a good explanation for that, but it could have to do with the need to calculate the parity stripe.

Bottom line is; I'm now very concerned that my RAID5 array will get corrupted as soon as I boot into windows.
Before I take that huge risk, I'd be very interested to hear from other members of this forum.
- Is my suggestion plausible?
- Can you point to evidence that contradicts it (e.g. A raid5 user for whom this worked flawlessly)

Note: I do have detailed notes and photos from when I installed the Raid Array originally, so I'm very confident that I can match the raid config exactly, if I do decide to take the chance on this.

I look forward to hearing from you.

This thread is an amazing resource and it is a real shame that this info isn't directly available on the Intel RST website.

Good observation.

It's been a while since I wrote that, and I can't really remember the specifics of what lead me to my hypothesis, but I do seem to remember a lot of RAID 5 recovery failures. I don't know if I just ignored that, or if I lumped those cases in with the "RAID is boot drive" scenario.

What I can say (and I don't remember if I've actually ever posted this before) is that I did attempt to recover a non-boot RAID without the uninstalling intel software step, and it failed similarly to other people's results, so the uninstall step does in fact have some effect, at least in RAID 1 and 10 (my tested configurations).

It would be great to get some more testing/feedback on RAID 5 configurations, so users in the future don't have to have the same uncertainty you are having, or worse, attempt a fix in full confidence and then have it fail.

If you haven't already tried your fix, good luck. If you have, what were your results?
Arcane
(33 items)
 
Sanctum
(9 items)
 
Fukurou
(15 items)
 
CPUMotherboardGraphicsGraphics
Core i7 980x GIGABYTE GA-EX58-UD5 MSI RX 480 GAMING X 4GB MSI GeForce GTX 680 Lightning 
RAMHard DriveHard DriveHard Drive
Kingston HyperX T1 Intel X25-M WD Caviar Black FASS Plextor M5S 
Hard DriveHard DriveOptical DriveOptical Drive
WD Velociraptor WD Caviar Black FALS Sony DVD Burner w/ Lightscribe LG Bluray + HDDVD 
CoolingCoolingCoolingOS
Black Ice GTX 360 Black Ice GTX 240 Panaflo High Speed - Push-Pull w/ shrouds Windows 7 Pro (64) 
OSMonitorMonitorKeyboard
Ubuntu (64) X-Star DP2710 ASUS VK266H Black 25.5" 2ms LCD X-Armor U9BL (Mech) 
PowerCaseMouseMouse Pad
EVGA 1000 P2 Cooler Master HAF 932 Razer Deathadder Chroma Cougar Control 
AudioAudioAudioAudio
ATH-A900X Maudio AV-40 Polk PSW-10 Zalman Mic-1 (Clip-on Mic) 
AudioOtherOtherOther
Sound Blaster X7 LE Logitech G13 Wacom Intuos 3 Scythe "3-Foot Switch" 
Other
Modded PS4, PS3, Xbox 360, and Logitech PC Cont... 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 MSI B350M Mortar Arctic RX Vega 64 G.Skill TridentZ  
Hard DriveHard DriveOSPower
Samsung EVO 960 Consatellation Windows 10 Pro Corsair HX 1050 
Case
Raijintek Aeneas White Window 
CPUMotherboardRAMHard Drive
Core i5-661 GA-H55-USB3 12GB DDR3 1333 WD Caviar Black AALS 640GB 
Hard DriveHard DriveOptical DriveCooling
WD Caviar Green EARS 2TB Vertex Turbo 60GB (SSD) Samsung Blu-ray, Samsung DVD Burner H50 (With push/pull nocturas) 
OSMonitorKeyboardPower
Windows 10 Professional 64 LG 47inch LED LCD Saitek Eclipse Lite-touch Wireless Seasonic X750 Gold 
CaseAudio
CM690 II Passive bookshelfspeakers + amp. 
  hide details  
Reply
Arcane
(33 items)
 
Sanctum
(9 items)
 
Fukurou
(15 items)
 
CPUMotherboardGraphicsGraphics
Core i7 980x GIGABYTE GA-EX58-UD5 MSI RX 480 GAMING X 4GB MSI GeForce GTX 680 Lightning 
RAMHard DriveHard DriveHard Drive
Kingston HyperX T1 Intel X25-M WD Caviar Black FASS Plextor M5S 
Hard DriveHard DriveOptical DriveOptical Drive
WD Velociraptor WD Caviar Black FALS Sony DVD Burner w/ Lightscribe LG Bluray + HDDVD 
CoolingCoolingCoolingOS
Black Ice GTX 360 Black Ice GTX 240 Panaflo High Speed - Push-Pull w/ shrouds Windows 7 Pro (64) 
OSMonitorMonitorKeyboard
Ubuntu (64) X-Star DP2710 ASUS VK266H Black 25.5" 2ms LCD X-Armor U9BL (Mech) 
PowerCaseMouseMouse Pad
EVGA 1000 P2 Cooler Master HAF 932 Razer Deathadder Chroma Cougar Control 
AudioAudioAudioAudio
ATH-A900X Maudio AV-40 Polk PSW-10 Zalman Mic-1 (Clip-on Mic) 
AudioOtherOtherOther
Sound Blaster X7 LE Logitech G13 Wacom Intuos 3 Scythe "3-Foot Switch" 
Other
Modded PS4, PS3, Xbox 360, and Logitech PC Cont... 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 MSI B350M Mortar Arctic RX Vega 64 G.Skill TridentZ  
Hard DriveHard DriveOSPower
Samsung EVO 960 Consatellation Windows 10 Pro Corsair HX 1050 
Case
Raijintek Aeneas White Window 
CPUMotherboardRAMHard Drive
Core i5-661 GA-H55-USB3 12GB DDR3 1333 WD Caviar Black AALS 640GB 
Hard DriveHard DriveOptical DriveCooling
WD Caviar Green EARS 2TB Vertex Turbo 60GB (SSD) Samsung Blu-ray, Samsung DVD Burner H50 (With push/pull nocturas) 
OSMonitorKeyboardPower
Windows 10 Professional 64 LG 47inch LED LCD Saitek Eclipse Lite-touch Wireless Seasonic X750 Gold 
CaseAudio
CM690 II Passive bookshelfspeakers + amp. 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: RAID Controllers and Software
Overclock.net › Forums › Components › Hard Drives & Storage › RAID Controllers and Software › HowTo : Recover Intel RAID "Non-Member Disk" Error..