Quantcast
Channel: Intel Communities: Message List
Viewing all articles
Browse latest Browse all 20046

Re: Request for advice on painless uninstallation of Intel RST RAID Driver version 13.2.4.1000

$
0
0

Hi joe_intel,

 

sorry for taking longer to respond. I have finally decided to try and solve the problem, but here's the next issue: It seems the above solution is meant for a hardware RAID, at least I do not get the CTRL-I prompt during POST. My RAID is a software RAID.

 

Any suggestions?

 

Thanks.

 

P.S.: In the meantime I have further investigated and have now activated the RAID option in the BIOS settings, and am now getting the CTRL-I prompt during POST. However, it shows the same information that is also reflected in the screen captures shown in my original post: My C: drive (boot drive) is correctly reflected as a RAID 0. This is something I did not mention because I had forgotten over time, but in fact is correct.

 

So the setup is the following:

 

Drive C: (boot drive with OS - Windows 7 Pro and all Program files on it), consists of two 1TB HDD's set up as RAID 0 with two partitions.

Drive G: (data disk), consists of two 3TB HDD's set up as RAID 1

 

Now the problem is that after the IRST driver update as mentioned in the original post, drive C: is still recognized as RAID 0, but not drive G:. Drive G: is recognized as two individual Non-RAID disks instead.

 

As a result, the solution you suggested would probably pose a problem with regard to the boot drive if the disks were set to Non-RAID (which is required as otherwise I can't uninstall the IRST RAID driver), as there is no mirror. On the other hand, the conncerned disks (G: drive) are ALREADY set to Non-RAID, or at least recognized as such.

 

My question therefore is: What should I do now??

 

Thanks!!

 

I include a screen capture from the Intel Matrix Storage Manager option ROM:

 


Viewing all articles
Browse latest Browse all 20046

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>