Had to unplug 2 HDDs set up in Raid 1 for a while. After plugging back in, Windows doesn't recognise drives.

Ravyu

Honorable
Mar 8, 2012
293
0
10,810
Hi there,


I have a RAID 1 configuration set up with 2 HDDs and have been using it for about 3 months now. Yesterday, I had to unplug the two drives to free up SATA ports temporarily and use windows (which is installed on a seperate SSD).

After plugging them back in, my Windows install no longer recognises the RAID or the Drives (I checked Disk Manager as well as the Intel Rapid Storage app). However, when I access the Intel RAID program (the one where you need to press Ctrl + I at boot to get into), I can still see the two drives, configured in RAID 1. When I go to BIOS, everything is as normal, with the Storage set to RAID and the two drives being recognised. It's only when I use Windows am I not able to see anything.

Did I mess up by unplugging the drives, using windows, then replugging the drives (of course with shutdowns inbetween)? Do I need to reset everything? Because I have important data in these drives that I do not want to lose. Thanks!!
 
Solution
That's interesting. So is there nothing in Disk Management under Windows? You could try uninstalling Intel's RST app, I've never used that for my arrays, and they always worked fine. You can try booting from a Windows Installation disk/flashdrive, because that should see it when you select the destination disk. Of course, don't install anything, just check if it can see it. If it can, then there is something wrong with your current Windows installation. Let me know if any of this helps.

PhysX_HW

Distinguished
That's interesting. So is there nothing in Disk Management under Windows? You could try uninstalling Intel's RST app, I've never used that for my arrays, and they always worked fine. You can try booting from a Windows Installation disk/flashdrive, because that should see it when you select the destination disk. Of course, don't install anything, just check if it can see it. If it can, then there is something wrong with your current Windows installation. Let me know if any of this helps.
 
Solution