Ok - Thought I had tried those as well... will give it another go and double check all the files.

Thanks,
Steve.

@Steve & Fernando,

I think I see two issues here. One is that for surer those are not all the Hardware IDs. There are 3 beginning with "Array" that are the key to this; those need to be added to your integrated driver as well Fernando. I'll post the key missing ones tonight when I get back to my system.

The other issue is that Steve you're not updating the right driver in the registry. There are 4 parts to the RAID Config - the RAID Bus Controller, which uses nvraid.sys, the "Devices" aka members aka HDDs, that also use nvraid.sys, the SATA Controller for the HDDs (nvstor.sys), and then the actual volume presented to Windows, which is just a standard Disk (disk.sys). The only ones with the issue (and for which the hardware IDs apply) are the "Devices" as Fernando mentions. They are usually listed under SCSI key as well, but I've seen instances where they are actually listed under "IDE" (since they are physical drives). It is precisely these devices that nvidia marks as Hidden so they will never show up in DM unless "Show Hidden Devices" is enabled. The names of the devices are "nVIDIA nFORCE RAID Device".

Hello again,

Please see attached screenshot of Reg & DM; I think this sums this all up pretty well. I compared this to my Windows7 install, and for sure the "Array*" entries are the ones required. Somehow, and I don't think any of us are sure of the ordering of this, the Win10 update (& Anniversary Edition) either deleted these values from the .INF (& therefore registry on the initial reboot), or the updated hardware detection routine changed by the AU is now <looking for> the Array* pre-pended to the actual Hardware ID, when it wasn't doing so before. Either way it once again requires the "Array*" to be there or it won't find the device. I did some research on SCSI device IDs, and the "Array*" name pre-pending is <NOT> actually stored and reported from the Hardware itself as the Device ID hard-coded in the firmware....it is <added> by the SCSI standard (software) at some later stage to identify the type of SCSI device (there is also "Processor*", "cdrom*", "disk*", "Enclosure*", etc.) The "real" SCSI ID is just the part <after> the "Array*". But to the Windows kernel, it doesn't really care and just treats the whole thing beginning with Array* as just another Device ID that it has to match <in full.>

The screenshot shows nicely the 4 components and how they relate to each other. On the physical side you have the SATA controller and the two "devices" aka HDDs (you'll maybe have more of these depending on how your array is physically implemented but you'll always have at least 2.) On the logical side you have the RAID bus controller and the RAID volume ("disk") itself. Looking at the Properties of the "Device", you can see the Hardware IDs listed. One of the ones in the list, I am 100% positive, is the one that makes this work, and I'm 99% positive that it's the first one in the list. In the Registry I've opened the ENUM key which is where these Hardware IDs are stored. I actually don't think that changing the .INF or the DeviceIDs key really mattered, but I wanted to be sure and update everything I could to be safe. The one thing that <must> happen is that these Hardware IDs must be added to the HardwareID under the ENUM key for the proper devices as shown, <not> on the disk device that's below, and <not> on the RAID Bus Controller (which is in ACPI key), and <not> on the SATA Controller (in the PCI key).

I hope this helps just a bit more,

Steve please let us know how it goes,

Justin

Zitat von ENAJonas im Beitrag #199

---

The screenshot shows nicely the 4 components and how they relate to each other. On the physical side you have the SATA controller and the two "devices" aka HDDs (you'll maybe have more of these depending on how your array is physically implemented but you'll always have at least 2.) On the logical side you have the RAID bus controller and the RAID volume ("disk") itself.

---

SCSI\Array__NVIDIA_______Raid_Disk____
SCSI\Array__NVIDIA_______Raid_Disk
SCSI\Array__NVIDIA
SCSI\__NVIDIA_______Raid_Disk_
__NVIDIA_______Raid_Disk_
ScsiArray
 

But note that I actually only have one device, because my RAID is setup as a single drive JBOD, in order to use AHCI features, and not RAID features. I'm going through permutations to try, and was going to start with the v9.99 as that is what my current reverted install is on.
@Fernando, I notice that the v9.99 drivers using, do not have all of those IDs, but the latest v11.1 .inf do have them all. I checked the v9.99 latest (8/24) and previous (8/19); neither have them all. I was thinking to check those registry settings after the August Cumulative Update first reboot, to see if ENAJonas' changes might work after the 2nd reboot...

Also, have you guys seen this:
https://blogs.msdn.microsoft.com/windows...0-version-1607/

