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 23

post #221 of 278
Quote:
Originally Posted by wackget View Post

Because I physically re-wired the order of the drives, will this affect my ability to recover the RAID metadata?
Also when using TestDisk should I be searching for the Intel partition type?

Yes, it must be in the exact same order, no search for the one it recommends. Mine was the same as the one in your screenshot and it found it because my HDDs were in the same order.
post #222 of 278
Hi guys,

TLDR: no, you cannot force drives back onto the Intel array as raid info is saved to the on-board Intel raid device, so backup images using Runtime's Raid reconstructor trial, virtually mount them with OSFMount, Recover data with Runtime's paid version or other raid recovery software. *I had good results opening the images with ReclaiMe File Recovery*

what I am doing (and what you should be doing, as it's what data recovery expert companies all are telling me) is start by making full-disk backup images of your hdd's before attempting to recovery anything.
This way if anything messes up, you still have the option of sending your disks off to paid recovery services as you are not modifying any data on the disks.

The only problem you might have is having enough disk space somewhere to place the images, as each file will be the size of the total disk, not just the size of used space. (if you have a 2tb disk, the image file will be 2tb). I'm fortunate enough to have tons of disks storage, as I'm using a 4-bay Drobo USB raid and HP microserver with raid5, but recovering yourself at home like-the-pro's without any risk to data loss isn't cheap if you don't have the tools like this.

1.)
I would suggest connecting each drive externally, one by one (via a usb hdd caddy, or a simple sata to usb connector, Startech makes a good one) and create images (img files) using runtime's Raid Reconstructor (https://www.runtime.org/raid.htm) it's free to make images from which you can then mount as physical disks using OSFMount (freeware, http://www.osforensics.com/tools/mount-disk-images.html).

2.)
After making images of ALL disks in your failed raid you can mount them virtually using OSFMount then attempt to recover the raid volume using various software options, such as the paid version of runtime's raid reconstructor ($99) or Reclaime. (Reclaime is similar, and claims to offer the same thing but can MODIFIES YOUR DISKS DATA without warning, so use images not real hard-disks, and there is little to no actual info or guides about how to use Reclaime, unlike Runtime who reply to e-mail queries usually within 24 hours and have many video guides on youtube).

NOTE: as you are recovering the raid volume to a new virtual (or psychical) disk, ensure you have enough free space somewhere to put the recovered volume, you could (in theory) after making all the disk images backed up delete and re-create your old raid to save the new/recovered volume to, if you don't plan to send your disks off to specialists if it doesn't work.
You can just access the disks live without making images first, using Runtime's software and then export the analysed data to a new disk or image file, if you doin't have enough space to store the images but I'm being super careful.

If you are going to send your disks to recovery specialists, they are going to do this same process anyway as working off the live disks is extremely dangerous.

MY RESULTS:
I won't know my results for at leasts another week, as backing up 6tb of data (3x disks) onto my Nas even at 1gbit each disk takes a very long time to copy, but I hope to analyze the virtually mounted backed up images using Runtime's software and recover the volume to a new image which I will then mount and HOPEFULLY finally access all my data smile.gif

@ AVJunkie: if you only have one of your 3 raid disks working as member disk, your volume won't be accessible. I suggest you try as I have described above, making backup images of all drives, mounting them virtually then using recovery software to repair the volume somewhere.

CLOSING NOTE:
To avoid this in future as we are learning Intel is useless, I would suggest using a proper raid card (pci-e) as they have on-board cache options, or an external device like a Nas. If speed is your thing, look at Drobo who offer USB 3.0 raid devices. (1gbit ethernet vs 5gbit USB3.0)

EDIT: if you want to write the backup image (.img) onto a HDD, "HDD Raw Copy Tool" can do it (it can also make raw image files, or compressed format also)
http://hddguru.com/software/HDD-Raw-Copy-Tool/
Edited by Virtuallymore - 5/25/15 at 8:54am
post #223 of 278
Quote:
Originally Posted by Virtuallymore View Post


MY RESULTS:
I won't know my results for at leasts another week, as backing up 6tb of data (3x disks) onto my Nas even at 1gbit each disk takes a very long time to copy, but I hope to analyze the virtually mounted backed up images using Runtime's software and recover the volume to a new image which I will then mount and HOPEFULLY finally access all my data smile.gif
/

How did your results turn out? Any luck??
post #224 of 278
ReclaiMe raid recovery has found all my files on the unencrypted partition which I can view and recover individually with the paid version of Reclaime File recovery, but I want the whole volume restored including the 2x encrypted partitions which it did also find. So I need to write this to a new local raid array which will take quite some time.

If you are out of options I would highly recommend making raw (or compressed) backup disk img files of your drives and open them in ReclaiMe raid recovery to see if it can find your old volume for repair.
It's free to recover the whole volume directly to another disk/array or image file, but if you want individual file recovery you need to buy their Reclaime File Recovery software (you can view files with the free version but not recover them until buy a license, which is fair).

