Overclock.net - An Overclocking Community - Reply to Topic
Thread: HowTo : Recover Intel RAID "Non-Member Disk" Error.. Reply to Thread

Register Now

In order to be able to post messages on the Overclock.net - An Overclocking Community forums, you must first register.
Please enter your desired user name, your email address and other required details in the form below.
User Name:
If you do not want to register, fill this field only and the name will be used as user name for your post.
Please enter a password for your user account. Note that passwords are case-sensitive.
Confirm Password:
Email Address
Please enter a valid email address for yourself.
Email Address:


  Additional Options
Miscellaneous Options

  Topic Review (Newest First)
06-19-2020 02:04 AM
Sandra McGray
Recover Data From RAID

Hi The RAID recovery software uses powerful algorithms to automatically match patterns and identify the RAID parameters. This RAID data recovery software for Windows works without the RAID controller card. It can build virtual RAID, search deleted/lost RAID volumes, and recover data from RAW or lost RAID volumes. Here you can try Stellar Data Recovery Technician that helps to recover data from non member disk. For more information you can check here: https://www.stellarinfo.com/windows-raid-recovery.php
04-09-2020 06:22 AM
RAID 1 - Non Member Disk - Locked Drives

So thankful I found this forum post, not sure my situation fits - but wanted to ask.

I am running (or was) RAID 1 - two identical 4TB drives.

I had this issue happen back in November, but after multiple unplug/replug the drives eventually worked

I started having problems again 2 weeks ago:
- At boot up - sometimes I see both of my drives that should be raid - but they both show as 'Non-Member-Disk'.
- When I get Windows booted (which is thankfully on an SSD that is not running RAID) and launch Intel RapidStore - I have had mixed results. Sometimes both drives show as locked. Sometimes only one drive shows (the other is missing) but is shown as locked.

I contacted INtel support - and while they tried to be helpful, I am still stuck.
I tried contacting Dell support, but that was a joke. The agent was suggesting completely wrong solutions and did not understand my problem.

Perhaps a silly question - They are RAID 1 - is there a simple way to remove the lock so I could recover my files? If this is not possible, this seems like a major flaw in the RAID design.
11-13-2019 10:20 PM
sean8102 For some reason my motherboard dose not let me enter the IRST interface with Ctrl+I, even though the manual says you can. But same as you all the same things can be done in the motherboards BIOS menus.
11-09-2019 04:44 PM
Over a decade later...

Over a decade later this procedure still holds! Thanks to the OP(Ictinike) and everyone who shared their experiences. Reading this has been very informative and encouraging. My situation is very similar but not the same. I can't use Ctrl+I for an IRST interface but rather must use the interface included in my bios screen.

My situation:
  • raid 10
  • 4x8tb shucked external drives for "16tb"
  • Not my windows install, just for storage/archive.
  • mobo: ASRock Z370 Professional Gaming i7 LGA 1151
  • copied files to the array earlier in the day without issue
  • went to search for a file later in the night and realized I had no results from the array
  • IRST reported two drives as there but not part of the array.

Searching for a resolution:
  • Shut off computer and went to bed. Some research and formation of a plan was needed.
  • Searched some tech forums for my issue, this discussion being one of the first things I found.
  • Read or skimmed every post here, noting situations that were closely aligned to mine
  • Looked on youtube for documentation of somebody following this procedure and indeed I found:

The resolution:
  • Uninstall IRST (Thanks Zero4549!)
  • Reboot and enter the bios.
  • Head to Advanced -> Intel Rapid Storage Technology
  • Here we can see my failed raid array and the two drives that should be in it.
  • Select the raid array and hit Enter
  • Take a screenshot of the configuration if possible (F12 on my system)
  • For each drive: select it and hit Enter. You'll see the option to "Reset to non-RAID". Hit Enter to choose that option. Confirm when asked to.
  • Once done with reseting the raid drives you should see the raid array is gone from the main IRST screen.
  • Select "Create RAID Volume" and proceed with putting in the information from your screenshot or notes.
  • Once created, use F10 to save and exit setup.
  • Your computer will reboot and should load into windows.
  • Download if you haven't already the TestDisk tool: https://www.cgsecurity.org/wiki/TestDisk_Download
  • Extract the archive, simply double click on testdisk_win.exe to run the cli tool
  • The prompts are pretty straightforward. You should see your array as one of the drives to search, not the individual drives. Before starting the quick search process I saw the familiar name for the drive already there. I wonder if I could have simply initialized it with Windows? Either way... I just did the Quick Search which re-found the partition. I skipped Deep Search and wrote the partition information.
  • I rebooted and bippity boppity boo there was my drive letter and all the data too!

