Changed to RAID 10 - Boot Device Inacessible

AndroidDan

Reputable
Mar 20, 2015
20
0
4,520
HI guys, Apologies if this has been answered elsewhere, i couldn't find an answer.
I recently added 4x500GB drives to my system. I already have a 840 pro 256GB SSD for my OS which works perfectly & a 3TB WD black for data storage. My mobo is Z97M-plus
I wanted to make the four 500's into a raid 10 setup just for some storage of some bulky files.
The problem i have is that when i configure the raid in the BIOS & then reboot (Windows 10 pro) i get the boot device inaccessible.
Any suggestions to keep the SSD bootable without reinstalling the OS? There is a crap load of programs & games installed id rather not go through the process of reinstalling everything if i can avoid it
 
Followed the Windows 8 part of that guide for Win 10. Worked a treat. Raid 10 now up and running & SSD still bootable. Only issue now is that it takes longer to boot because of the raid configuration utility that comes up on boot.
 
Yea that will happen. Addin Raid cards can take MUCH longer. I have clients who get high end Dell servers with MD Vaults, each being able to hole 12 3.5 inch drives or 24 2.5 inch drives. They always get 3.5 though. but one server had two of those in one big RAID 6. yea 100TB or usable space and the server took almost 4 Minutes or so to boot just the RAID lol so feel good! haha
 
So if i want my system to boot faster like it did before ill have to disable the raid setup? My SSD is not part of the RAID configuration at all. I tried to disable the Intel rapid storage in the BIOS & it wanted to change the SATA controller back to AHCI.
 
Yea the RAID controller, no matter if it is onboard or addin, had to startup and make sure the RAID is running properly BEFORE anything boots up. So if you want it to be fast again then you can't run RAID on that PC at all UNLESS you do a software RAID which does tax the CPU.
 

TRENDING THREADS