For me personally though, as my volume is so large (6tb) and the recovered volume does contain the parity drive also, I need an array of 8tb in size which I have now built as raid1 on an old dell pc with a proper pci raid card (Lindy brand) but keeps crashing about 5% when writing to the volume but this is 32bit windows machine so maybe that's part of the problem.
I will see if I can do this somehow with 64bit windows or just write an 8tb image file onto my nas, then use HDD raw copy tool to write this image file to a new local raid volume instead.
post #225 of 278
I got exactly the same issue with Raid 5 after bios update(I should back up my files first). but never thought of bios update could cause dead of my raid.

my Raid 5 contains 3 3tb disk, and I don't have intel software installed. try change different order of disk in raid, found two disk orders may be right, one could show folders with bootimage etc, not sure I have that on my disk, another order just show "." or "..", seems it's root directory, the create time is just right before bios update, not sure which one sounds right.

and I also do deep search, but it's damn slow, takes forever, do I need to finish it before continue?

Thanks!
post #226 of 278
Got issue solved, Raid 5 just work as charm as other Raid format. copy all the files from search and save partition, it just works as expected!
post #227 of 278
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.

Feeling VERY relieved!!!

I also have just registered an account to say THANK YOU.

MOB: ASUS Z97-DELUXE USB3.1
4x 4TB WD RAID 5 array

PC wouldn't start for some reason today ... after several attempts at trying to get past the post, resetting the bios was the only thing that would allow the PC to boot up.

This then led to the RAID array failing! FREAKOUT

The raid was telling me that 2 drives were now not members of the raid.

I followed these instructions and was able to recover all my documents as quick as it took to restart the computer!

AWESOME AWESOME AWESOME ... i am so glad i found this thread and TESTDISK
post #228 of 278
I have been browsing on the webz, and you guys have the most helpful info. Toms didnt turn up much...so decided to make an account on here.

My specs:

Windows Server 2008 R2

AsRock H87M Pro4 (Intel RST hardware I suppose...)

Intel G3220

RAID 1 - working (2 x 1TB toshibas)

