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 26

post #251 of 287
any know how to make the bios re-recognize my raid 0 SSDs?

I have tried reconnecting them, and in different orders, but nothing.
Please help
post #252 of 287
Guys,
As I'm a Linux user and there were not many posts regarding resolving this issue on a Linux system, I thought I'd post my tale of woe/success as it may be helpful to others.

After a BIOS update to my main video editing box, the Intel onboard RAID dropped two of the four RAID1+0 members that I had created. Apparently, Intel RAID gets upset when the BIOS gets updated. The simplified steps from the excellent description here is basically:
A. Turn all members into Non-Raid Members
B. Re-create the RAID in the exact same order that it was created
- Don't Delete the RAID set, as that has caused data loss for some people
C. Usually, the partition table gets blown away when you recreate the RAID. You then have to go find it again by running a program like TestDisk to find and rewrite any missing partitions
The Path I Took
TestDisk allows you to select from a number of choices, but here are the top two that applied to me:
1) Intel/PC partition
2) EFI GPT partition map

For my Linux system, I needed to select "1) Intel/PC partition", even though my four disks had GPT partition maps.

Prerequisite
Before I touched anything, I decided to pull off any data that I could using PhotoRec, a program that reads files block-by-block, written by the same guy who wrote TestDisk, Christophe Grenier. I wrote that data to my 3GB SATA local backup drive. This took about ten hours.
- I ran through this exercise, but of course, the files that PhotoRec outputs are labeled F000001.txt, F000002.sh, F000003.gz and so on. The names and directory structures are totally lost. The content of the data files, however, is kept and I was able to find the video editing scripts that I had spent 100s of hours developing. That was good, but it would be an enormous pain-in-the-A to dig through them and rename them all.

My Steps
Once that was done, I went back into TestDisk and selected "Intel/PC partition." I saw a Linux partition of the correct size, 2.7TB. TestDisk gives you the option of viewing the directory structure. When I did this I got a foreboding message:
Code:
“Can’t open filesystem. Filesystem seems damaged.”

Ugh. I pressed on and wrote the partition table to disk. Mounting the drive, I got a new error:
Code:
mount: wrong fs type, bad option, bad superblock on /dev/md126p1

Ugh. Doing some research, I found this article on fixing bad superblocks, which entails finding a good one from the many that are sprinkled throughout an ext4 filesystem:
http://ubuntuforums.org/showthread.php?t=1245536

I found backup superblocks using mke2fs:
Code:
sudo mke2fs -n /dev/md126p1

mke2fs showed me a number of superblocks available. I prayed they weren't corrupt. Using e2fsck, I chose one of the superblocks, 32768, from the output of mke2fs and ran e2fsck:
Code:
sudo e2fsck -f -b 32768 /dev/md126p1

When the program ran, it found a few errors. In case there were many errors, I CTRL-C'd out of e2fsck and restarted the program by adding the "-y" switch to let it run unattended and accept all fixes with a "yes." I let it run. After I came back to the terminal, I found the screen full of the text output of the program, with thousands of sector id codes scrolling by. I wasn't sure if this was bad or good..but I let it finish. Afterward, I mounted the drive.
Code:
sudo mount /dev/md126p1 /sodoFiles

The mount came back without error. Good. The moment of truth was when I ran an "ls" and saw my files and directories! However, I wasn't out of the woods yet. The proof would be if I was able to access them. I played some music files, opened a few videos, started up a VM..they all worked! YAHOO!! I didn't lose my stuff!! Even though I had pretty much everything backed up, I did not have some custom video editing scripts backed up and I've spent 100s of hours on those. Thank God I got them back!!

So..hooray for me!
smile.gif
Now onto finishing setting up the Windows SSD for DOOM, the reason why I got into the mess in the first place!!
post #253 of 287
[deleted]
Edited by nickeveli - 6/2/16 at 4:54am
post #254 of 287
[deleted]
Edited by nickeveli - 6/2/16 at 4:54am
post #255 of 287
I am about to lose it. I have a raid 10 4x3gb array which has all of my work and personal information. I do have a partial backup but it is only 4gb and has been backing up only part of my stuff, photos, and music mostly. I think it has not been backed up in 2 weeks so I have some photos that are not there but most of my work is also not backed up.