Hello, everyone.
I just want to share my experiences on Windows 10 1607 clean installation with nForce RAID Arrays (Success!).

My System.
Nvidia nForce 630a with RAID 0 (2 SATA HDD.).
Modified Nvidia nForce sataraid driver version 11.1.0.43 (nvstor.sys on Microsoft driver version 10.6.0.23 often freeze system during boot on old my Windows 10 1511).
Windows 10 Enterprise 2016 LTSB.

Preparing Step.
Modify Windows 10 Enterprise 2016 LTSB image with NTLite both install.wim and boot.wim (only Windows ... Setup, except Windows PE...).

%NVRAID_DESC%=nvraid,SCSI\__NVIDIA_______Raid_Disk_
%NVRAID_DESC%=nvraid,__NVIDIA_______Raid_Disk_
 

%NVRAID_DESC%=nvraid,SCSI\__NVIDIA_______Raid_Disk
 

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\SCSI\Array&Ven_NVIDIA&Prod_Raid_Disk\xxxxxxxxxx
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\SCSI\Array&Ven_NVIDIA&Prod_Raid_Disk\yyyyyyyyyy
 

HKEY_LOCAL_MACHINE\TEMP\ControlSet001\Enum\SCSI\Array&Ven_NVIDIA&Prod_Raid_Disk\xxxxxxxxxx
HKEY_LOCAL_MACHINE\TEMP\ControlSet001\Enum\SCSI\Array&Ven_NVIDIA&Prod_Raid_Disk\yyyyyyyyyy
 

ClassGUID
DeviceDesc
Driver
Mfg
Service
 

Hi Fernando,

Thanks for supplying image and sorry I didn't get back sooner - I was working away since Monday.

I have just tried the image you provided but unfortunately results are exactly the same. No drives are displayed to be selected for the Installation.

Thanks,
Steve.

Zitat von aokake im Beitrag #202

---

I just want to share my experiences on Windows 10 1607 clean installation with nForce RAID Arrays (Success!).

My System.
Nvidia nForce 630a with RAID 0 (2 SATA HDD.).
Modified Nvidia nForce sataraid driver version 11.1.0.43 (nvstor.sys on Microsoft driver version 10.6.0.23 often freeze system during boot on old my Windows 10 1511).
Windows 10 Enterprise 2016 LTSB.

---

Zitat von jwhickman im Beitrag #210

---

@aokake:
To clarify, you are saying that your Windows boot installation is on your RAID 0 array, then? Thanks for these details!

---

1. Boot with modified Windows 10 USB boot disk.
2. Now, I can installing Windows normally because Windows Setup detected RAID Arrays disk that come from modified driver in USB boot disk.
   • Windows Setup can copy any Windows setup files to RAID Arrays disk then it will reboot my PC.
3. Before PC boot up I change boot order to boot from RAID Arrays disk first in BIOS, now Windows Setup continue installing from RAID Arrays disk (Getting devices ready ...% screen).
   • After Windows Setup running 100% it will reboot PC again. (Now Windows on RAID Arrays disk use scsidev.inf driver that not work, therefore I fix this on step 4.)
4. Before PC boot up I change boot order to boot from Windows USB boot disk first for modify driver on RAID Arrays disk to use modified sataraid driver v.11.1.0.43 by compare keys and values from two systems registry.
   • System 1 HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\SCSI\Array&Ven_NVIDIA&Prod_Raid_Disk\xxxxxxxxxx (this registry on Windows Setup RAM disk from USB boot disk).
   • System 2 (load hive from ?:/Windows/System32/config/SYSTEM by set TEMP key name) HKEY_LOCAL_MACHINE\TEMP\ControlSet001\Enum\SCSI\Array&Ven_NVIDIA&Prod_Raid_Disk\xxxxxxxxxx (this registry on RAID Arrays disk).
   • After modified System 2 registry and unload hive, I can reboot PC to boot Windows on RAID Arrays disk.

Zitat von aokake im Beitrag #211

---

Zitat von jwhickman im Beitrag #210

---

Zitat von aokake im Beitrag #202

---

I just want to share my experiences on Windows 10 1607 clean installation with nForce RAID Arrays (Success!).

---

To clarify, you are saying that your Windows boot installation is on your RAID 0 array, then? Thanks for these details!

---

Sorry, I don't understand your question but I'll show my summarize installation below...

---