Follow Up: A New Method to Enable Intel ICH RAID after Installing Windows (Plus Updates to the Original)
Bypass this article and fix your Intel RAID Drivers immediately using RAIDFix
I have three pieces of information to share with those of you looking to enable RAID on your Windows PC after having installed Windows without RAID enabled in your BIOS settings. Now that you have rebooted past a handful of blue screens and Googled to find some help, I am here to tell you that you have come to the right place.
I have written on this topic twice before, once when I first figured out how to fix this problem, and again when the drivers had been updated by Intel. Once again there are driver updates, so I wanted to provide you the appropriate registry file as well as the steps required to enable RAID on your system.
But first, I wanted to mention an extremely easy and fast solution. After studying the problem for some time, I have put together an application named RAIDFix which installs the proper registry keys and drivers to get your Intel RAID up and running in seconds. As I pointed out in the large link above, fix your RAID issues immediately by clicking here.
If you prefer to fix the problem manually, read on.
Method #2 – The Long, but Tried and True Process
1) Download the Intel Matrix Storage Manager v8.9.0.1023 installer (Dated 7/17/2009) from Intel.
2) Open a command prompt on your machine and navigate to the folder where you saved the IMSM software in step 1.
3) Type “iata89enu.exe -a -p c:\iastor” and press Enter – this will load the installer and extract all of the driver files to C:\Iastor folder. Close the command prompt.
4) Copy the appropriate iastor.sys file from the C:\Iastor\winall folder to your C:Windows\System32\drivers\ directory
5) Click here to download the registry file, or copy the text below and save it as “Intel.reg”
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_8086&DEV_2822&CC_0104]
"ClassGUID"="{4d36e97b-e325-11ce-bfc1-08002be10318}"
"Security"=hex:01,00,04,90,00,00,00,00,00,00,00,00,00,00,00,00,14,00,00,00,02,\
00,4c,00,03,00,00,00,00,00,14,00,ff,01,1f,00,01,01,00,00,00,00,00,05,12,00,\
00,00,00,00,18,00,ff,01,1f,00,01,02,00,00,00,00,00,05,20,00,00,00,20,02,00,\
00,00,00,18,00,9f,01,12,00,01,02,00,00,00,00,00,05,20,00,00,00,21,02,00,00
"Service"="iaStor"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}\0001]
"InfPath"="oem39.inf"
"InfSection"="iaStor_Inst_RAID"
"ProviderName"="Intel"
"DriverDateData"=hex:00,c0,44,67,a7,e4,c9,01
"DriverDate"="6-4-2009"
"DriverVersion"="8.9.0.1023"
"MatchingDeviceId"="pci\\ven_8086&dev_2822&cc_0104"
"DriverDesc"="Intel(R) ICH8R/ICH9R/ICH10R/DO/PCH SATA RAID Controller"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor]
"Type"=dword:00000001
"Start"=dword:00000000
"ErrorControl"=dword:00000001
"Tag"=dword:00000019
"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,69,00,61,00,53,00,74,00,6f,00,72,\
00,2e,00,73,00,79,00,73,00,00,00
"DisplayName"="Intel RAID Controller"
"Group"="SCSI Miniport"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Parameters]
"queuePriorityEnable"=dword:00000000
"BusType"=dword:00000008
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Parameters\Port0]
"AN"=dword:00000000
"LPM"=dword:00000000
"LPMSTATE"=dword:00000000
"LPMDSTATE"=dword:00000001
"GTF"=dword:00000000
"DIPM"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Parameters\Port1]
"AN"=dword:00000000
"LPM"=dword:00000000
"LPMSTATE"=dword:00000000
"LPMDSTATE"=dword:00000001
"GTF"=dword:00000000
"DIPM"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Parameters\Port2]
"AN"=dword:00000000
"LPM"=dword:00000000
"LPMSTATE"=dword:00000000
"LPMDSTATE"=dword:00000001
"GTF"=dword:00000000
"DIPM"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Parameters\Port3]
"AN"=dword:00000000
"LPM"=dword:00000000
"LPMSTATE"=dword:00000000
"LPMDSTATE"=dword:00000001
"GTF"=dword:00000000
"DIPM"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Parameters\Port4]
"AN"=dword:00000000
"LPM"=dword:00000000
"LPMSTATE"=dword:00000000
"LPMDSTATE"=dword:00000001
"GTF"=dword:00000000
"DIPM"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Parameters\Port5]
"AN"=dword:00000000
"LPM"=dword:00000000
"LPMSTATE"=dword:00000000
"LPMDSTATE"=dword:00000001
"GTF"=dword:00000000
"DIPM"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Parameters\oromVersion]
"MajorVersion"=dword:00000007
"MinorVersion"=dword:00000005
"HotfixNumber"=dword:00000000
"BuildNumber"=dword:000003f9
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Enum]
"0"="PCI\\VEN_8086&DEV_2822&SUBSYS_82771043&REV_02\\3&11583659&0&FA"
"Count"=dword:00000001
"NextInstance"=dword:00000001
6) Double-click on the .reg file and click yes when asked if you want to merge the data into your registry.
7) Reboot the computer and change the SATA configuration in your BIOS to RAID – Windows should load without any issue.
8 ) Install the Intel Matrix Storage Manager software to complete the driver installation/configuration.
9) Celebrate the fact that you have now enabled RAID without having to reinstall Windows.
Good luck with your RAID install! Feel free to ask questions here if you need help.
Method #3 – Peregrinus’ Hack
A reader named Peregrinus discovered that there might be an even easier method to get your computer up and running again. Instead of expanding drivers and manually adding registry information to your computer, you can fix the problem with one small registry tweak.
I do have to add the disclaimer that I have not tried this method, so your mileage may vary. Peregrinus stated that this worked for him, so I am publishing this information on his recommendation.
1) With RAID disabled, boot into Windows and start Regedit.exe
2) Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\iaStorV
3) In the right-hand column, you should see a value named Start. Double-click this entry and change the data from 1 to 0.
4) Reboot with RAID enabled – Windows should load just fine. Now install the Intel Matrix Storage Manager as you usually would. This time around, it should detect your hardware and install without any issues.
Peregrinus’ suggestion didn’t work for me, but the “tried and true” method worked flawlessly. Dr Nathan, you are my personal hero. Thanks!
Method #3 – Peregrinus’ Hack worked fine for me!
I hava an Asus P5W DH Deluxe Mainboard with an Intel ICH7R Chipset. Setting the “Start”-value from “3″ to “0″ let windows 7 64 Bit boot in RAID mode. After that i could install Intel Storage Manager without any problems. My Raid-0 (2x 1TB Western Digital Caviar Green) runs now.
Thanks Dr Nathan and Peregrinus!
You are real heros :-)
James,
Thanks for the feedback. I will wait and see if other people have the same results with Peregrinus’ method – if so, I will pull the information.
I just tried the new method right now, and it worked. I was able to boot in raid mode with no issues. My only problem was that my controller is labeled as ich8r/ich9r instead of the ich10r that it is supposed to be. I don’t think it will be a problem, but I’m wondering if there is something else that needs to be changed so that it recognizes it as an ich10r chipset that it’s supposed to be.
Jay,
Did you install the Intel Matrix Storage Manager after tweaking the iastorv setting in the registry?
If so, Windows *should* recognize the controller for what it is.
I installed the Intel Matrix Storage Manager before tweaking iastorv. Maybe I will uninstall, and reinstall.
you are the man! the easy fix worked for me. and man, am i thankful.
i just bought a dell studio xps much like yourself and installed a couple hard drives after already having installed a clean copy of vista business. i had even found a way to raid 2 hard drives in the ahci mode, but they weren’t being managed by the intel matrix storage controller as raided drives and it worried me that i would have no way to know if one failed (they were raid 1).
i’m actually just typing most of this to add keywords so that other people can find this when they search. everything else i found told me to reinstall vista – that would have sucked since i had an old original copy vista and had to fight my way up through the service packs and updates to get it working right.
i can’t believe this turned out to be a 1 digit fix. so awesome! my registry actually had 4 as the start value instead of 1 (fyi). but i changed it to 0 and restarted and the storage manager fixed itself. after another reboot, the storage manager showed everything raided as it should be. so easy!
thank you again.
worked for me too; thanks *alot*
As alex above said, you ARE the man! :D
After hours of frustration and reboots/reconfig/Repair console/BSODs i stumbled upon your blog, and thank God, i was ready to give up
Your “tried and true” method works like a charm, it just does! Currently the Intel Matrix Storage Console is at 4% of migrating my RAID and i did not picture it to be quite this easy to evade the hassle of reinstalling a whole OS – by the way this method works on Windows 7 RC1, which i am currently using.
Thanks again for this best solution
p.s. makes you wonder why this type of driver installation is not made as official option throughout the hardware vendors, for scenarios like ours
2lame,
I am glad to hear that my post help you fix your issues.
I completely agree that this issue should be far easier to fix than it is. Theoretically, you are “installing” the RAID driver to some extent when you copy over the Iastor.sys file and tweak the registry. There does not seem to be any reason that Intel should not allow you to install the driver with their application, but they lock you out if the application does not see RAID-enabled hardware. Perhaps someday…
I did not set the value to RAID in bios when I built my new system in July 2009. I was shocked when I figured out that it was too late and I’d need to rebuild my system. So I looked for alternatives, and found your solution(s) in August. However, I dreaded the task and family matters combined to delay my attempt to apply your fix. The delay paid off, as the new “one small registry tweak” method did the trick for me. It worked so well that now I’m wondering what all my fussing was about.
Thanks DrNathan & Peregrinus!
I had it exactly the same as Alex did, and resolved it in exactly the same manner. Brilliant – huge thanks!
I have researched for hours on how to fix this BSOD issue with this raid controller while trying to boot Vista x64. I never wanted Vista to boot from my raid, but yet it would blue screen every time I set this controller to raid mode in the bios. Like I said, I have searched for hours and played with registry settings and nothing work. I then downloaded your reg file, and with one click, problem solved. Thanks for saving me a huge headache!!!!
Abit IP35 PRO XE
Intel ICH9R
Windows Visa x64
Raid 5
5 Seagate 7200.11 1.5 TB drives
5.45 TB total space :)
Also many reboots and bios configuration later…, the first solution helped me out.
The raid controller is now being installed. And it all seems to work fine.
Asus P5Q Pro
320gb Samsung HD321KJ (existing installation)
2*1000gb Samsung HD103SJ (newly added in raid 1)
Sooooo easy.
Incredible Microsoft/Intel do not have a solution for automatting this task.
Thanks to the Dr. too. Your solution was hard won, and useful for those who cannot use Peregrinus’ suggestion.
Just a marker: first time it did not work for me. Why? Because I had the setting “3″ and changed it to “1″ in stead of “0″ (bummer…). Maybe some of those who cannot get it to work should double check their settings.
DrNathan,
Last week I updated from Vista 64 to Windows 7 64. Everything was great, except for the fact that I was experiencing problems with my Raid0 array set up on the JMicron controller on my motherboard. Googling JMicron Raid installations on the net, I noticed manyyyyyyy complaints with the JMicron Raid configurations and I decided to move my Raid array to the Intel controller.
After Googling on the subject for about 5 hours, I was kind of discouraged and shocked to find that there was no way to install Raid on my Intel controller if I hadn’t set the Bios to Raid before installing the OS. But then I found your solution. It took me about 5 minutes to complete the setup as per your instructions and everything works fine.
Thanks a million DrNathan. You saved me quite a few hours of work.
I still can’t believe that Intel hasn’t figured this out yet. They are still saying it can’t be done. Is it that they lack the knowledge is is it that they just won’t bother to find a solution to satisfy their customers.
THEY SHOULD HIRE YOU ON A FULL TIME BASIS…….
Thanks again.
Rick
Thanks for the compliments, I am glad that I was able to help you out.
It still does boggle the mind that Intel has no published method of making this work at all.
As for being picked up by Intel, one can only hope!
I just finished building a Windows 7 64bit system for video capturing and editing about a month ago. Initially, I had a 64GB Kingston SSD for the OS and programs and two 1.5TB Seagate Barracudas for storage and capturing. But then I decided to install two Caviar Black 640GB HDD’s in RAID 0 to take full advantage of the capabilities of my Blackmagic Intensity Pro HDMI capture card, and that’s when I ran into problems trying to get Windows to boot. After a couple of days of head scratching and googling for solutions, I remembered that my motherboard, an ASUS P7P55D, had an unused JMicron SATA connector in addition to the six Intel SATA connectors.
Solution: 1) Load JMicron driver from motherboard disc. 2) Switch SSD from Intel SATA connector to JMicron SATA connector. 3) Change storage configuration setting from IDE to RAID in BIOS. 4) Create RAID array as per motherboard manual. 5) Start up Windows and initialize RAID array in administrative tools and Voila.
Bryan,
Well, that’s one way to fix it if you happen to be able to switch to a different RAID controller completely.
If you have only one controller that happens to be Intel, you have but three choices in the matter. Reinstall everything, try my method, or try RAIDFix.
I went to do the simple method but found the Start value to be “3″. I don’t want to take any chances with changing it to “0″ without checking here first. I have a P7p55d LE motherboard and Windows 7 Ultimate (x64).
The SATA Configuration in bios is set to IDE, and I’ve never tried to change it. Any advice?
Thanks!
dbl_clutch,
If you are a little hesitant to try one of the manual methods, your best bet is to try the utility that I created which does it for you. RAIDFix can be found over here.
All you do is run RAIDFix on your machine, select that you are using a 64-bit OS, and click “Patch my machine”. After that, reboot your computer, change the SATA configuration to RAID, and you are good to go.
Just make sure you install Intel’s Matrix Storage Manager software after you boot back into Windows with RAID enabled so that you can manage your arrays from Windows.
Let me know how you make out.
Well, I tried it. Did not work. At boot up it did not recognize the C: drive as bootable. I switched back to IDE and it booted fine, then installed the older version and tried again, same problem.
Any ideas?
Thanks,
dbl_clutch
dbl_clutch,
Just to make sure, you are trying to enable RAID, not AHCI, correct? The process for enabling each of those features is somewhat slightly different, and my application only covers RAID.
If you are indeed trying to enable RAID, I have a few questions and a suggestion:
1) Do you have more than two hard drives in your PC?
2) Have you checked the boot order in your system’s BIOS after switching to RAID, but before booting Windows?
I ask these two questions because on my board, an Asus P5E, whenever I switch to or from RAID mode, the motherboard will rearrange the hard drive boot order. The problem you are having when switching to RAID, the PC not finding your Windows installation, is a sign of the motherboard looking at the wrong drive as the boot device rather than RAID failing in Windows.
I typically run in RAID mode, but when I switch back to IDE compatible, the boot order will change. Each time, I have to boot the PC, switch to IDE mode in the BIOS, reboot, configure the boot order, reboot again. At this point, Windows will load normally as I have directed the BIOS to look at the proper drive. When I switch back to RAID mode, I have to go through the same process.
Give your boot order a look after switching to RAID mode and see if that is the issue. Remember however, you will likely need to exit the BIOS and reboot before checking the boot order, depending on your motherboard.
Hope that helps!
Thanks DrNathan,
Your suspision was correct, but not in the way you thought. I had 4 hard drives attached, 3 SATA (1 system drive and 2 data drives targetted for RAID1), and also one ATA drive attached to the one available Jmicron connector of the motherboard. I added this as another storage drive because I have about 10 of these old ATA100 drives laying around.
I did as you said and checked if the boot order had changed after switching to RAID (booting twice), but found the boot order was not changed as on your computer. But what I realized was that the only hard drive that it would allow as the boot drive was the one Jmicron connected drive. Very curious. So I removed the Jmicron drive and the system booted up as expected. I am now creating the RAID array and everything else is as before.
Thanks for the help! It’s great that there are people like you out there helping people when the manufacturers are unwilling to.
Thanks!
–dbl_clutch
Excellent solution. I tried your original one on my P7P55D with Windows 7 64-bit and I still got the BSOD. I fast forwarded to this latest approach using the shortcut registry edit. That did the trick!!! I am currently setting up RAID 1 on my 1.5TB data drive.
Thanks for taking the time to document and share all of this. I could not bear going through another Windows 7 installation, reboots and the dreaded Windows Activation debacle!!!
Many many thanks for your time spent and sharing knowledge! Method #3 – Peregrinus’ Hack worked on my ASUS P5Q-EM with ICH10R (initially the start value was 4 rather than 1) with Vista 64-bit. I used it to swich from AHCI to RAID.
Initially I switched from IDE to AHCI some time ago by forcing install of intel’s driver, allowing reboot and changing BIOS setting to AHCI before the system boots.
I’m interested in trying this but there’s one issue: When I go to enable the RAID1 using Intel’s raid creation tool (comes up just after BIOS) it tells me that creating the RAID1 will destroy all data on both disks. If that’s the case, then I might as well plan to reinstall the whole OS, eh?
Or is it the Intel tool not correct?
Reading comprehension failure on my part. I see that we should be using the Windows-based console, not the text/boot tool.
However, Intel Matrix Storage Console doesn’t do the job, either. It gives the helpful error: “Volume creation failed”. Their site suggests shrinking the drive a bit so it can store RAID metadata, but I tried shrinking it between 8 and 500MB to no avail.
The drives are exactly identical.
Is there a log I should be looking at?
dpk,
The issue you are having is definitely a strange one. I have not seen anything like it before – is the second drive you are adding (your mirror) already formatted?
How full is your primary drive?
Also, are you sure you have selected RAID 1 rather than RAID 0? If you are converting the volume to RAID 0, it will indeed erase any data already present on the disks. RAID 1 however should simply copy the primary drive’s data to the secondary drive – I have created many a RAID 1 array after installing windows without any data loss.
DrNathan,
The second drive is unformatted, but it also tried it formatted, too. The primary drive is 393GB out of 465GB. I’m sure I’ve selected RAID 1. The only thing I can guess is that it could be because my primary drive is “dynamic”. That shouldn’t matter, obviously, because the RAID is hardware.
What’s most frustrating is knowing that this is a one, maybe two line operation in Linux.
dpk,
Where are you attempting to create your RAID volume? You mentioned that this is typically a 2-line operation in Linux, so I am guessing that you are trying to create the RAID volume via Windows, correct?
I typically shy away from doing it in Windows and instead configure my arrays from within the RAID controller’s BIOS, before Windows even boots. You will typically see a message similar to “Press Ctrl+I to configure RAID” after your computer’s BIOS messages pass, but before the Windows loading screen appears. I recommend configuring RAID there – you might have better luck doing it that way.
DrNathan,
I am trying to create it in Windows, I only mentioned Linux because Windows and/or Intel seem to be making this 100x more complicated than it ought to be.
In any case, I thought that the whole point of this method was to make the RAID work after Windows was already installed. When I try go to set up the RAID early on, immediately after BIOS, the tool tells me it’ll destroy all data on all disks, something I was hoping to avoid. Did I totally misunderstand the goal and techniques laid out here?
Many thanks, works great!
Instead of extracting the iastor.sys from Intel(R) Matrix Storage Manager as you described in this new and the previous method.
Simply download the “32-bit Floppy Configuration Utility”, the file is inside the zip file :)
dpk,
If you had a spare disk sitting around, I would try cloning your OS drive so you have a backup, then giving the RAID configuration in the BIOS a try. I know it states that it will destroy all of your data, but that sounds like it is a simple “catch all” warning that Intel chucked in there just in case the configuration process blew your data away.
I personally have configured RAID 1 arrays after installing and configuring Windows on an ICH10 controller without any problems at all. Not a single byte of data was lost.
Tnx 1000x
Thanks for these hints :-)
I used Peregrinus hint and it worked perfectly for me (on Windows 7 x64). I guess the reason why it doesn’t work for some people is, that they had AHCI activated before. To deactivate you have to set HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\msahci\start to 3 (should have been 0 if active). Although I didn’t try it I think you are only allowed to have either msahci or iaStorV active. Maybe you want to give this a try if Peregrinus instructions won’t work for you
For me the Peregrinus hint is worked perfectly but with first and second method didn’t (on Windows 7 x64 for ICH7R MB:SuperMicro X7DAE) BIG THANKS
Method #3 – Peregrinus’ Hack worked for me. I switched from IDE to RAID on a Asus P55D-E mainboard.
You are a life saver ! I’ve run your program and I could then start Windows 7 with RAID mode enabled in BIOS. I was so annoyed just thinking I had to re-install my system to enable RAID…..
Thanks a lot !
Parfait, merci! thanks!
travaux parfaitement sur mon windows 7 64bit norvégien!
works perfectly on mine!
Works perfect for me. My situation was the following:
w7 installation based on a nforce chipset with a raid5 config., sysprepped and moved to a new board in AHCI mode (Asus P6X58D-E) installed the drivers and want to migrate to raid again.
I just took the differences of your registry settings to mine and reboot.
Voila – it works. Thanks a lot!
Thank you!
Method #3 – Peregrinus’ Hack worked for me.
MB: Supermicro X7SBi-LN4 ICH9
Many thanks!
Method #3 – Peregrinus’ Hack worked for me.
It’s just sick how well this works and how disastrous the conventional wisdom is. 10 seconds with regedit vs. days rebuilding my system? WTF?
How can I PayPal you some dough, DrNathan? I’m serious. Please e-mail me.
Mobo: Asus P6X58D-E
Win7 x64
OS on SSD (drive C:)
2 x 600GB HDDs as RAID 1 (drive E:)
Involute,
No need to send money my way, I’m glad to be of help. My email address is mike at geek – republic dot com, but seriously you don’t need to send me anything!
[...] describes a couple of methods of enabling Intel’s RAID driver by editing the Windows registry (first method, second method). At the bottom of the first post I found following [...]
This article is useful for me.
I use the Method #3 – Peregrinus’ Hack.
It works fine.
My os is win 7 x64, installed on AHCI, with Intel rapid storage driver.
I try to add a raid 0 with my new drives but with old OS.
So I changed reg iaStorV from “3″ to “0″, reboot, change bios to RAID,
Then I entered the OS and the Raid controller is enable after another reboot requested by the OS.
Methed #1 is cool for most of people.
While I am from China, the internet is controlled.
RAIDFix.exe can not connect to server.
Now I connect to this web by a online proxy.
This guide would be very useful for me if anyone was able to provide me with the equivalent information for RAID from AMD SB850 chipsets.
To install the AMD RAID drivers I had to make a minor modification to its .INF file so that it’d allow a manual install.
I then tried Method #3 (from Peregrinus), of course first locating the equivalent registry key for my drivers. I found it at:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ahcix64I changed the respective
Startentry value, rebooted, changed SATA type from IDE to RAID but didn’t work for me: I keep having BSODs when loading Windows.Could anyone provide the exported registry entries for this driver/chipset?
Thanks in advance!
Peregrinus’ Hack worked like a charm!!! Thank you sooooo much.
I had a win 7 pro system setup with a raid 1 array (sata drives only) and while installing a new raid 5 array got an error message and pressed the key that reset the bios to default values. Funny thing is that the machine continued to boot with raid activated and allowed me to setup the new drives. Upon reboot, the system came up as a normal ide drive. I stupidly changed the bios back to raid (which shows the raid arrays as being fine and dandy and normal) and then let windows try and recover things (the stupid part). It loaded new drivers for the ide drives. The system has the intel matrix storage manager installed. This is an Asus P7P55D-E Pro Board. Help!