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 27

post #261 of 278
Many thanks for this thread, Overclock.net delivers thumb.gifthumb.gifthumb.gif

Solved my RAID 0 failure after blue screen in that it allowed me to recover all my valuable files.

My problem:

I installed a new GPU and this brought up memory problems (it appears one stick of RAM has become faulty) which lead to a BSOD. After the BSOD, my PC was screwed as the RAID 0 setup was lost meaning I couldn't access all the files on both SSDs that were set to RAID 0 but could still boost as my OS was on a separate M.2 Drive.

Followed the OP step by step and used TestDisk and I have saved all my files. I'm currently using 'refresh' repair for my Windows 10 installation.

Thanks guys. smile.gif
post #262 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.

Mate, just make a account to say : THANK YOU !!!

you saved all my data (8tb) ... the hint for me was:

7. Mark the partition as Primary, write partition data to it

then i noticed: i had to use left or right cursor to set the partition to "P" wink.gif

Both raids are now live and working as before... i didnt know, what happens. last week i removed 16 gb RAM of my Sys from 32GB to use these in a other machine, after putting it back, my bios got reset and only want to start with a default setting set. i was not able to load any profile on my gigabyte board.

and now... i will buy a nas wink.gif

Also thanks to all others in this forum! many users witih the same Problem done a lot of work to help other.... thumbs up! thumb.gif
post #263 of 278
10/10 saved my files thanks!
+rep
post #264 of 278
Hey you are the boss, saving me lots of time and effort in restoring the lost. Thank you so much! thumb.gif
post #265 of 278
Hey!

just yesterday I was doing some BIOS work on my computer, and accidentally loaded a saved configuration from my BIOS that changed the SATA mode from RAID->AHCI.

I have a RAID10(0+1) composed of 4x3TB drives managed by the intel onboard controller, which promptly failed after the sata mode changed. two disks fell out of the raid, and are now in a non-member configuration. As I understand it, nothing has physically failed, just the software RAID has messed up the metadata. (just like another user, zero4549 earlier in this thread)

I found another gentleman who experienced the exact same issue that I did, and has recovered all of his files without issue, just like many of the others in this thread. link1 link2

In the case that my self recovery fails, prior to doing so, can I take each drive of the raid and individually clone it to a 3TB drive, then attempt to restore the raid from the 4 duplicate drives I made? this theoretically would preserve the original drives so if I mess anything up, I would be able to take it to a professional no problem.

My question is, is it possible to clone the drives and then restore the RAID from the duplicate drives? If so, what steps should I take to clone the drives safely without any risk? Thanks!
post #266 of 278
I need help please !

I succeed restoring my Raid 0 partition with AOMEI , it detect and restored it but I can't access it from the explorer .

it says many errors in event viewer

{Delayed Write Failed} Windows was unable to save all the data for the file \:$I30:$INDEX_ALLOCATION. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

A corruption was discovered in the file system structure on volume F:.

A corruption was found in a file system index structure. The file reference number is 0x9000000000009. The name of the file is "". The corrupted index attribute is ":$SDH:$INDEX_ALLOCATION".



With AOMEI I can do a Chkdsk and it detect non stop errors and correct them

Should I let it finish ??

Using Stellar Recovery it detects all the files from the Partition ! What should I do ? Recover first or finish chkdsk !

Please someone help
post #267 of 278
So no one answered yet ?
post #268 of 278
Quote:
Originally Posted by el3c View Post

Mate, just make a account to say : THANK YOU !!!

you saved all my data (8tb) ... the hint for me was:

7. Mark the partition as Primary, write partition data to it

then i noticed: i had to use left or right cursor to set the partition to "P" wink.gif

Both raids are now live and working as before... i didnt know, what happens. last week i removed 16 gb RAM of my Sys from 32GB to use these in a other machine, after putting it back, my bios got reset and only want to start with a default setting set. i was not able to load any profile on my gigabyte board.

and now... i will buy a nas wink.gif

Also thanks to all others in this forum! many users witih the same Problem done a lot of work to help other.... thumbs up! thumb.gif

Brand new account here to say thank you. After reading this thread I STILL thought for sure I'd be screwed out of my 12TB RAID5. It took me a few days to build up the courage to follow these steps but I eventually did and would like to add a few things:

First, a little about my configuration and what happened:
  1. 4x4TB RAID5 configured as a non-operating system array Initially configured within Intel RST in Windows two years ago. - This bolded part was a huge uncertainty for me. I incorrectly assumed the Intel RST driver was a software RAID that was distinctly separate from the CTRL+I option ROM. In reality, Intel RST is a driver interface that allows you to manage the RAID from within windows, but it is the same RAID controller as CTRL+I. It's a driver that manages a Hardware RAID.
  2. Single PCIe SSD as my OS drive, another single SSD for my games, another single SSD for caching for my RAID5.
  3. Flashed MSI X99S SLI PLUS firmware from v1.7 to v1.D to troubleshoot what ended up being a failed video card in my SLI configuration. Identified the video card as the problem and doing a smoke test I noticed my data drive is completely missing.
  4. Intel RST driver wasn't even loading the GUI at this point within Windows.
  5. Discovered that the BIOS update reset all of my BIOS settings to default, including RAID -> AHCI.
  6. Restarted after setting the BIOS back to RAID, windows came up and my RAID wasn't just failed or offline, it was ENTIRELY GONE. I have no reference for what my RAID configuration was in terms of name or stripe size.
  7. Disk Management in Windows showed all 4 disks in weird states. Disk 3, Disk 4, Disk 5 and Disk 6 were the former RAID members. Disk 3 was automatically assigned a drive letter but prompted a format when i tried to access it. DON'T DO THAT, BY THE WAY. (I didn't). Interestingly Disk 3 showed up as 12TB. Disk 4 and Disk 5 were Online but not initialized and showing 4TB in size. Disk 6 was Online and initialized but not assigned a drive letter. Also showing 12TB. Totally weird.
  8. Came to this thread to do research and make a plan. Followed the Zero4549 + TheAssimilator guidance using TestDisk and filling in a few blanks, I'm back. My RAID5 is back and totally healthy.

