@ppmodarksage :
Welcome at Win-RAID Forum!
To avoid this issue, you have to hit the "Compatibility" button from the NTLite Taskbar.
Regards
Dieter (alias Fernando)
@ppmodarksage :
Welcome at Win-RAID Forum!
To avoid this issue, you have to hit the "Compatibility" button from the NTLite Taskbar.
Regards
Dieter (alias Fernando)
At this point it seems the best solution is to use the Windows creator’s update, it’s due in 4 days (April 11th) and presumably will have the same drivers as the preview of the same build that works on nForce. It’s also easy to sign up for the insider preview that already works. I’m a little concerned that this information will be buried by new posts, especially as there’s now so much technical info to read through.
I totally agree with you.
What we currently not know is, whether a clean install of the "Creator’s Update" onto an nForce RAID array will work. I just have compared the content of the scsidev.inf files v10.0.14393.0 (v1607) and v10.0.15063 (v1703). Both are dated 06/21/2006 and their content is identical.
So it seems to me, that problems are foreseeable.
The 1703 preview worked for a clean install. Admittedly this removed a previous installation.
Greetings everyone!
I am trying to install the 11.1.0.43 driver for the "NVIDIA nForce RAID Device". The current device is the stock. 10.6.0.24 from 1/6/2017. The inf file will not install. It says that it does not contain files that apply to my hardware.
I took a look at the windows file that is being used, nvraid.inf and compared it to the file that you provided, Fernando.
I see that there is a device string missing that windows has included. %NVRAID_DESC%=nvraid,SCSI_NVIDIA____Raid_Disk_20 AND %NVRAID_DESC%=nvraid,SCSI_NVIDIA_______Raid_Disk (see the trailing underscores!)
----Windows nvraid.inf----
%NVRAID_DESC%=nvraid,SCSI\NVIDIA__Raid_Disk________
%NVRAID_DESC%=nvraid,SCSI_NVIDIA_______Raid_Disk
%NVRAID_DESC%=nvraid,SCSI_NVIDIA_______Raid_Disk
%NVRAID_DESC%=nvraid,SCSI\NVIDIA__Raid_Disk_20____
%NVRAID_DESC%=nvraid,SCSI_NVIDIA____Raid_Disk_20
%NVRAID_DESC%=nvraid,SCSI_NVIDIA____Raid_Disk_20
%NVRAID_BUS_DESC%=nvraidbus,*NVRAIDBUS
%NVRAID_BUS_DESC%=nvraidbus,*NVRAIDBUS
%NVRAID_BUS_DESC%=nvraidbus,NVRAID20
----Your 11.1.0.43 nvrd64.inf ----
%NVRAID_DESC%=nvraid,SCSI\NVIDIA__Raid_Disk______
%NVRAID_DESC%=nvraid,SCSI_NVIDIA_______Raid_Disk
%NVRAID_DESC%=nvraid,SCSI\NVIDIA__Raid_Disk_20____
%NVRAID_DESC%=nvraid,SCSI__NVIDIA____Raid_Disk_20
%NVRAID_BUS_DESC%=nvraidbus,_NVRAIDBUS
%NVRAID_BUS_DESC%=nvraidbus,*NVRAIDBUS
%NVRAID_BUS_DESC%=nvraidbus,*NVRAID20
Including these into the inf file works, but then of course I break the signature. Can you include these and resign please? Thanks!
Nebarnix
PS: To be clear, the stock drivers let me see and use my RAID array, but the storage section is not there in the NVidia control panel, so there is no way to manage them! I suppose we need the relevant version of the raid tool maybe?
@Nebarnix :
Welcome at Win-RAID Forum and thanks for your informations, which are obviously very important for all nForce RAID users, who are going to install Win10 v1703 ("Creator’s Update") onto their RAID array.
Yes, I will present tomorrow refreshed mod+signed 32/64bit NVIDIA nForce SATARAID drivers v11.1.0.43, whose INF file has been customized by me according to your proposal.
Regards
Dieter (alias Fernando)
Ausgezeichnet! =D
@Nebarnix :
After having done a deeper look into the INF files of the NVIDIA nForce SATARAID drivers v11.1.0.43, which have already been modfied and signed by me, I think, that your demanded driver already exists.
Please try the driver named "64bit nForce SATARAID drivers v11.1.0.43 for mod scsidev mod+signed by Fernando", which I am offering >here< since September 2016.
This is the related part of the nvrd64.inf:
Which RaidTool version did you use? The original RaidTool v11.1.0.43, which is within my "Latest nForce Driverpacks for Win7-10", should work with my mod+signed driver variants as well.
@all:
Since my guide, which currently can be found >here< has been written for nForce RAID users, who want to do a clean install of Win10 v1607 (= "Anniversary Update") and I don’t know, whether it is still valid for a clean install of Win10 v1703 (= "Creator’s Update"), I need your feedback.
As soon as we know the exact procedure and the required nForce drivers, I will customize the related guide and either start a new thread with the up-to-date guide as start post or customize this already existing thread and give it a new thead title.
Thanks in advance for your reports!
This driver worked!! Now I can see my arrays, AND manage them with the raidtools package from 11.1.0.43!!! This is great! =D
Hey guys,
I have a question, I have an Asus M3N78 PRO motherboard, I created a RAID5 array with 4 disks, set it to bootable, its MediaShield ROM BIOS 10.0.0.31 RPT IDP.
I then proceed to boot Windows Server 2016 Standard, and it doesn’t see my disk, no problem that’s normal, I just need to load the RAID drivers right? I load the original from Asus website, it recognizes the drivers and loads it but after it’s still not showing my disks, I Google and find this forum, tried every link with diferente drivers, all load the inf files as compatible, it loads, but still doens’t see my disks.
What can I do to solve this? As Windows server 2016 is based on W10.
@DGP_Maluco :
Welcome at Win-RAID Forum!
Questions:
Which nForce chipset or MCP number has your ASUS M3N78 (GeForce 8300 is a graphics chip)?
Which driver version and which driver subfolder did you load while trying to get the OS installed onto your RAID array?
Regards
Dieter (alias Fernando)
How can I check? On the motherboard I got no specific reference, neither on the manual, or the asus description page. None on the BIOS.
Thanks
EDIT: I tried from the first topic:
1. "NForce4 WHQL Driverpacks for Vista/Win7"
1. "Latest nForce Driverpacks for Win7-10"
2. "Special nForce RAID Driverpacks for Win7-10"
3. "Special nForce2-4 LEGACY Driverpacks for Win7-10"
Inside the IDE folder, Win764, sataraid
Or IDE, sataraid
They show up, compatible with the hardware, it loads but then nothing it doesn’t see the RAID.
If you should have a running Windows OS within your current system, run the Device Manager, expand the section "Storage Controllers" (or - depending on the OS - "SCSI and RAID Controllers"). Then do a right click onto the listed NVIDIA nForce RAID Controller and choose the options "Properties" > "Details" > "Property" > "HardwareIDs".
The only interesting part is the DeviceID shown as "DEV_XXXX".
If you should not be able to run any OS on the machine, I recommend to try the OS installation again and - if it is a 64bit OS - to load the attached 64bit driver (the *.rar archive has to be unzipped before). If you want to install a 32bit OS, let me know it and I will attach the 32bit variant of the driver.
Good luck!
sataraid.rar (381 KB)
nVidia advertised some chipsets with integrated graphics directly with the model number of the graphics core.
All information taken from wikipedia:
- nForce 400 / GeForce 6000
- nForce 600 / GeForce 7000
- nForce 700 / GeForce 8000
So the chipset "GeForce 8300" is a MCP78 with GeForce 8300 graphics core.
Fernando, ALL Microsoft drivers are dated 06/21/2006 in case a driver update occures the newer driver of the manufacturer is installed.
If Microsoft would push their own driver dates, Windows Update and the driver installer routines would always pick the Microsoft drivers in case of a Windows Update/Upgrade and not the manufacturer ones.
You should compare the SYS and DLL files.
https://blogs.msdn.microsoft.com/oldnewt…208-00/?p=95395
Hi All,
With regards to the “Win10 Update makes nForce RAID arrays unaccessable” and the special “scsidev.inf” procedure for getting it working on Windows 10 etc… Errrmmmm I was just doing some googling and I found a group who creates updated releases. When I tested quite a recent version - it found my nVidia Array. I was able to format it. It appears to work like it did originally before the “Anniversary Update” issues started
The release in question is "Windows 10 X64 8in1 Build 15063.11 v1703 RS2 ENU APR 2017 {Gen2}"
I’ll do another install to make sure I am 100% correct and report back… but it actually looks like the issue may have been resolved? Unless its the way they build their images. I wonder if MS have incorporated a fix?
Kind Regards,
Kenny
I just ran the Update Assistant tool to upgrade to v1703 and it worked without issue. Crazy. Note: my RAID drive is also my boot drive.
The Device Manager now shows the RAID/SATA devices as:
I don’t need the Windows RAID tool, so I am hopefully good to go, if Sleep/Hibernate still works… :-/
Update: Yup, no issues with sleep and resume.
Hi all,
just to add my experiences with creator’s update: it does NOT work with my pc (NVIDIA Nforce 7 afaik) . Setup exited with an error as when installing 1607 last autumn; and starting from DVD is no option because I want to keep my programs and data. But it’s not the same error than before; this time installation proceeded until “first boot” and didn’t stop in “safe_os” phase. So Zelphium and jwhickman may be right presuming creator’s update solves the old driver problem; however I’ve possibly got an additional specific issue.
volba
EDIT by Fernando: Unneeded fully quoted post removed (to save space)
In post #311 you say
but the OneDrive files only have a 32-bit version shown in the v11.1.0.43 folder of the SataRAID drivers. Is there a 64-bit version or is the one labeled "32-bit" good for either form of installation?
Thanks
@DominosJR :
Welcome at Win-RAID Forumand thanks for your info!
While cleaning my OneDrive folders and their content a few days ago I obviously have deleted by mistake the mod+signed 64bit drivers v11.1.0.43 incl. the related folder. Now everything is available again.
I am sorry for the inconvenience.
Regards
Dieter (alias Fernando)
After announcing Windows 10 prof. Insider Preview Build 16232, actually you can not make a clean install of that Build anymore on the following
Nforce Chipset Mainboards:
Asus Striker 2 Formula
Asus Striker 2 Extreme
Asus Striker 2 NSE
The Computer does not run into the Setup main menu and restarts (reboots) all the time
weather you use a raid array or an ahci drive (does not make a difference)!
And yes… the boot image is okay, because it runs under the XFX Mainboard with Nforce Chipset 780 SLI!
On the following Mainboard it is still possible to make a clean install of Build 16232 or higher (Build 16241)
XFX Mainboard with Nforce 780 SLI Chipset even on raid 0 array drives (modified install.wim and boot.wim with NTLite)…
Tested last Weekend on July the 15th and 16th!
I need a reply if somebody has made the same experience?!?