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 12

post #111 of 278
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

Zero, thanks for these detailed instructions !

I'm facing pretty much the same problem, due to a Bios update I lost a 4 x 2TB Raid 10 that was drive D.

I'm on a Gigabyte GA-P55A-UD3 mobo, the Raid on the Marvell controller had no issues with the Bios update, the Intel controller lost the Raid...

Now regarding the "disk order", I'm assuming this refers to the order in which I SELECT the disks when I (re-)create the Raid in the IRST Configuration utility at bootup ?

So I would always select the same 4 disks that were used in the Raid, but the ORDER in which I make a selection (of the disks) with the space bar has to be identical to when I created the Raid ?

If that is the case, then I'm looking at 24 possible variations (with 4 disks involved)... I have already tried 12... no luck so far, TestDisk did find partitions but they did not contain the data that was on the Raid...

Thanks for any suggestions !

- Mike
post #112 of 278
Hi all,

Wonder if you could help me... (Please)

I have a vaio laptop with a 128gb raid0 setup.

I started it up the other day to find that the raid had failed mad.gif
(ID volume name: Volume0
Level: Raid0(strip)
Strip:128k
Size: 178.9gb FAILED
Bootable: no

The physical devices on port 2 &3 are:
Samsung mmcre28g 59.6gb Member disk(0)
Samsung mmcre64g 59.6gb Member disk(0)
The actual disk is a 128gb samsung SSD with the os & important data files on it.

its looking like it has lost its way as its showing 178.9gb rather than 128gb.

So, i have booted up into the intel raid setup and reset the disks to non member disks.
I then created a new array with 128gb size and it still cannot find the o/s.

Any help appreciated,

thanks
post #113 of 278
Quote:
Originally Posted by eitch View Post

Hi all,

Wonder if you could help me... (Please)

I have a vaio laptop with a 128gb raid0 setup.

I started it up the other day to find that the raid had failed mad.gif
(ID volume name: Volume0
Level: Raid0(strip)
Strip:128k
Size: 178.9gb FAILED
Bootable: no

The physical devices on port 2 &3 are:
Samsung mmcre28g 59.6gb Member disk(0)
Samsung mmcre64g 59.6gb Member disk(0)
The actual disk is a 128gb samsung SSD with the os & important data files on it.

its looking like it has lost its way as its showing 178.9gb rather than 128gb.

So, i have booted up into the intel raid setup and reset the disks to non member disks.
I then created a new array with 128gb size and it still cannot find the o/s.

Any help appreciated,

thanks

You should of received / seen a warning when converting to non member disks that it will/can destroy data and pressed Y and proceeded.

Essentially when you converted them to non-member disks, you erased any and all data stored on those two disks/ssd's while in raid mode.

There's nothing you can do with intel raid. Especially since you created a -NEW- array, which erased all data on the disks a -second- time.

I'm sorry to be the bearer of bad news but all your data is lost. I would hope you had backups, as anyone running any form of raid-0 should be making regular backups.
Edited by kithylin - 4/23/13 at 2:30pm
post #114 of 278
update on my scenario:

I tried all 24 variations of disk arrangement and still TestDisk could not find the correct partition... not sure why it didn't work, it seemed to work for Zero in the almost exact same scenario...

Here's what happened in details:

> updated Bios on Gigabyte GA-P55A-UD3 mobo - there was no warning of possible data loss, somebody should seriously sue these idiots

> had to reboot

> after being back in Win 7, I saw that my 4 x 2TB Raid 10 was gone

> rebooted into Bios and saw that Intel Sata Control mode was not enabled

--> so the Bios update did reset all of my Bios settings to default, incl. Raid conf., Memory setup etc.

> applying my settings I was now able to get back into the IRST controller at bootup

> all Raid configuration was gone

> I re-booted into Windows and the Raid 10 was still not there

> stumbled upon this thread, and starting applying Zero's instructions, uninstalled IRST sw on the OS level and rebooted to re-create the Raid 10 within the IRST bootup utility

> since I did not remember the disk order (Raid was originally configured in 2010), I went through all possible 24 cases of disk order, rebooted every time, set all Raid member disks to non-members and re-created the Raid with a different disk order - all other settings were exactly the same as in the original Raid...

> TestDisk in all cases found partitions, but when previewing with the P option, the file system was either damaged or it displayed an empty directory or a directory with single letter files (seemed corrupted)...

I am not sure if I correctly understood the workflow, so if you have any suggestion on things to try, please let me know !

Is there anything else (besides what I did already) I can try using TestDisk to recover my Raid configuration ?

Currently running GetDataBack to see what it finds and what can be recovered... any advice on superior data recovery sw packages would also be appreciated !

- Mike
post #115 of 278
for anybody else looking for help with their lost Raid 10, here's the final update on my situation:

I was able to recover one of the two Raid 0's in my Raid 10 with DiskInternal's Raid Recovery. Runtime's Raid Reconstructor was unable to find the Raid 0 on the same 2 disks, while DiskInternal's Raid Recovery recovered ALL FILES.

I copied them over to the other 2 disks from the original Raid 10.

Should have done that right away, rather than wasting so much time trying to figure out disk order and Raid configuration. The sw does it all for you. And I'm def moving away from the Intel Raid solution...

And I will never purchase a Gigabyte mobo again. The fact that Gigabyte's own sw updates the Bios w/o keeping the users' Bios settings or warning the user of possible data loss b/c the dumb ass morons are resetting the raid controller setup is un-freakin-real...

- M
post #116 of 278
This process worked for me recovering my RAID 0 C drive where one of the drives had dropped out of the array (because I re-wired the SATA drives incorrectly). I used the process with the addition of making it active and recovered all the files. What a relief... THANK YOU. I'm planning on donating to testdisk today.thumb.gif
post #117 of 278
Had a series of problems, learned a lot from this thread, and want to post what worked for me:

Windows 7, fast Boxx computer, a couple of years old. Two Intel two-disk RAID1 arrays, both large SSD's, one for the system, the other for data.

Had what appeared to be various scary disk problems. The Boxx people were very helpful. Updated BIOS. Problems remained. Boxx sent new system disk pair and had me update Intel RAID software. Started getting the bad disk in array messages. Removing and replacing the "failed" drive worked; the system would rebuild the array successfully. But then the problem would recur, maybe with a different disk, and sometimes with the other array, sometimes one disk in each array. Sometimes worked fine for a couple of weeks, then happened again. Boxx sent a replacement motherboard. I enjoyed replacing it, and it seemed to go fine, but the RAID problem came back. Yow!

Decided it must be OS or software problems. I checked at Intel site, which is very complex, and discovered that the updated RAID driver I had installed was no longer the most recent. Installing the latest Intel Rapid Storage Technology driver (in March, 2013, version 11.6.0.1030) has apparently solved the problem completely. It's been several months now, with no more RAID problems. I think the RAID errors were not drive issues, but Intel software problems. The SMART data for all the drives showed no errors at all.

Both times that I updated the RAID drivers the fancy user interface that appears in Windows changed completely, which kind of gives me the creeps. I guess Intel has somehow combined low level driver code with a Windows GUI program, which seems to be asking for trouble. Anyway, it's better now.
Edited by charlesstaylor - 5/11/13 at 12:12pm
post #118 of 278
Everyone seems to be having success except me. I've a RAID5 using an intel chip on an Asrock z68 Extreme 4 Gen3 mobo. with 4x2TB hdds. I toggled from RAID to AHCI in the bios while installing a new SSD and when I changed it back to RAID two of my four raid drives were showing as non-members.

I've done what's in this thread - deleted the array, recreated the array identically, but test disk takes 12+hrs to do a quick scan now.

I've tried using other programs suggested in this thread and both GetDataBack and Zero Assumption Recovery can see a lot of my files - so I know some sort of structure is there - but the majority show up as random gibberish or have lost a tonne of the folder structures or are damaged in some way.

As you can see "LostFiles" and "LostDirs" is huge.



Anyone have any thoughts? At present - after deleting and recreating my array - I haven't initialised it in Windows. Is it worth trying?
Edited by PSBtaboo - 5/17/13 at 5:28pm
post #119 of 278
More info:

Following Zero4549's instructions perfectly, I find nothing useful on a quick scan and after a few seconds with a deeper scan my array shows up. However when I get to browse files there is nothing there. If I set it to primary and write the new partition data, when I reboot a new disk shows up but it is inaccessible.


Edited by PSBtaboo - 5/17/13 at 6:11pm
post #120 of 278
Well, I'm glad this thread is still active. I have the following problem. I use 2 vertex4 in raid0 as my boot partition, my storage is composed of 2 1.5Tb Seagate HDs, well suddenly I got the "non-member" error. I want to follow the OP instructions, but I'm having a hard time to do the step

2. Create a new array with identical settings as the broken array.

That 2 HDDs had two arrays one with 2tb and one with 1tb, the one with 2tb had two partiitons data1 and data2 each one of 1tb in raid0 the array with 1tb was a 500gb in raid1. The problem is that I can't recall the right order, nor the parameters I used to create those arrays! In addition to that I had to refresh my windows 8 install at the Vertex4 array and that just reduce my chance of getting those parameters from somewere in the system folders/register all i have left is a "windows.old" folder. Anyone have some idea that might help me? I don't want to spend money on a program to restore that data and also on a new drive since what i have read those "de-stripping" programs require a full copy of the partition. I have tons of precious photos and videos in those partitions really need help thumb.gif.
Temp Derp
(21 items)
 
  
CPUMotherboardGraphicsRAM
2600K MSI Mpower Z77 7970 Reference G.Skill RipjawsZ 4x4GB 
Hard DriveHard DriveCoolingCooling
OCZ Vertex 4 Seagate Barracuda 7200.11 Apogee HD XSPC RX360 V2 
CoolingCoolingCoolingOS
EKFC-7970NA Swiftech D5 XSPC Dual Bay D5 Reservoir Windows 8.1 
MonitorMonitorKeyboardPower
Overlord Tempest X270OC (@114Hz) Dell U2412m Ducky DK-9008 Corsair TX950 V1 
CaseMouseMouse PadAudio
Cooler Master CM290 Logitech G600 - Razer Naga Epic Steelseries 9HD Asus Essence STX 
Audio
Denon AH-D2000 
  hide details  
Reply
Temp Derp
(21 items)
 
  
CPUMotherboardGraphicsRAM
2600K MSI Mpower Z77 7970 Reference G.Skill RipjawsZ 4x4GB 
Hard DriveHard DriveCoolingCooling
OCZ Vertex 4 Seagate Barracuda 7200.11 Apogee HD XSPC RX360 V2 
CoolingCoolingCoolingOS
EKFC-7970NA Swiftech D5 XSPC Dual Bay D5 Reservoir Windows 8.1 
MonitorMonitorKeyboardPower
Overlord Tempest X270OC (@114Hz) Dell U2412m Ducky DK-9008 Corsair TX950 V1 
CaseMouseMouse PadAudio
Cooler Master CM290 Logitech G600 - Razer Naga Epic Steelseries 9HD Asus Essence STX 
Audio
Denon AH-D2000 
  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..