Overclock.net - An Overclocking Community - Reply to Topic

Thread: HowTo : Recover Intel RAID "Non-Member Disk" Error.. Reply to Thread
Title:
Message:

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.
Password
Please enter a password for your user account. Note that passwords are case-sensitive.
Password:
Confirm Password:
Email Address
Please enter a valid email address for yourself.
Email Address:

Log-in


  Additional Options
Miscellaneous Options

  Topic Review (Newest First)
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!

HTH
07-11-2018 12:56 AM
jcubed Thank you so much. This worked!!! And thank you to everyone who took part in posting and researching these things. I made this account just to say thank you.

Just for reference, I had a Raid10 with the 0 and 1 of my array being Non-Members. This happened after I updated the bios on my Z97-Pro motherboard. These were 4 2tb HDDs that were in array. I didn't actually move the placement of the SATA drives.
06-21-2018 08:36 PM
hell0sir Thank You so much... It worked !!!

Quote: Originally Posted by rdaraujo View Post
So, one more succesful case

My setup (revelant info only):
ICH10R RAID controller (onboard)
1x 320GB HD as boot (Windows 7 x64)
4x 2TB HD Caviar Green on RAID5
-> with 4 primary partitions on it, one of them 4TB in size

My history:

WIndows started to give me BSOD. After a couple of tries to correct it, I decided to restore BIOS default configurations (my mistake).
One of the configurations on BIOS is the arrangement of your HDs (IDE, ACPI or RAID, I think).. The default value for this configuration on my motherboard is not RAID, so when I loaded default configurations and booted (Windows is on a spare HD), two out of four RAID HDs were "Non-member". After the freak feeling has passed, I started to Google and found this thread.
I started to read all pages 2 or 3 times to figure out how to proceed correctly, as there were succesful cases and unsuccesful cases (unfortunetly).

So, I did as mentioned by Zero4549 on post #65, except for the fact that I did not uninstallled Intel Rapid Store app, I just disabled his service under Windows Services configurations (press Start menu, type service and you will find it).

After marking the two still RAID members from CTRL+I boot option as " non-member" (making all 4 drives as Non-member), I created another RAID5 with exactly the same configuration as before (same name (easy to remember), chunk size (the default one: 64KB) and the drivers order (from top-down as far as I remeber)) and booted.
I run TestDisk following their guide here: http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step

Everything was fine even with Quick Search, showing all my files (with P option).
5-10 minlater after write up partition table on TestDisk and booted, all my system was back to normal with no data loss.
The only anormal thing was that drive letters has changed, by you can change it as you desire.

Many thanks to Ictinike for the origial post, Zero4549 for this contribution and for everyone who enriched this thread!
02-07-2018 01:12 PM
Br0ski I would have to point you in the direction to say you are right about the drive letters. I am wondering if you could use a live version of GParted to correct the drive letters? You could make a PartedMagic live USB maybe? and change the letters?

I can't think of a way to tell your BIOS which drive to boot from?

Research more and don't listen to me. But this is some of the things I am thinking.

- Br0ski
01-28-2018 08:36 AM
mailalan
Drive letter assignment

Using the instruction in this thread I was able to recover my lost RAID array but now I can't get Windows 7 to boot up and I believe it's because my drive letters have changed. My operating system which was on drive C: is now drive E:. And what was drive F: is now drive D:. My DVD drive is now labeled F:. I believe that whats now the D: drive needs to be relabeled F: because that's where my Win7 user profile is stored.





In my setup I have two SSD drives in a RAID 1 array. This was my C: drive with the Windows 7 operating system.

I also had 4 spinning SATA drives in a RAID 10 array. This was my F: drive where I had placed my Win7 user profile.

When my BIOS settings were lost, Windows could not find the F: drive and would not boot up.

Before I realized what happened though, I had used Bootrec.exe in the Windows 7 Recovery Environment to run the FixMbr, /FixBoot, and /RebuildBcd commands. The first two said they worked but /RebuildBcd did not. I think doing that made things worse. So now I can't boot up.

So my old C: drive is now labeled as the E: drive.
And my old F: drive is now labeled as the D: drive.

I think I need to restore the correct drive letters as C: and F: before Windows will boot. Is that correct? Can anyone tell me how to fix this? Any help would be GREATLY appreciated!
01-16-2018 10:37 AM
stephenn82 hmmmmm

Do you have another DVI port on that card to test? Or maybe an HDMI to DVI adpater, etc? I think it sounds like the port is at fault. Have you removed and reapplied thermal compound in the past? Maybe something got jarred in there making contact on some pins to short out the DVI port? Just an idea...

If it was PCI-e at fault, I think the whole card would exhibit super issues, not just one port.
01-16-2018 06:52 AM
Br0ski @stephenn82

I have one over at nVidia's website asking the community but they won't be able to answer much.
I am going to spend the rest of the day switching it out with my second computer and see whats going on.

I think it might be a faulty DVI port. I just restarted my computer and it looked like safe mode?***!? with the DVI port monitor.
The DisplayPort is fine. Both my monitors are fine the cords are fine etc...

It also could be the PCIe slot but I highly doubt that.

Give me a couple hours and maybe I will come back and post my findings and start a thread. thumb.gif
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