SSD Shown in Bios and not in Windows 2016 install.

sYndax

n00b
Joined
Nov 3, 2013
Messages
53
Hey,

I'm trying to install Windows Server 2016 on an Corsair Force 3 180GB ssd on
Asrock Rack E3C224D4I-14S mobo.

The SSD is recognized in Bios however when i boot off the DOK to install
windows, it asks me for a "driver" and does not find the SSD.

If i enter command prompt the SSD is show in Diskpart.

I tried clearing it, deleting partitions and reset attributes but with no effect.

I also tried download the chipset driver for windows 10 (intel c224) directed the installer
to the INF, but it wont work... i get the same msg...

the SSD is the single drive connected...

Can ne1 help me?
 
Not sure what "boot off the DOK" means but couple items i've had to set with most of the Windows Server installs i've done is within BIOS:
1) Boot menu -> turn off all boot drives except for the SSD
2) Boot Order -> should only show the SSD but if not, set it to the SSD as the 1st and only drive

If the SSD is plugged into 1 of the sata ports, it should see it. Are you installing the OS from a USB drive or a disk?
 
Not sure what "boot off the DOK" means but couple items i've had to set with most of the Windows Server installs i've done is within BIOS:
1) Boot menu -> turn off all boot drives except for the SSD
2) Boot Order -> should only show the SSD but if not, set it to the SSD as the 1st and only drive

If the SSD is plugged into 1 of the sata ports, it should see it. Are you installing the OS from a USB drive or a disk?
I'm booting the installation from a disk on key. The SSD is the only device. The bios sees it, windows installer does not. If i enter command prompt within the installation Diskpart sees it.

The bios recognizes it as drive #5 because the first 4 drives can be connected only via sff cable as its a server board. This drive is connected to the additional sata ports on the same c224 intel controller.

Trying to point the setup to an c224 inf just in case windows cant see the controller yields nothing. After selecting the driver it rescans for drives and comes up with none.
 
Your def thinking right on the troubleshooting. My guess would be a driver which seems like you are head deep in that already. I've had some similar issues before but not onboard disk, usually with a raid card and not having the correct drivers.
 
Your def thinking right on the troubleshooting. My guess would be a driver which seems like you are head deep in that already. I've had some similar issues before but not onboard disk, usually with a raid card and not having the correct drivers.

The system has a raid card, however the OS and Raid is yet to be configured. I just can't seem to move further than the install screen.
 
Onboard. The board has 2 controllers.

2 SAS ports on Lsi controller and additional c224 intel controller with 2 sata and 1 sas port.
 
When i point the installer to the win10 drivers, it shows the controller, scans and comes out empty. And again the drive is clearly visible on both bios and diskpart.
 
looks like the other driver I mention is software and probably wont let you pull an INF file from it.
 
since this is a server board, does that controller have options during post to let you go into it similar to the raid controller?
 
This might even be the one i tried. Its a generic c200 driver... It shows the controller in the setup, but nothing more...
 
since this is a server board, does that controller have options during post to let you go into it similar to the raid controller?
Onboard controller? Not that I'm aware of. The lsi is both flashed to IT mode and disabled in Bios.

I can access the pcie raid bios but its not related...
 
I have had this issue before when installing on my son's rig, and it turned out to be a bad install on the USB drive we were installing from. Simply running the MS install creator thingy fixed the issue for some reason.
 
I have had this issue before when installing on my son's rig, and it turned out to be a bad install on the USB drive we were installing from. Simply running the MS install creator thingy fixed the issue for some reason.

I've created the drive using rufus. I'll try using the MS app.
 
I have had this issue before when installing on my son's rig, and it turned out to be a bad install on the USB drive we were installing from. Simply running the MS install creator thingy fixed the issue for some reason.

That worked.

I had to tinker a bit in the bios due to EFI/Legacy issues within the installation, but re-doing the boot disk definitely worked!
 
Awesome, and glad it worked out. I have tried to load the drivers, but it would have given the same error. I don't know the deal but something gets corrupted in the installation files, and it happens over time as well.
 
Another question, after i finish configuring my server is there a way to save all the settings so when i reinstall o don't have to go thru it again?
 
Back
Top