|Topic Review (Newest First)|
|11-13-2019 11: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 05: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.
Searching for a resolution:
Thanks again to all of you!!
|10-16-2019 10:33 PM|
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 09: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 11:16 PM|
|Y.O.N||hello, how to boot to windows if the window on the broken raid?|
|08-30-2018 11:16 PM|
|Y.O.N||Hello, how to boot to windows if the window on the broken raid?|
|08-24-2018 12:45 PM|
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:
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
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
- 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 11:48 AM|
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.
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!
|07-11-2018 01:56 AM|
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 09:36 PM|
Thank You so much... It worked !!!
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
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!
|This thread has more than 10 replies. Click here to review the whole thread.|