Things I'd like to add to make this as smooth as possible for new users:
  • My four 4TB disks were already non-raid members, as opposed to some other people on here where their disks were in mixed states. I happened to be someone that didn't have to reset the raid member status before recreating the array. This is OK!
  • If you built your RAID array in Windows using Intel RST drivers and NOT CTRL+I, that's OK! The process to recover should be no different than setting it up using CTRL+I during boot.
  • While I can't completely confirm this, it seems that the former name of the array doesn't matter. Setting up RAIDs in RST gives them names like Volume_0001 and Volume_0002, where setting them up in the CTRL+I Option Rom creates them with names like Volume1. When I recreated my array in CTRL+I, I took the default name of Volume1 (instead of what RST would have named it in 2015) and my restore with TestDisk ended up working.
  • After writing the new partition tables with TestDisk and restarting, windows must have seen the drive signature because it automatically gave it the drive letter (F:) and drive label back (bin) with me having to do anything else. Beautiful.
  • It seems very strange, unintuitive and scary to make a whole new RAID array with disk members when your end goal is to restore data off of those same disks. As long as you don't have Intel RST installed in windows, everything is OK if you follow the steps.
post #269 of 278
I created an account just to thank the people in this thread- I have now used this method successfully 6 times... and each time, I'm really nervous about if the data is gone, but it works so far. Thanks again!
post #270 of 278
Quote:
Originally Posted by mjwinger1 View Post

Brand new account here to say thank you. After reading this thread I STILL thought for sure I'd be screwed out of my 12TB RAID5. It took me a few days to build up the courage to follow these steps but I eventually did and would like to add a few things:

First, a little about my configuration and what happened:
  1. 4x4TB RAID5 configured as a non-operating system array Initially configured within Intel RST in Windows two years ago. - This bolded part was a huge uncertainty for me. I incorrectly assumed the Intel RST driver was a software RAID that was distinctly separate from the CTRL+I option ROM. In reality, Intel RST is a driver interface that allows you to manage the RAID from within windows, but it is the same RAID controller as CTRL+I. It's a driver that manages a Hardware RAID.
  2. Single PCIe SSD as my OS drive, another single SSD for my games, another single SSD for caching for my RAID5.
  3. Flashed MSI X99S SLI PLUS firmware from v1.7 to v1.D to troubleshoot what ended up being a failed video card in my SLI configuration. Identified the video card as the problem and doing a smoke test I noticed my data drive is completely missing.
  4. Intel RST driver wasn't even loading the GUI at this point within Windows.
  5. Discovered that the BIOS update reset all of my BIOS settings to default, including RAID -> AHCI.
  6. Restarted after setting the BIOS back to RAID, windows came up and my RAID wasn't just failed or offline, it was ENTIRELY GONE. I have no reference for what my RAID configuration was in terms of name or stripe size.
  7. Disk Management in Windows showed all 4 disks in weird states. Disk 3, Disk 4, Disk 5 and Disk 6 were the former RAID members. Disk 3 was automatically assigned a drive letter but prompted a format when i tried to access it. DON'T DO THAT, BY THE WAY. (I didn't). Interestingly Disk 3 showed up as 12TB. Disk 4 and Disk 5 were Online but not initialized and showing 4TB in size. Disk 6 was Online and initialized but not assigned a drive letter. Also showing 12TB. Totally weird.
  8. Came to this thread to do research and make a plan. Followed the Zero4549 + TheAssimilator guidance using TestDisk and filling in a few blanks, I'm back. My RAID5 is back and totally healthy.

Things I'd like to add to make this as smooth as possible for new users:
  • My four 4TB disks were already non-raid members, as opposed to some other people on here where their disks were in mixed states. I happened to be someone that didn't have to reset the raid member status before recreating the array. This is OK!
  • If you built your RAID array in Windows using Intel RST drivers and NOT CTRL+I, that's OK! The process to recover should be no different than setting it up using CTRL+I during boot.
  • While I can't completely confirm this, it seems that the former name of the array doesn't matter. Setting up RAIDs in RST gives them names like Volume_0001 and Volume_0002, where setting them up in the CTRL+I Option Rom creates them with names like Volume1. When I recreated my array in CTRL+I, I took the default name of Volume1 (instead of what RST would have named it in 2015) and my restore with TestDisk ended up working.
  • After writing the new partition tables with TestDisk and restarting, windows must have seen the drive signature because it automatically gave it the drive letter (F:) and drive label back (bin) with me having to do anything else. Beautiful.
  • It seems very strange, unintuitive and scary to make a whole new RAID array with disk members when your end goal is to restore data off of those same disks. As long as you don't have Intel RST installed in windows, everything is OK if you follow the steps.


what if I deleted the first name it gives in windows raid0? which name should I give when using testdisk?
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..