RAID 0 - working (2 x 500GB WD Greens0

RAID 0 - NOT WORKING! (2 x 2TB Toshibas)

I know RAID 0 shouldnt be used for reliable strorage...but I dont have tons of money being a military man with single source of income and a family of 4...throw that into a high cost of living area...just doesnt work out. I made do with what I have.


***Huge Edit, new developments...***

So, I followed procedures, and figured out something new. I forced the TestDisk into Intel mode, did quick scan, viola! It found my old folders/files! I even changed the name (to what i think it was before?)

I had the drives out of order, and looking in with RAID Reconstructor helped me ID the drives serials and order. Turns out, I had them backwards...fixed that. Label your drives!!

I did quick scan, it found my stuff...I wrote the file to the drives...reboot, sits....nothing. I seen the MEBX menu. I hit Ctrl+P, didnt do anyhting...maybe I did something wrong? So close, but so far away...

Is there anything special or different from ICHR and the RST chips for raid?
Edited by stephenn82 - 7/9/15 at 9:09pm
Cubic Beast
(13 items)
 
Dakine Server
(9 items)
 
 
CPUMotherboardGraphicsRAM
i7 6700k Asus Maximus VIII Hero 1080 FTW Hybrid Corsair Vengeance LED 16GB  
Hard DriveCoolingOSMonitor
Samsung 950 Pro 256GB Corsair H115i Windows 10 Acer G257Hu  
KeyboardPowerCaseMouse
Corsair K70 RGB Rapidfire Corsair AX860 Corsair Carbide Series Air 740 Corsair M65 Pro RGB 
Audio
stock Realtek AC1150 
CPUMotherboardGraphicsRAM
pentium g3220 MSI H81M‑P33  XFX HD 7870 Gigahertz edition G.skill DDR3 1333 
Hard DriveHard DriveOptical DriveCooling
patriot blaze Western Digital asus 24x dvd burner Intel 775 cooler 
OSMonitorKeyboardPower
windows 10 pro acer 19 cheapy antec earthwatts 430 
  hide details  
Reply
Cubic Beast
(13 items)
 
Dakine Server
(9 items)
 
 
CPUMotherboardGraphicsRAM
i7 6700k Asus Maximus VIII Hero 1080 FTW Hybrid Corsair Vengeance LED 16GB  
Hard DriveCoolingOSMonitor
Samsung 950 Pro 256GB Corsair H115i Windows 10 Acer G257Hu  
KeyboardPowerCaseMouse
Corsair K70 RGB Rapidfire Corsair AX860 Corsair Carbide Series Air 740 Corsair M65 Pro RGB 
Audio
stock Realtek AC1150 
CPUMotherboardGraphicsRAM
pentium g3220 MSI H81M‑P33  XFX HD 7870 Gigahertz edition G.skill DDR3 1333 
Hard DriveHard DriveOptical DriveCooling
patriot blaze Western Digital asus 24x dvd burner Intel 775 cooler 
OSMonitorKeyboardPower
windows 10 pro acer 19 cheapy antec earthwatts 430 
  hide details  
Reply
post #229 of 278
Quote:
Originally Posted by stephenn82 View Post

I have been browsing on the webz, and you guys have the most helpful info. Toms didnt turn up much...so decided to make an account on here.

My specs:

Windows Server 2008 R2

AsRock H87M Pro4 (Intel RST hardware I suppose...)

Intel G3220

RAID 1 - working (2 x 1TB toshibas)

RAID 0 - working (2 x 500GB WD Greens0

RAID 0 - NOT WORKING! (2 x 2TB Toshibas)

I know RAID 0 shouldnt be used for reliable strorage...but I dont have tons of money being a military man with single source of income and a family of 4...throw that into a high cost of living area...just doesnt work out. I made do with what I have.


***Huge Edit, new developments...***

So, I followed procedures, and figured out something new. I forced the TestDisk into Intel mode, did quick scan, viola! It found my old folders/files! I even changed the name (to what i think it was before?)

I had the drives out of order, and looking in with RAID Reconstructor helped me ID the drives serials and order. Turns out, I had them backwards...fixed that. Label your drives!!

I did quick scan, it found my stuff...I wrote the file to the drives...reboot, sits....nothing. I seen the MEBX menu. I hit Ctrl+P, didnt do anyhting...maybe I did something wrong? So close, but so far away...

Is there anything special or different from ICHR and the RST chips for raid?

well, I said screw it, moving all my data off the drives with TestDisk. Will redo the raid and write all the configs down. At least all my stuff is salvageable!
Cubic Beast
(13 items)
 
Dakine Server
(9 items)
 
 
CPUMotherboardGraphicsRAM
i7 6700k Asus Maximus VIII Hero 1080 FTW Hybrid Corsair Vengeance LED 16GB  
Hard DriveCoolingOSMonitor
Samsung 950 Pro 256GB Corsair H115i Windows 10 Acer G257Hu  
KeyboardPowerCaseMouse
Corsair K70 RGB Rapidfire Corsair AX860 Corsair Carbide Series Air 740 Corsair M65 Pro RGB 
Audio
stock Realtek AC1150 
CPUMotherboardGraphicsRAM
pentium g3220 MSI H81M‑P33  XFX HD 7870 Gigahertz edition G.skill DDR3 1333 
Hard DriveHard DriveOptical DriveCooling
patriot blaze Western Digital asus 24x dvd burner Intel 775 cooler 
OSMonitorKeyboardPower
windows 10 pro acer 19 cheapy antec earthwatts 430 
  hide details  
Reply
Cubic Beast
(13 items)
 
Dakine Server
(9 items)
 
 
CPUMotherboardGraphicsRAM
i7 6700k Asus Maximus VIII Hero 1080 FTW Hybrid Corsair Vengeance LED 16GB  
Hard DriveCoolingOSMonitor
Samsung 950 Pro 256GB Corsair H115i Windows 10 Acer G257Hu  
KeyboardPowerCaseMouse
Corsair K70 RGB Rapidfire Corsair AX860 Corsair Carbide Series Air 740 Corsair M65 Pro RGB 
Audio
stock Realtek AC1150 
CPUMotherboardGraphicsRAM
pentium g3220 MSI H81M‑P33  XFX HD 7870 Gigahertz edition G.skill DDR3 1333 
Hard DriveHard DriveOptical DriveCooling
patriot blaze Western Digital asus 24x dvd burner Intel 775 cooler 
OSMonitorKeyboardPower
windows 10 pro acer 19 cheapy antec earthwatts 430 
  hide details  
Reply
post #230 of 278
This thread is a fantastic resource. Sorry to bump, but I'm stuck at the very end of the recovery process.

(TL;DR -- Went thru process, Windows won't recognize array. I think a corrupt MBR is why, cuz the files are still there. Should I use TestDisk to repair the boot sector or MBR? I'm afraid to write anything to the array.)

I've followed the procedure, rebuilt the array, used TestDisk to reinstate the partition table. But on reboot, though BIOS lists the RAID (10, btw) as healthy, Windows 7 Professional doesn't recognize it. It does appear in disk management as one drive of correct size, but it's only partially allocated, and it's not browseable.

I know data is still there because I've used TestDisk to recover some files. I think the MBR is corrupt, which must be common enough for it to be mentioned in this thread, though it seems most people here didn't need to repair their MBR. Also, this is a storage RAID, I don't boot an OS from it. So I don't think a Windows 7 recovery disk will do anything, since I'm not booting Windows from the RAID.

I'm getting confused about Intel/PC vs. EFI GPT partition type in TestDisk. I really have no idea what mine is. I was using Intel Rapid Storage to manage the RAID, but it looks like some Intel RAID arrays are GPT. In any case, whether I select either partition type in TestDisk, I can see my files listed.

I'm assuming corrupt boot sector or MBR is the problem, but when I check in TestDisk as GPT, it says boot is fine. When I check as Intel, it says boot is bad. This leads me to believe the drive isn't GPT, but regular Intel/MBR, and the MBR is corrupt. However, I'm afraid to use TestDisk to repair the MBR or boot sectors (two separate options in TestDisk -- don't know which, if either, to use). I don't want to write anything to the drive and corrupt files and ruin the array.
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..