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 21

post #201 of 278
Thanks a ton for posting this! Can't tell you how many times I've ran into this issue!
HTPC
(9 items)
 
GF's Rig
(8 items)
 
Editing/Gaming
(14 items)
 
CPUMotherboardGraphicsRAM
fx 6300 gigabyte 78mlt usb 3 HD 6450 Corsair  
Hard DriveCoolingOSMonitor
SanDisk SSD cooler master seidon 120m Windows 7 55" Samsung 1080p 120hz 
Audio
Pioneer vsx-1123 
CPUMotherboardGraphicsRAM
4930k Sabertooth X79 r9 270x Team  
Hard DriveHard DriveCoolingCase
Samsung 850 Evo Samsung 850 Evo Corsair h100i Antec p280 
CPUMotherboardGraphicsRAM
i7 5960x Sabertooth X99 GTX 980ti HYBRID G. skill Ripjaw  
Hard DriveHard DriveHard DriveHard Drive
Samsung 950  Samsung 850 evo Samsung 850 EVO WD RED 4TB 
Hard DriveCoolingOSMonitor
Hitachi X61 Kraken Windows 10 Qnix 27" 1440p 96HZ 
CaseAudio
s340 NZXT Firewire SOLO 
  hide details  
Reply
HTPC
(9 items)
 
GF's Rig
(8 items)
 
Editing/Gaming
(14 items)
 
CPUMotherboardGraphicsRAM
fx 6300 gigabyte 78mlt usb 3 HD 6450 Corsair  
Hard DriveCoolingOSMonitor
SanDisk SSD cooler master seidon 120m Windows 7 55" Samsung 1080p 120hz 
Audio
Pioneer vsx-1123 
CPUMotherboardGraphicsRAM
4930k Sabertooth X79 r9 270x Team  
Hard DriveHard DriveCoolingCase
Samsung 850 Evo Samsung 850 Evo Corsair h100i Antec p280 
CPUMotherboardGraphicsRAM
i7 5960x Sabertooth X99 GTX 980ti HYBRID G. skill Ripjaw  
Hard DriveHard DriveHard DriveHard Drive
Samsung 950  Samsung 850 evo Samsung 850 EVO WD RED 4TB 
Hard DriveCoolingOSMonitor
Hitachi X61 Kraken Windows 10 Qnix 27" 1440p 96HZ 
CaseAudio
s340 NZXT Firewire SOLO 
  hide details  
Reply
post #202 of 278
Quote:
As I mentioned wayyy back on page 7 (in 2012), if your OS isn't on the array (and thus is still operating when you attempt this guide), Intel's software will attempt to reinitialize the new array immediately, erasing all files in the process. Instead, you should boot into the OS before attempting the fix, uninstall / disable the Intel software, and then apply the fix (allowing it to complete uninterrupted). Once you are done you can reinstall the software.

I know, and that is precisely what I did. In fact, I printed out your updated guide and still have it right in front of me.

There was no initialization going on, otherwise I'd probably not be able to recover the files even with ZAR.
Edited by CourmacherGeert - 1/28/15 at 6:19am
post #203 of 278
Quote:
Originally Posted by CourmacherGeert View Post

I know, and that is precisely what I did. In fact, I printed out your updated guide and still have it right in front of me.

There was no initialization going on, otherwise I'd probably not be able to recover the files even with ZAR.

Took at look at your earlier posts. I'm curious if it is a windows 8 auto recovery feature that is disrupting the process.

I've never had to run this on win 8.1 personally, and I don't recall anyone else doing so either.
Arcane
(33 items)
 
Sanctum
(9 items)
 
Fukurou
(15 items)
 
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)
 
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 #204 of 278
I have read the entire thread before starting the process as I wanted to be extra-careful.
Well, as far Windows 8.1, I don't know. It could be. But without backups, I still wouldn't rely on it, no matter what Windows version you are using. There has also been a suggestion that whether or not you uninstall the Intel Driver does not matter, because once you installed Windows istelf in RAID mode (as you should do), the driver is hidden somewhere. I don't know whats true, but appareantly there was no initialization going on, at least my data is still there.

I am, btw, not trying to convince anyone. In fact, I couldn't care less. Having said that, despite the vast majority of users reporting success, there are a number of users in this thread where it didn't work. One I have just quoted above and this is also the guide that worked for me. Unless you feel extra risky, my advice would therefore be to first recover your data via ZAR, and then, if you still feel like it, try out the solution posted here. But, of course, this is entirely up to you. Whether trying to find patterns (such as RAID 1 vs 5 vs 10, Intel drivers or OS) is useful given the still rather small sample I very much doubt, but if you are satisfied with, say, a 95% recovery guarantee, then by all means proceed. Just bear in mind, you could be part of the 5%.
post #205 of 278
Quote:
Originally Posted by CourmacherGeert View Post

