Solved W7 clean install and amd 9-series raid drivers

[sasxa]

Hi,
I'm having some problems with my new rig - windows 7 x64 installation doesn't recognize hard disks. All hardware is operational, it's recognized by BIOS and works with Win8CP, but can't make it work with W7.

I have Gigabyte's GA-990XA-UD3 rev1.1 motherboard. In BIOS I've turned on RAID, set up arrays in MB's raid tool - 2xSSD raid 0 (connected to SATA3_0 and SATA3_1 ports), 4xSATA2 raid 5 (connected to SATA3_2-4 ports). Drives are clean, empty and working; I don't have any issues with power (700W) or anything similar - everything works. Also I don't have any optical drives, all installations are from USB sticks, and that works too.

After booting to windows 7 installer and few initial steps, I get to the screen with boot drive selection and installer doesn't recognize the raid arrays; it asks for the drivers but none of the drivers from disk i got with MB work (divers downloaded from website don't work either). I did try to install them from repair tool too.

When installing Window 8 Consumer Preview my raid 0 array is recognized and windows installs correctly (it didn't recognize raid 5 array, but did 'see' 4 separate disks, and strangely two were disabled, but I figured I'll deal with it from windows...).

Anyone have similar problems or knows how to solve this? Or does anyone know a way to 'copy' drivers from w8 to w7 installation?

This is a production machine, so I don't want to keep Win8 and want to install Win7 x64...

Also, I should mention I'm using en_windows_7_ultimate_with_sp1_x64_dvd_618240.iso MSDN installation and Windows7-USB-DVD-tool to make bootable USB.

Any help would be appreciated.

 

[sasxa]

When Windows is asking for driver, just click Cancel. You will be brought back to the welcome screen. At the welcome screen, remove your USB drive, insert it back to DIFFERENT USB PORT. Click Install Now again. The installation process will be like usual.

This problem happened to all new version of updated Windows 7 installer. I think, it is due to failure of Windows installer to remain its detection to the USB drive. It lost the connection, and became confused, don't know where to find the USB drive it used to read before.

When we re-insert the USB drive, Windows installer will detect the USB drive back, and continue like usual.

LOL