Windows 10: Can't access disk during boot with newly installed raid disks

I'm using win10 and I'm updating my disks with intel vroc. I can install new system on the raid disk with loading the vroc driver during installation and successfully boot into this new system.


But when I want to use the old system without windows installation with vroc dirver loaded, the windows can't detect the old driver I had, which is not the raid disks. After intel vmd enabled, windows will go into BSOD as INACCESSIBLE_BOOT_DEVICE since it can't detect my nvme ssds. How can I install the driver to the windows so it can detect the disk during booting? Installing the driver when vmd disabled is not functional.

:)

 

Raid setup needs Vista disk to boot

My first Raid setup

P5N32-E SLI
Nvidia Raid Setup through Bios
(2) 74GB Raptors Stripped

Installation of Vista went perfect but wasnt able to load nvidia drivers it kept giving me a blue screen so I used the Vista default(may be where the prob is from)

When I boot the computer without Vista CD in drive it wont boot... says invalid system disk...then I pop the disk in an press enter and it boots fine.....

Is it an issue that the nvidia raid driver werent used during the install

Please help

 

Disk boot failure!!!

You can format the disk with like fdisk or something. A linux disk would make more sense but you say it won`t boot....

 

Disk management console view is not up-to-date

i dont know how to fix your disk management, but i can fix your partition problems...




open up Command Prompt with admin rights. (Right click, run as admin)


enter in
DISKPART
list disk

then find the Disk number for your Raid array... lets call it number 7 ( you can tell what disk is what by the total size)
type in

Select Disk 7
List Partition (will give you a list of all the partitions..)
Select Partition 1 (im assuming you only have 1 partition on Disk 7) repeat this step if you have more partitions.
ASSIGN


that should get the array up and running ready to use.


EDITED.

any problems, post back ^^


Still EDITING *Stick Out Tongue

side question, have you tried restarting the PC?