HowTo : Recover Intel RAID "Non-Member Disk" Error..
41 - 60 of 305 Posts
Does anyone know if I should go into Windows Disk Management and initialize the disk before doing this? Just went into it and it asked me to do this, didnt accept because I don't wanna destroy the disk.
BTW, found my partition, haven't tried restoring it yet, I have some hope though
![smile.gif]()
BTW, found my partition, haven't tried restoring it yet, I have some hope though
Joined
·
1,828 Posts
Quote:
At 59 I get confused easily. LOL!
Sorry, I contribute to several computer forums and noticed a post about a guy that had 8 drives in RAID0 when you have 8TB in RAID0.
At 59 I get confused easily. LOL!
Joined
·
392 Posts
Quote:
I am having this issue and accidentally did this on one of my RAID0 drives (the non-member one that showed up separately in windows). TestDisk so far hasn't found a partition on Quick Search but it has only completely 5%. I'm hoping there's still a way for TestDisk to recover my partition.
EDIT: Ok so far it has gotten to 51% on deeper search and still hasn't found any partitions...is this basically a lost cause? It's been running over an hour...
EDIT 2: OK SO THIS COMPLETELY WORKED! What's important to note is that you have to be in Windows when trying this method. I was trying to do it from an Ultimate Boot CD setup and it kept seeing the drives separately instead of as one singular RAID volume. Once I tried it in Win7, where my motherboard's RAID controller drivers are installed, TestDisk saw the partition immediately. After that I just had it write the partition to the drive and restarted Windows. Everything was back to normal!
Originally Posted by Kramy  Initializing the drive/array wipes out the partition table. TestDisk should have more to work with if you don't do that. |
EDIT: Ok so far it has gotten to 51% on deeper search and still hasn't found any partitions...is this basically a lost cause? It's been running over an hour...
EDIT 2: OK SO THIS COMPLETELY WORKED! What's important to note is that you have to be in Windows when trying this method. I was trying to do it from an Ultimate Boot CD setup and it kept seeing the drives separately instead of as one singular RAID volume. Once I tried it in Win7, where my motherboard's RAID controller drivers are installed, TestDisk saw the partition immediately. After that I just had it write the partition to the drive and restarted Windows. Everything was back to normal!
Joined
·
392 Posts
Ok guys I just had this problem again and the fix worked but I am wondering if anyone knows what exactly causes this problem? This has now happened a total of five times. Is the Intel RAID controller on these motherboards really this bad, or is there something else that causes this error? My rig is overclocked but has passed >24 hours of prime95. I know that doesn't mean it's for sure 100% stable but I am wondering if there is something else at play here besides the overclock that could be causing my RAID0 to constantly fail. Both HDDs pass diagnostic tests.
Joined
·
406 Posts
Well I have gone thru the steps but testdisk cannot find my partition in windows 7 using the Intel/PC criteria. I have tried quick search and deeper search is currently at 10% finding nothing.
I have a 4 disk raid 5 array which I reset in the intel bios then created a new volume identical to old.
I booted into windows (which is on my ssd) with intel rapid storage techology software uninstalled. That is to say, I didn't want it to automatically start initializing the array.
I also tried using testdisk to find the array using GPT which it did! However, when using the "P" option I see none of my files listed, its just blank.
The real question now is... do I have to initialize this array before it sees the partition? I'm in the original windows so all drivers should be installed to see the data. Any help would be immensily appreciated!
I have a 4 disk raid 5 array which I reset in the intel bios then created a new volume identical to old.
I booted into windows (which is on my ssd) with intel rapid storage techology software uninstalled. That is to say, I didn't want it to automatically start initializing the array.
I also tried using testdisk to find the array using GPT which it did! However, when using the "P" option I see none of my files listed, its just blank.
The real question now is... do I have to initialize this array before it sees the partition? I'm in the original windows so all drivers should be installed to see the data. Any help would be immensily appreciated!
Joined
·
406 Posts
Quote:
I am able to find my partition but it shows NO files when I use the P command. This concerns me greatly as the directions suggest I should be able to browse my files.
Well, did RST auto initialize the array in windows when you first booted into it?. In addition, did you find your array using the PC/Intel method and able to browse your files?
I am able to find my partition but it shows NO files when I use the P command. This concerns me greatly as the directions suggest I should be able to browse my files.
Joined
·
392 Posts
Quote:
As far as finding or being able to browse files, I never tried that. All I would do is analyze, search for a partition table and then tell TestDisk to write that partition table to the drive as soon as it found it. It would find it immediately (less than 5 seconds max) when it was searching and after I would tell it to write the partition table to the drive it would just ask me to reboot the machine. After rebooting the array would show up normally again.
I don't know if RST would auto-initialize my array. I want to say it didn't but I'm not sure. I definitely never saw any pop-up from my RST icon in my system tray.
As far as finding or being able to browse files, I never tried that. All I would do is analyze, search for a partition table and then tell TestDisk to write that partition table to the drive as soon as it found it. It would find it immediately (less than 5 seconds max) when it was searching and after I would tell it to write the partition table to the drive it would just ask me to reboot the machine. After rebooting the array would show up normally again.
Joined
·
406 Posts
Quote:
I have RST manager installed and it shows the array as "normal". In windows Disk Management it shows an uninitialized unknown disk 1 of size 5589.04GB which is clearly the array. RST did not initialize any array which it usually does. I'm not sure if this is good news or not.
Using testdisk it finds no usable partitions. I get "write errors" when I try to do NTFS. I wonder, do I have to do a windows initialize prior to using testdisk? Or will initializing the disk DEFINITELY delete all my data (assuming its not all completely lost already)?
Well just bit the bullet and tried some things.. no luck yet but this is where I'm at now:
I have RST manager installed and it shows the array as "normal". In windows Disk Management it shows an uninitialized unknown disk 1 of size 5589.04GB which is clearly the array. RST did not initialize any array which it usually does. I'm not sure if this is good news or not.
Using testdisk it finds no usable partitions. I get "write errors" when I try to do NTFS. I wonder, do I have to do a windows initialize prior to using testdisk? Or will initializing the disk DEFINITELY delete all my data (assuming its not all completely lost already)?
Joined
·
1 Posts
Excellent process, thank you, worked like a charm. Foolish me went and tried to dust off some major dust build up while the computer was on. Knocked a cable I guess, which in turn marked two discs out of a three disc RAID 5 array as Offline Members.
Beyond this, though, Vista still wouldn't boot for me. It would hang at the first black screen with the green "Progress bar" type thing. No error message, no disc activity, just Progress bar forever.
Turns out it was a corrupt registry. I followed this process using an emergency repair console and got booted up straight away after that:
Taken from http://forums.techarena.in/windows-vista-performance/1145863.htm :
"
Hello,
There are backup copies of the registry in the
\windows\system32\config\regback folder
You can try replacing the ones in the config folder with the ones from the
regback folder.
Rename the ones in the \windows\system32\config folder first
Change directory so you are in the \windows\system32\config folder
ren system system.bak
ren software software.bak
ren sam sam.bak
ren security security.bak
Then
copy c:\windows\system32\config\regback\system
copy c:\windows\system32\config\regback\software
copy c:\windows\system32\config\regback\sam
copy c:\windows\system32\config\regback\security
All four registry hives should be replaced at the same time even though you
are only having issues with one of the hives, they are a unit, they are not
intended to be replaced individually, there may be issues later if one of
the hives is rolled back and not the others."
Again, the process with redefining the array and using the testdisc tool saved my bacon so much, I thought I should post so that perhaps someone could benefit from this extension from my experience.
Good luck to all, and thank you!
Beyond this, though, Vista still wouldn't boot for me. It would hang at the first black screen with the green "Progress bar" type thing. No error message, no disc activity, just Progress bar forever.
Turns out it was a corrupt registry. I followed this process using an emergency repair console and got booted up straight away after that:
Taken from http://forums.techarena.in/windows-vista-performance/1145863.htm :
"
Hello,
There are backup copies of the registry in the
\windows\system32\config\regback folder
You can try replacing the ones in the config folder with the ones from the
regback folder.
Rename the ones in the \windows\system32\config folder first
Change directory so you are in the \windows\system32\config folder
ren system system.bak
ren software software.bak
ren sam sam.bak
ren security security.bak
Then
copy c:\windows\system32\config\regback\system
copy c:\windows\system32\config\regback\software
copy c:\windows\system32\config\regback\sam
copy c:\windows\system32\config\regback\security
All four registry hives should be replaced at the same time even though you
are only having issues with one of the hives, they are a unit, they are not
intended to be replaced individually, there may be issues later if one of
the hives is rolled back and not the others."
Again, the process with redefining the array and using the testdisc tool saved my bacon so much, I thought I should post so that perhaps someone could benefit from this extension from my experience.
Good luck to all, and thank you!
Hey guys, I found your site on the web and I'm hoping that this will be my saviour. I have a ASUS Z68 motherboard that I just installed with my old raid set as a drive 2. I think what happened is that I installed the OS with the RAID disks turned on and MS smacked the fist drive with a new partition and killed my RAID 0. one of the 4 drives shows up as a non-member disk. I followed the instructions above and to my surprise, testdisk actually found the missing partition. I went through the process to write the partition and reboot, but after the reboot, my system would hang at the BIOS screen. I first thought that it was trying to boot from the partition and having an issue, but in the end I couldn't even get into the BIOS screen at all. As long as I have those 4 drives installed with the recovered partition, the system will not POST to the EFI BIOS screen and will not boot. It just hangs at the last screen in the boot process. My guess is that the EFI is interogating the partition and is not happy with it somehow....but I can't figure this out.. and help would be greatly appreciated.
thanks.
thanks.
@Cr0nJ0b
I doens't POST because you configured the drives as either primary or bootable. At least, that was the problem i had with TestDisk and my RAID 5 array... Still don't have my data back by the way, but did discover the POST-errors.
I just made all the drives non-raid again and started again. You can go to the Intel screen with CTRL-I before EFI does more, so you can just revert back to that state.
I doens't POST because you configured the drives as either primary or bootable. At least, that was the problem i had with TestDisk and my RAID 5 array... Still don't have my data back by the way, but did discover the POST-errors.
I just made all the drives non-raid again and started again. You can go to the Intel screen with CTRL-I before EFI does more, so you can just revert back to that state.
Intel raid is temperamental and if you don't want lost data keep backups, I had a 2 drive raid 0 mark one disk as bad and lost a month worth of data, game over man. I tried test disk but it was my os raid that broke..
I will never again trust intel raid with my data
sent from my sprint HTC supersonic using tapatalk
I will never again trust intel raid with my data
sent from my sprint HTC supersonic using tapatalk
Hello everyone. I'm new here and am having very similar issue. 2 of 4 of my Raid 5 array disk show as non-member. Not sure what to do as after I read this thread some of you have had success with it some not. Let me paint you a picture of my situation and maybe you would be so kind to help me.
My Config:
i5 760 1156 Socet
8gb RAM
Asus Maximus III Gene P55 chipset
Win 7 Ultimate 64bit
I have an OS installed on Raid 1 array. All the drivers and apps installed including Inter Rapid Storage utility and driver. My storage is on a separate Raid 5 array where 2 out of 4 drives are marked as "non-member" drives. The instructions provide in this thread say that to resolve it:
1. I'll need to break the raid 5 array first
2. recreate it
3. boot into windows and run testdisk
My question is, will I loose my data after recreation of the raid 5 array ? Since I recreated it when I boot into windows my Intel Rapid Storage will initialize the array automatically. Actually doesn't the initialization of the array start automatically after recreation when I'm still in the Raid Controllers Bios utility ?
Any help and advise would be appreciated.
My Config:
i5 760 1156 Socet
8gb RAM
Asus Maximus III Gene P55 chipset
Win 7 Ultimate 64bit
I have an OS installed on Raid 1 array. All the drivers and apps installed including Inter Rapid Storage utility and driver. My storage is on a separate Raid 5 array where 2 out of 4 drives are marked as "non-member" drives. The instructions provide in this thread say that to resolve it:
1. I'll need to break the raid 5 array first
2. recreate it
3. boot into windows and run testdisk
My question is, will I loose my data after recreation of the raid 5 array ? Since I recreated it when I boot into windows my Intel Rapid Storage will initialize the array automatically. Actually doesn't the initialization of the array start automatically after recreation when I'm still in the Raid Controllers Bios utility ?
Any help and advise would be appreciated.
Joined
·
9,545 Posts
Quote:
I don't have an answer, but I'd like to mention that you may be able to run TestDisk from a linux boot CD if you're worried about what happens when Windows starts.
http://www.sysresccd.org/Download
But that won't do you any good if it starts immediately. (in the RAID BIOS)
Good questions.Originally Posted by mmiszkiel
My question is, will I loose my data after recreation of the raid 5 array ? Since I recreated it when I boot into windows my Intel Rapid Storage will initialize the array automatically. Actually doesn't the initialization of the array start automatically after recreation when I'm still in the Raid Controllers Bios utility ?
Any help and advise would be appreciated.
I don't have an answer, but I'd like to mention that you may be able to run TestDisk from a linux boot CD if you're worried about what happens when Windows starts.
http://www.sysresccd.org/Download
But that won't do you any good if it starts immediately. (in the RAID BIOS)
Hello, I was going to start a thread, but found this one similar to my problem. I have two 2-disk RAIDs in my system, 4 TB and 3 TB for video storage. ASUS P8P67 Pro B3 with i7-2600K processor and SSD system drive Windows 7. I recently updated to new BIOS 2303 from 2103, but it rebooted to default AHCI setting and the RAIDs failed. I set the BIOS to RAID setting, but problem still exists. Intel Rapid Storage mgr shows each array with one good drive and one missing, then lists the missing drives as separate 'good' drives. 
Windows Disk manager is displayed in the photo. The pre-boot Intel RST shows the two failed arrays, then below lists two 'member' disks and two 'non-RAID' disks. With no recovery options.
I tried several things, including disconnecting and reconnecting the drives. The TestDisk program analyzed the volumes, but was unable to find any partition to fix, even after deeper search. The RAIDS were set up with GPT file system originally, so in TestDisk I chose that option instead of Intel PC. It may have worked, but it went so slow it would have taken days. When I chose Intel PC type, it analyzed pretty quickly but found nothing.
I am probably out of options at this point, but thought I'd check here before re-initializing my drives. I have most everything backed, but would have liked to rescue some files.
I tried several things, including disconnecting and reconnecting the drives. The TestDisk program analyzed the volumes, but was unable to find any partition to fix, even after deeper search. The RAIDS were set up with GPT file system originally, so in TestDisk I chose that option instead of Intel PC. It may have worked, but it went so slow it would have taken days. When I chose Intel PC type, it analyzed pretty quickly but found nothing.
I am probably out of options at this point, but thought I'd check here before re-initializing my drives. I have most everything backed, but would have liked to rescue some files.
41 - 60 of 305 Posts
