Hi all, and probably for the last time,
The analysis I promised won’t be possible, since after the next Cumulative Update (Sept.) was installed, I had no subsequent issues with my array. No drivers or INFs were overwritten.
Anyone who still has issues with the INACCESSIBLE_BOOT_DEVICE on a boot array, please PM me - I’m convinced I can get it working.
Thx to all,
Justin
@ENAJonas :
Hello Justin,
It is great, that you obviously found a final and easy way to solve the INACCESSABLE BOOT_DEVICE problem even for nForce users, whose system drive is on the RAID array, but why don’t you publish your solution guide into this thread?
Do you really want to solve the user’s problems individually via PM and let the testers continue wasting their time? Why do you want to leave this Forum at this point of our investigations?
Please share your knowledge with us!
Thanks for all your efforts!
Dieter (alias Fernando)
Hi Justin,
Please share your results and the process you used to get this working. Did you have your Raid array as a bootable OS?
I was able to get fernando’s drivers working BUT only after implementing them after booting to a non raid SSD. Once I had applied the Win-RAID CA and changed the drivers (show hidden devices etc…) I was able to see my Raid array but only as an additional extra drive. I have NOT been able to use the device or set it as a bootable raid device.
I’ve been looking at this for over a week now and getting tired. If you have any information to share that would be great for everybody on this forum 
I am currently going through the list of activities that Fernando requested. I should have the results later today.
Much Appreciated.
K
Hi,
Please find attached test results as per requirements from Fernando. I hope they make sense.
Kind Regards,
Kenny
Win10 Tests using Fernando Drivers and Removal of scsidev.inf.docx (605 KB)
The results!!!
Trying to install booting the CD win10 pro 64bits latín.
…this no detecte tehe array, neither driver can be loaded, only the WHQL can be loaded buthi this don show the array 0.
The results!!!
Trying to install/update the versión win10pro 64bits latín inside Windows after install Fernando drivers the install is loaded but in the reebot show a recoger screen, in this only can be selected startup advanced options/off/etc etc.
But in the next reebot loging in Windows, show this screen.
@kingkenny :
Thank you very much for your detailed and perfectly documented tests.
Although I hadn’t yet the required time to to have a deeper look into your test results, they seem to be not very promising and partly do not match the reports I have gotten from other testers.
Here are 2 remarks/questions from my side:
- It is a pity, that you were not able to remove the scsidev.inf file from the BOOT.WIM and INSTALL.WIM by using NTLite.
Which NTLite version did you use and where did you get it? As I had already written >here<, our Forum member nuhi had compiled especially for the current nForce RAID issue tests a special NTLite version with enhanced options to remove in-box storage “drivers” like the file scsidev.inf from the Win10 image. This special NTLite version can be found within >this< folder of my OneDive account. - What was the reason why you hadn’t unplugged all disk drives except the RAID array members before you started the OS installation tests? That is what I always recommend to do, if you want the best chances to get an OS and the boot sector installed onto a RAID array.
@Holocausto :
Thanks for your tests as well!
@all:
After having seen these test results I do not really know how to proceed.
Please post your ideas into this thread.
Hi, the temporaly solution is obtain a older CD installation windows 10 & use the Latest nforce drivers by fernanado. This do to work your computer but whitin the las compilation update (1607)
EDIT by Fernando: Unneeded part of the fully quoted post removed (to save space)
Hi, Fernando my next TEST will be Edit/erease/remplace a file from Win10.iso (ver10.0) to Win10.iso (ver1607) .
But my cuestion is, wich files/folder have to be modified in the Win10.is (MOD)???|addpics|at2-1-67b2.png|/addpics|
EDIT by Fernando: Unneeded fully quoted post removed (to save space)
That will not work.
All the Setup informations and data are extremely compressed within the 2 files named BOOT.WIM and INSTALL.WIM. These 2 files are within the folder named "sources", but it is impossible to edit/erase/replace them or parts of them.
Hi,
1. I just downloaded it from the web site - https://www.ntlite.com/ which is before I read about the special edition by Nuhi.
I did download the NTLite v1.2.0.4247 Beta Special from Nuhi but after extraction and running the exe I got an error Integrity check failed for file Tools\7-zip\x64z\7z.dll so though best just to use the one I had downloaded.
I’ll try some of the tests again later using the beta special and see if it actually allows me to rename or delete the files from the loaded and explored image and boot wims.
2. Being as I had noticed before… that it had either seen the RAID array or the non-raid SSD - but not BOTH. I wanted to be sure that what ever fix we found actually identified BOTH type of disks. I would have been really unhappy to find a solution that picked up the RAID array… to then only re-attach my normal SSD and it wasn’t seen. lol.
Damn shame we all getting different results. Has anybody actually got it working and installed a OS on it. ?
Installing the latest Win 10_1607 on a standard SSD and then installing either of your driver sets (I used the new v11.1.0.43 x64 ) and doing the show hidden devices etc works to see the array. It even appears in the Nvidia Strorage panel - but this doesn’t help anybody who wishes to use the the RAID array as a bootable OS.
Ohhh noooo I may have to go back to Windows 7! - which isnt such a bad thing.
@Fernando ; The latest ISO I got from you, allowed me to select my raid drive and install, but was not able to boot without a INACCESSIBLE_BOOT_DRIVE message. The original install is gone now of course (I was aware it was likely, and was fine with it), so am willing to try anything for testing. I will note that I could never get the iso to boot from DVD nor USB, but pxe worked.
@jwhickman :
Thank you very much for your additional report, which gives me new hopes, and thanks for your willingness to do some additional tests.
By the way: I will prepare and upload today a Win10 x64 EN-US ISO, where I had removed the "bad driver" scsidev.inf by using NTLite.
The safest and simpliest way is to insert a proper working USB 2.0 Flash Drive, to run the tool named Rufus, navigate to the ISO file and choose the option "LEGACY mode Partition Table (MBR)". The rest will be done automaticly by Rufus.
Good luck!
Btw the integrity check just means that there is no Tools\7-zip\x64\7z.dll file.
Extract the whole package instead, or if there is only exe inside, then use existing NTLite installation and just place the newer exe in it.
New official version with that and other changes will be out tomorrow if testing passes.
Thanks for the Update Nuhi…
@all interested nForce users with a bootable RAID array:
Today I have created a freshly modded Win10 x64 Pro EN-US ISO file by using the special NTLite v1.2.0.4247 Beta, which had been compiled and delivered by nuhi for nForce RAID testers (it worked flawlessly!).
This is what I have customized:
- removed: Win10 in-box scsidev.inf v10.0.14393.0 dated 06/21/2016
- inserted: scsidev.inf v10.0.14393.0 dated 06/21/2016 mod+signed by me today (09/25/2016)
All I have done was the addition of a *.CAT file entry and the removal of the following lines:- %GenericScsiArray% = NODRV, ScsiArray
- GenericScsiArray = "Generic SCSI Array Device"
Notes:
- For the clean install of Win10 x64 Pro it is recommended to use a proper bootable USB Flash Drive image, which had been been created by the tool Rufus and designed for a LEGACY mode (MBR) installation.
- Before you start with the OS installation, all storage drives except the members of the nForce RAID array should be unplugged.
If this customized ISO file should work for a clean installation of Win10 v1607 onto an nForce RAID array, you can install any of my mod+signed nForce SATARAID drivers.
EDIT by Fernando: The link and the related file have been removed by me (to avoid any problem with Microsoft).
Ahhh great
Looking forward to testing this. Is it possible (once we have confirmation that it works) that we can have a separate upload of your modified scsidev.inf. May come in handy as a manual backup in case we need to re-mod any further windows images.
Did you replace all instances of the file or just the one in \windows\inf. I assume the modified scsidef.inf driver needs to replace the original in both INSTALL and BOOT WIMS.
Kind Regards,
Kenny
Yes, for sure.
Exactly this is what I have done.
Hi all again,
Didn’t think I’d get attacked for just reporting my progress…
@Fernando & all, I reported everything I did to fix the problem more than 2 weeks ago, please check that post. It is very detailed & contains exactly everything I did to fix it.
I do not have experience with Windows installs & NTLITE and therefore can’t assist in that area. I can however tell you what Windows expects in the Registry on boot of a nvraid system, which I have done. Fernando you have disputed throughout this thread that the missing prefix “Array__” cannot be the solution; however clearly it helped me in my case so perhaps you may have been mistaken on that.
Again, I’m here to help but again, I don’t have experience with driver signing, NTLITE, or Windows install process. If you sign a driver with an INF with <all> of the hardware IDs we’ve talked about (there can never be too many), the only reason that shouldn’t work is because there’s something still wrong with the Signing I would think (though can’t be sure.).
In general, I think we should stop trying to figure out how to get a completely fresh install working, and take this path: install the base 1511 version, which is fine, then upgrade to Anniversary VIA Windows Update. If you then get the BSOD, take my steps to edit the registry & make it work again.
Just my 2 cents,
Justin
Nobody attacked you. I just wondered about your last post, where you let us know, that you stopped your tests and your participation on our discussion, but offered personal support via PM for nForce RAID users, who need help. If I should have misunderstood you, I beg your pardon.
Thanks for your guide, which obviously worked for you and will still be an option for affected nForce RAID users.
Nevertheless we are trying to find a solution, which avoids a modification of the regsitry (which is always risky) and may be usable even for a clean install of the latest Win10 version.