I have read the entire thread before starting the process as I wanted to be extra-careful.
Well, as far Windows 8.1, I don't know. It could be. But without backups, I still wouldn't rely on it, no matter what Windows version you are using. There has also been a suggestion that whether or not you uninstall the Intel Driver does not matter, because once you installed Windows istelf in RAID mode (as you should do), the driver is hidden somewhere. I don't know whats true, but appareantly there was no initialization going on, at least my data is still there.

I am, btw, not trying to convince anyone. In fact, I couldn't care less. Having said that, despite the vast majority of users reporting success, there are a number of users in this thread where it didn't work. One I have just quoted above and this is also the guide that worked for me. Unless you feel extra risky, my advice would therefore be to first recover your data via ZAR, and then, if you still feel like it, try out the solution posted here. But, of course, this is entirely up to you. Whether trying to find patterns (such as RAID 1 vs 5 vs 10, Intel drivers or OS) is useful given the still rather small sample I very much doubt, but if you are satisfied with, say, a 95% recovery guarantee, then by all means proceed. Just bear in mind, you could be part of the 5%.

For what it is worth, I've used ZAR and several other recovery softwares in the past for these scenarios. They ranged from completely bricking my hard drives to slowly recovering small fragments of my information. I've never had one actually fully restore my (RAID) drives aside from the method here, never mind doing it so quickly.

Of course, it is always important to have an actual backup. RAID, recovery software, etc should never be your only option. That is just asking for trouble - especially when your RAID failure is due to an actual drive failure, controller malfunction, or data corruption due to other factors (bad RAM for instance).

I'm personally a huge fan of this method, as it saved my data at a time that I was between backup drives (my array had grown larger than my backup drives, and I didn't have the money for an upgrade). Since then, I have learned to rely on it as a corrective measure for of the Intel ICH10R's shortcomings. Particularly common is updating the BIOS and losing your tables. In this scenario, all your data, and hardware, is still perfectly intact, and the teskdisk method can almost always restore the array to fully functional order in just a few seconds.

When it comes to actually damaged data or hardware, this method simply will not work. This is where some some other recovery software becomes more useful, but really, you should have an actual backup if you want to ensure a good chance of restoring your system and all of its data (especially without expensive and slow platter recovery).

As for drivers being hidden within windows and causing an automatic initialization regardless of uninstalling intel RST, etc... well I'm doubtful, to say the least, at least within Win 7. I've tested with and without uninstalling, and the pattern is pretty clear at least with my setup. There is also no real practical reason for this behavior to be embedded within windows itself. For anyone that is uncomfortable with this step however, you could always remove the boot drive and perform these fixes outside of your "raid mode" windows installation entirely (also im pretty sure windows doesn't actually differentiate between RAID and non RAID, but rather AHCI and IDE).

Not saying you shouldn't use ZAR, just trying to clarify things a bit.
Arcane
(33 items)
 
Sanctum
(9 items)
 
Fukurou
(15 items)
 
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)
 
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 #206 of 278
Well that's interesting to see that ZAR would have the potential to brick your drives. It certainly takes that much longer, but since no writing whatsoever should be involved, I'd have thought that you should be able to get to your data in a much safer way (assuming your drives are healthy as it puts some stress on them).
In my case, I did actually do some writing as I performed the commands according to the updated guide, but even so, ZAR found about 2TB of mainly large iso's in the lost folder category. It even went as far to find stuff I had deleted a while ago. Regarding the rest of my files, mainly pictures and flacs, everything was in the folder as it used to be.