Thanks again to all of you!!
10-16-2019 09:33 PM
sean8102 I had to make a account just to say THANK YOU SO MUCH. I have a 1 TB NVME SSD for Windows, and two 3TB HDD's in RAID0 for the large majority of my games (ones I'm not playing much ATM or don't benefit much from SSD). I have a MSI Z370 board and for some reason any time you do a BIOS update it causes the exact issue you described of the RAID volume failing because one of the drives gets dropped as a member of the array. Hell it actually happened this time without me even updating the BIOS, it happened just from booting into the motheboards flash mode (M-flash). I didn't update because I frogot to format the USB stick to FAT32 so it could't detect the flash drive so I just clicked cancel and rebooted. That alone cause the RAID array screw up problem.

Just went into the bios removed the 1 drive that was still in the array, re created the array exactly as it was. Used test disk it found the partition instantly (make sure to pick GPT if using UEFI). I had it write the partition structure back, rebooted and the drive was right back. Can't believe it. Thank you so much again.
09-14-2019 08:39 PM
Attempting to fix RAID5 with 2 non-member disks

This is a fantastic thread, with so many great suggestions.

I am looking to follow the below instructions provided in this thread which seem to be the best for my situation:

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!

However I have a problem. Here is my situation: I am running 4 x 6TB drives in RAID5. I set these up using the Intel Rapid Storage Technology (RST) RAID creation tool through my BIOS. The RAID is used for storage and my OS is running on a seperate SSD. My motherboard is ASUS GRYPHON Z97. After a BIOS firmware update, 2 of the 4 disks fell out of my RAID configuration and it now only shows 2 member disks, with the other 2 disks as non-member. I formatted my SSD and installed a fresh version of Windows 10. The RAID problem remains.

