No boot device when connected to RAID

freeskier93

Reputable
Dec 2, 2014
159
0
4,710
I'm trying to set up a RAID 1 array but having issues getting an existing Windows 7 installation to start up on the RAID controller. It's the Windows catch 22 with an existing installation and installing drivers, however different because the drivers SHOULD be installed but still getting no boot device.

I'm trying to set up the RAID with a Gigabyte F2A88X-D3H, so far that has been the easy part. I have an existing Windows 7 installation on a 250 GB SSD, really don't want to start fresh. The mobo has 8 SATA ports, with the ability to configure 0-3 as RAID/AHCI/IDE and the ability to configure 4-7 as IDE or "same as 0-3".

What I did was connect the two drive to be RAIDed to port 0 and 1 and the SSD to port 4, then turned on RAID for 0-3 and IDE for 4-7. I booted into RAID BIOS and set up the array, easy. Continued to boot and Windows 7 booted up. Went and got the AMD chipset drivers (which include RAID drivers) and installed them. Went to disk manager and the RAID array shows up, formatted it, and assigned a drive letter. In this set up everything works perfectly.

The issue is when I move the SSD to SATA port 2 on the RAID controller it won't boot, I just get no boot devices found. Not sure if there are additional drivers I need to install? Gigabyte has drivers that would normally be installed upon Windows installation, but I assume these are the same AMD drivers that I already installed.
 
Solution


Yes, I am aware of that issue because of drivers. Stupid Windows won't let you install RAID drivers unless RAID is enabled but can't boot on RAID without the drivers, so you have to do a fresh install and install the drivers then. I was able to get around that because my motherboard allows both RAID and IDE on certain ports. With RAID enabled I was able to boot on an IDE port then install the drivers on my existing Windows installation.

I figured it out, was and issue with the array orders. The bootable array HAS to be first, so once I swapped the order in RAID BIOS it booted right up. It's always the simple things...

freeskier93

Reputable
Dec 2, 2014
159
0
4,710


I've verified in RAID BIOS that the SSD is non-RAID. I've also verified that the Gigabyte drivers are exactly the same as what's already installed. The only thing I can think is the drivers aren't set to load on boot so I'm currently going through Windows registry to see if I can find the RAID drivers and make sure they are set correctly.
 
"What I did was connect the two drive to be RAIDed to port 0 and 1 and the SSD to port 4, then turned on RAID for 0-3 and IDE for 4-7."
No, connect the SSD to port 2
"I booted into RAID BIOS and set up the array, easy"
SSD remains non-RAID
"The issue is when I move the SSD to SATA port 2 on the RAID controller it won't boot, I just get no boot devices found"
No need to move it, it's already connected to port 2
 

freeskier93

Reputable
Dec 2, 2014
159
0
4,710


Yes, that's when the problem occurs. Connect the SSD to port 2 and set up as non-RAID but get no bootable devices found.
 

freeskier93

Reputable
Dec 2, 2014
159
0
4,710


Yes, I am aware of that issue because of drivers. Stupid Windows won't let you install RAID drivers unless RAID is enabled but can't boot on RAID without the drivers, so you have to do a fresh install and install the drivers then. I was able to get around that because my motherboard allows both RAID and IDE on certain ports. With RAID enabled I was able to boot on an IDE port then install the drivers on my existing Windows installation.

I figured it out, was and issue with the array orders. The bootable array HAS to be first, so once I swapped the order in RAID BIOS it booted right up. It's always the simple things...
 
Solution