I did come from the same scenario though, a BIOS update that messed with the FakeRAID and not failed hardware or anything; in that case I very much doubt that the ZAR Raid Recovery would work (other recovery tools may work, but this one particularly seems to reconstruct your RAID momentarily). For me the real lesson from this, however, has been to move away from Intel's FakeRaid. It's really just a terrible solution that you cannot rely on; I hate to image what would actually happen if your mainboard broke (2-3 years after buying it, it's probably impossible to get a replacement).
Edited by CourmacherGeert - 1/28/15 at 8:26am
post #207 of 278
Many thanks !

If not already stated, the trick works with a raid 5 too (5x4Tb).

I just recovered 7.98 Tb of data and am gonna found a religion with 3 gods : C. Grenier , adamsap (original post) and you Ictinike biggrin.gif
post #208 of 278
Hi all,

Glad I found this thread but of course most of us end up here due to the unfortunate circumstance of drives dropping of ICH arrays. In my case I have a 4x2TB RAID5 array and 2 drives dropped when my BIOS was changed to IDE mode vs. RAID and booted into Windows. After realizing the mistake and setting BIOS back to RAID, Intel RAID BIOS showed 2 drives were non-members and the array was in "failed" state.
The original array had 3 partitions, 120GB for user files/docs, 750GB for Apps, and rest about 3.6GB for random content
I've followed the instructions so far to remove the 2 remaining member disks from the array, then recreated the array with same parameters, RAID5 and stripe size of 128KB. Booted back into Windows and fired up TestDisk.

Results after Quick Scan EFI-GPT:
  1. It auto-detected EFI-GPT scheme but after scanning found 4 partitions for some reason, excluding the meta/reserve space.. partitions 1, 3, and 4 appear to be the correct size calculating by sector count, but only partition 4 shows any files, and only 2 at that... Partition 2, the strange one, has the same start as partition 1 but ends at the end of partition 3, TestDisk doesn't like it and if I label it as P I get a bad structure error
  2. During Quick Scan it also seems to find another partition with the size of 3.5TB, which is the correctly mapped to the above but reports the size is too big for array (array has 6000GB available) while this partition somehow would require the array to be 8000GB

I then decided to check with MBR
  1. Strangely the quick scan of MBR found the 3 partiions quickly, first 2 were correctly sized, but 3rd one was smaller. Same issue as above, only partiion 3 showed 2 files

I'm now letting GPT-EFI do the full deep scan but due to size of disks it'll probably be overnight, I'll report back in the morning
post #209 of 278
Thread Starter 
Hey everyone! I was shocked to see a notification from OCN the other day regarding this thread..

I am so elated that so many of you were able to recover your RAID setups using this method. It's been quite a while since I first posted that and I've since upgraded systems and out of the RAID business for now. Unfortunately I'm not likely to provide much support these days on this method [ie: questions, further impact, etc] but I just wanted to stop in and again state how happy I am that this has been so beneficial to so many! smile.gif

Due to life constraints and a family that is getting older [my oldest is now driving eek.gif] I don't have the time like I used to but I'm hoping someday to pick back up from my years @ OCN and once again provide meaningful dialog, ideas and all around tech talk.

Thank you OCN for allowing me to be a part of this great community!

Cheers,
~Ictinike
Refreshed Duo
(13 items)
 
  
CPUMotherboardGraphicsRAM
E8500 E0@4.25Ghz (500x8.5) Gigabyte GA-EP45-UD3P EVGA GTX285 (720/1674/2772) 2x2gb G.SKILL PC8500 
Hard DriveOptical DriveOSMonitor
3xWD 250GB RAID0 Sony DVD/CDR/RW Windows 7 Ultimate x64 ACER 24" P241WAID LCD 
KeyboardPowerCaseMouse
Logitech G15 (Original) OCZ GameXStream 700w SLI ThermalTake Armor Black Logitech G5 
Mouse Pad
Razor XACT 
  hide details  
Reply
Refreshed Duo
(13 items)
 
  
CPUMotherboardGraphicsRAM
E8500 E0@4.25Ghz (500x8.5) Gigabyte GA-EP45-UD3P EVGA GTX285 (720/1674/2772) 2x2gb G.SKILL PC8500 
Hard DriveOptical DriveOSMonitor
3xWD 250GB RAID0 Sony DVD/CDR/RW Windows 7 Ultimate x64 ACER 24" P241WAID LCD 
KeyboardPowerCaseMouse
Logitech G15 (Original) OCZ GameXStream 700w SLI ThermalTake Armor Black Logitech G5 
Mouse Pad
Razor XACT 
  hide details  
Reply
post #210 of 278
Thank you so much for this article,

I have an ASUS Sabertooth Z77 with 6x2GB setup in a RAID 5.

I updated the bios not knowing that it would give me the non-member disk error.

in my case i had to try a few times to get this to work as i didn't write down the stripe size =(
I tried with the wrong values and the name was different (this part is case sensitive or was in my situation).

please note that i uninstalled the rapid storage application first


i tried 3 different variations of the stripe size and name, each time i repeated the steps in the instructions. (each time getting more and more worried)

1. reset all to non member
2. create array
3. boot into windows and run the test disk
*note that each time i did this it created a new partition, so things were getting confusing and the list kept getting bigger.

on the third try i got the stripe size and name how they were previously and the testdisk gave me a list of my files!!! i wrote it and restarted....

however for me this process left my disks in an "initialize" state, so i re-installed the rapid storage program, and it says initializing... while im still able to see my files i am backing up everthing to external drives


this tutorial saved 7gb of my data, thank you so so much!!!
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..