Anyways, I created this other post, other post because my computer would not post. CTRL, ALT Del got the system to finally work. I then got to my desktop and realized that it was asking me to format my disk. I shut down and noticed one of the drive cables had become disconnected. So I plugged it back in and restarted. Again it asked me about formatting my drive D. I restarted and got into the INTEL raid config to find that my array said all 4 of the disks are not a part of an array!!! I am so scared and need some assurance that the walkthrough in the beginning of this thread will do the trick. this has always been my worst fear since going with RAID about 10 years ago.
What I have done so far:
1.Got the system to boot
2. Installed Test Disk
- I did not reset disk to non-raid as recommended because the system did it on its own.
- I am very nervous about building a new array with the disks. The help did not mention if he rebuilt the array inside the windows based intel rapid storage technology application or in the intel raid bios system.
? Do I need to scan? Do I need to rebuild the array first or is there another option?
The reason I am nervous about rebuild the array is that I have no idea what the name of the old drive was. I always name my drives. I believe it was called New Safe Drive or something like that but I do not recall it exactly. I am sure I had a screen shot at one point but it is on the drive that is currently failed. The drives are in the correct order at least.

Okay, I have installed Test Disk. It found the raid array which is comprised of the 4 drives but it believes that they are non-partitioned. What do I do here? Do I change it to EFI or Intel?

I tried Intel. The next screen said that the partition did not have an endmark.

Here is what the computer sees. It is really confused because it sees a 3tb mirrored partition which I do not have and then the correct 6tb partition and then it again as offline.



5 Hours into the project:
I just stopped the scan after 5 hours. It had gotten about 31% and because I had not done the first step of creating a new array, I felt it was going to be futile.
I did go through the raid bios and build a new array. I hope I did not use a different stripe size when I built it originally.
Anyways, I have started Test Disk again and instead of seeing all of the individual disks like it did previous, it had just the 6tb drive that is currently a problem. Computer management does not see the raw drive anymore either. I am praying that this will resolve the issue.My new question is if I need to use INTEL or EFI? I read one post where someone said never use INTEL. If anyone is out there, please advise me.
Next Step
I went with the recommended EFI and it found this within seconds.

Because it found one partition which looks to be correct I am going to move forward.
FINAL UPDATE: SUCCESS!!
THANK GOD!

I checked the fild system and saw that all directories were there!!!

I then went back to the previous page. I then clicked enter to select the partition. I then asked it to write the data!
EVERYTHING IS BACK TO NORMAL. smile.gif
I also uninstalled INTEL's management software during the process to reduce the chance that it may write to the disk during the process. I am now finding the most current version.
I hope these images help someone else.

After restarting agin my ssytem did one of the most intense checkdisks I have ever seen. Hundreds or thousdand of orphans. It seems like everything is working properly now smile.gif

Quote:



Originally Posted by The Source Thread Above

Thanks to everyone who tried to help. I found a solution and I thought I'd share it. I was able to recover the broken array using following steps.


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).


7. Run Vista repair from installation CD to fix the MBR.


Quote:



Originally Posted by Ictinike


On this part, a gent and myself went through this for Win 7 as well I've done Vista and we had to run the 3 bootrec commands to get his viable. I can't remember if I did this on Vista but it might be wise to run all three to fix the MBR in Vista as listed above. To do so:


in Command Prompt from the Recover console enter:


bootrec /fixmbr (should success)

bootrec /fixboot (should success)

bootrec /rebuildbcd (detects the Windows installation and asks you to add it to the BCD, hit YES)






8. Last but not least, send a donation to Mr. Grenier, the author of TestDisk.