It appears to me (although I'm a nooblette) that Intel RST must be used with my motherboard, as it is built into the BIOS as the only way to set up RAID configurations. I am unable to boot into Windows in RAID mode, and I get inaccesible boot device error. When I boot into Windows in ACHI mode there's no problem, however the RAID of course does not appear. When I boot into Windows in ACHI mode, it also appears that Intel RST is uninstalled as a program and there are no drivers for it, so there is nothing for me to uninstall.

How do I begin this recovery process with any confidence that when I recreate the RAID (using the above instructions) and I boot in with RAID mode enabled that Intel RST wont just load up and start to initialise my disks automatically and I will lose everything?

Appreciate the help of anyone who can assist.
08-30-2018 10:16 PM
Y.O.N hello, how to boot to windows if the window on the broken raid?
08-30-2018 10:16 PM
Y.O.N Hello, how to boot to windows if the window on the broken raid?
08-24-2018 11:45 AM
ParallelFiber Hello to all,
This thread gave me a lot of hope, I read it front to back.

I encountered the same problem as you all.

I created my RAID5 array on a Asus p8p67 deluxe. My OS is on a separate disk
I moved the disk to a new motherboard, MSI x99 mpower and sure enough 2 of the 4 drive were marked as non member.

I followed the steps here:

Quote: Originally Posted by Zero4549 View Post
Solved it a few hours ago. Was able to repair the array after carefully reading the whole guide thread over several times and making some wild-guess modifications to the procedure based on the issues people were having.

What I did, new/modified steps in green:
1) Booted into windows and uninstalled Intel Matrix / Intel Rapid Storage software!
2) Rebooted, Reset to non-raid (did not delete)
3) Build new raid identical to previous one.
4) Booted into windows and used TestDisk to analyze.
5) Quick Search with Testdisk returned no readable files/
6) Deeper search revealed the original RAID 10 partition after about 10 seconds (it continued for what would have been several hours afterwards, discovering error after error after error until I stopped it).
7) RAID 10 partition showed correct files, marked it as primary partition, wrote partition data to disk using testdisk
8) Rebooted
9) Re-established links within windows (and re-installed chrome... for whatever reason that and only that got corrupted in the process... and it wasn't even on the raid to begin with! I was on C! As soon as I reinstalled it, all the bookmarks, extensions, and settings were in place automatically. Whatever)

Note that my raid was my "d" drive and not my "c". I believe this is the key! The majority of users following this guide have had their RAID as their C drive and as such when they followed this guide, the intel software was not readable until the process was finished. For several users the method did not work due to intel software attempting to re-initialize the new raid therefore overwriting old data - these users logically had a separate C drive where the intel software was free to work while attempting this fix.

In other words, if your raid is NOT your C drive, you must first uninstall intel software to prevent erroneous re-initialization.

Anyway, thanks for your input mmiszkiel. +rep for responding helpfully even if it was a wee bit late
I encountered a few problems:
- when trying to previez the files, the program just crashed
- after writing the partition and rebooting, the partition is not accessible (RAW format, data inaccessible or corrupted)

Is there any chance some had this issue as well ? How did you fix it ?

Thanks in advance for your help
07-26-2018 10:48 AM
_retro__gamer_ Hi guys,

Just joined to give you a big thank you, speacially to the opener. And to provide some recent feedback, as this thread has gone slightly silent over the last years.

My story:
Since a year and a half or so, my MSI GT72 Pro, which mounts a 4x128Gb SSD RAID0 as a primary drive and runs Windows 8.1 failed from time to time showing a non-raid message on one of the drives. I normally fixed that by restarting several times until the OS eventually booted. After that, instead of shutting down the laptop at nights, I suspended it, and that prevented that thing from happening again until the times I failed to enforce the rule of "not letting the computer die", for example running it without power supply and letting the battery die. This used to produce the aforesaid error 90% of the times. But as I said, some restarts (even deep ones with the reset button you have to push with a needle) fixed the thing. It has never been clear to me what is the exact action that triggers the OS to finally reload, but after some minutes it always worked so I didn't give it much of a thought.

Until yesterday. Another battery drain shut down the computer intempestively and for five hours I tried the restart thing without success. I though that that was it. That I would have to send it to MSI support, wait for a month and then reinstall everything. D:

But before that, I thought that what kind of IT guy am I if I don't try some other options besides restart^n. That's how I came across with this thread today, which I read completely, and decided to try the steps of the opening post. And man did they work! Sure they did.

As useful complementary tips:
- I didn't have another drive to install windows to run testdisk from it. Well, I do have another one (1TB non SSD), but is the one I use to store the data, so installing there another windows was not an option.
- What I did instead, was to download at work the recovery ISO of W8.1 from MS website, write it to a USB stick using the "Windows USB/DVD download tool", then download the TestDisk for windows 7, and put it in another USB stick.
- After doing the BIOS steps (undoing and redoing the RAID), I changed boot order to start from USB and connected the USB with the image of the W8.1 recovery media.
- Then, after loading with it, I went to repair -> advanced -> command prompt (or something like that), connected the other USB stick (the one with testdisk) in another free USB slot and started trying letters until I found that the USB was at F (being in X:> initially, I typed X:>F: to switch to it).
- Then I launched the TestDisk_win.exe present in the TestDisk folder inside F and followed the steps of that link (http://blog.quindorian.org/2013/07/r...reported.html/) for the testdisk specific stuff
- When finished, I exited everything and shut down the computer.
- Then I rebooted without the USB drive, and voilà!! Back on business. No need to run the fixmbr&fixboot commands.

Thank you all again!

This thread has more than 10 replies. Click here to review the whole thread.

Posting Rules  
You may post new threads
You may post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off