Edited by PlantPoweredPro - 6/9/16 at 4:35pm
post #256 of 287
Hey everyone!
Just another success story, thanks so much! smile.gif
After having my computer turned off for a couple of days (I usually leave it powered on all the time), my ICH9 controller showed only 2 of my 4 disk RAI5.
After the initial panic, I searched for a way to recover it all. I've came across this topic and it was a life saver smile.gif Almost 6 TB in data that I was able to recover smile.gif
A couple of notes regarding my particular situation:

- my RAID5 is separated from my boot volume, so I didn't have to mess around with boot stuff

- I actually recreated the RAID on BIOS twice. On the first time I recreated it, I used TestDisk, but ended up writing the wrong kind of partition (so my volume didn't show up in Windows). After pondering a bit, I decided to start from scratch, recreate the RAID again on BIOS and run TestDisk again, this time looking for GPT partitions. And there it was, the little rascal, showing up after like 10 seconds smile.gif

So just as a note for future readers, you can recreate the RAID multiple times in BIOS, as long as you use the same parameters as the original RAID. Also, even if you go through TestDisk and write a wrong set of partitions, you can start from scratch again without loosing any data. Keep in mind that the only operations I did while recovering were through the BIOS and TestDisk, I didn't do anything else in Disk Manager or Windows or whatnot, so I believe that as long as you don't mess around with the volume before having your correct partition recovered, you should be fine.
Again, thanks a million, guys!
post #257 of 287

Can someone help me please as im struggling big time.

 

Heres whats happened:

 

I have an old p67 system running 1x SSD (OS).  I halso have 2x 1TB HDDs which were setup in RAID 1 config with data on and also an old OS still present.  With all three drives in my PC refuses to boot the SSD OS and wont start.  I stupidly went into the bios under false information and clicked "reset hard drives to none raid setup" or similar in the RAID config.  Low and behold when I go into windows on the SSD it shows 2 hard drives but says they are completely empty of data.

 

How can I get this data back? Is it possible to have the drives somehow return to normal and just have one HDD with all the data on that was being mirrored before?

If so how do I do this?  I dont think windows 10 and RAID works properly on this system.

 

many thanks

Current rig
(11 items)
 
  
Reply
Current rig
(11 items)
 
  
Reply
post #258 of 287
THANK YOU, THANK YOU, THANK YOU.

Changed MOBO and 2 HDD showed up as non members in my 3 HDD Raid 5.

Followed instructions, and all data is back.

//Zorglub
post #259 of 287
+1 Success Story.
Recovered 3x 1TB RAID5, Win7 on an ASROCK mobo with onboard Intel RAID. Quick Search was enough.

For anyone discovering this thread in the future, my advice is to read the ENTIRE thread. You can skim posts that just contain questions, pleas for help, and success stories. Read all posts with detailed steps. LEARN FROM THE MISTAKES OF OTHERS.

For my problem, posts #1, #65, #92, and #134 were the most helpful. Thanks to a generous user, I know that Intel RST is a software suite that can be found in the Control Panel's "Programs and Features" - my computer did not have this installed, and thus I was able to skip that step.

A warm THANK YOU to everyone in the thread, and a donation to the brilliant Christophe Grenier for his free software! biggrin.gifbiggrin.gifbiggrin.gif
post #260 of 287
Quote:
Originally Posted by $ilent View Post

Can someone help me please as im struggling big time.

Heres whats happened:

I have an old p67 system running 1x SSD (OS).  I halso have 2x 1TB HDDs which were setup in RAID 1 config with data on and also an old OS still present.  With all three drives in my PC refuses to boot the SSD OS and wont start.  I stupidly went into the bios under false information and clicked "reset hard drives to none raid setup" or similar in the RAID config.  Low and behold when I go into windows on the SSD it shows 2 hard drives but says they are completely empty of data.

How can I get this data back? Is it possible to have the drives somehow return to normal and just have one HDD with all the data on that was being mirrored before?


If so how do I do this?  I dont think windows 10 and RAID works properly on this system.

many thanks

Anyone please?
Current rig
(11 items)
 
  
Reply
Current rig
(11 items)
 
  
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..