Most other versions can be found in the inf already so there are only 2 drives, that is 3 lines to add(for the 3.2TB one, COMMNvme3200GBPM1725SFFGen.DeviceDesc = "NVMe PM1725 3.2TB Controller" this line is already there so only adding the first line will make it work)
Is this PM1725A? I’ve tested 800 1600 1800 3200GB, dell oracle and original es versions of PM1725, but only tried 1 PM1725A once. Which oem version is this?
@111alan : @test0rn : Attached is a test version of the 64bit Samsung NVMe driver v1.4.7.6, which has been mod+signed by me today. Don’t forget to import the Win-RAID CA Certificate, before you try to install the driver. Please give us your feedback regarding the results
Thank you for the driver @Fernando Unfortunately it did not work. The installation itself went fine the driver updated successfully and asked for a restart. After that the device cannot start (Device PCI\VEN_144D&DEV_A822&SUBSYS_A814144D&REV_01\C2480071EA38250000 had a problem starting.) but a driver rollback went flawless.
@test0rn : Thanks for your report. It is a pity, that it didn’t work. I suspect, that either the specific rather new NVMe Controller is natively not supported by the old NVMe driver or I have entered a not correct Device description (“3200GBPM1725AHHHL”) into the INF file. Questions: 1. Which OS are you running? 2. Which NVMe driver does your on-board Samsung NVMe Controller currently use? To find out the reason for your installation error message, please do the following: 1. Run the Device Manager, expand the section “Storage Controllers” and right-click onto the listed Samsung NVMe Controller (the exact name doesn’t matter). 2. Choose the Options “Properties” > “Details” > "Property" 3. Look into the various drop-down menue options for an entry like “3200GBPM1725AHHHL”. Do you find any similar entries? If yes, which ones?
The OS is Server 2016 and NVME is using the standard windows driver. There is no entry like “3200GBPM1725AHHHL” to be found but that’s probably due the driver rollback?
@111alan : @test0rn : Attached are the 64bit Samsung NVMe drivers v1.4.7.6 and v2.0.8.1611, which have been mod+signed by me today (the v1.4.7.6 INF file is identical with the one I had attached yesterday, I just have removed an unneeded entry regarding the 32bit support). Please test them both and give us your feedback. Good luck!
The 2.0.8.1161works very well, at least not encountered any problems yet. Regarding the 1.4.7.6, I suggest to copy all hwids except those with “PM1725A”(DEV_A822) from 2.0.8.1161 to the 1.4.7.6’s inf, because I just ran into a bizzare “SM1715a” drive from dell that there’s no corresponding hwid in 1.4.7.6, but worked flawlessly when I manually selected SM1715 model.
Also delete the"PCI\VEN_144D&DEV_A822&SUBSYS_A814144D" you just added from 1.4.7.6 because PM1725As are not supported. And don’t forget that “UBX” controller which is unique to 1.4.7.6
@111alan : Thank you very much for your report and for your recommendations regarding the v1.4.7.6 driver. Attached is the 64bit Samsung NVMe driver v1.4.7.6, which has been mod+signed by me today according to your recommendation. Good luck!
The v2.0.8.1611 has been tested meanwhile by me as advertised. It installed flawlessly, but then after reboot it wasn’t able to initialize the drives properly. See screen. I am out of ideas now…
I had to roll back the driver to the lame MS Standard NVM Express Controller which completely sucks under WS2016 and StorageSpacesDirect…
@test0rn : It is a pity, that the mod+signed Samsung NVMe driver v2.0.8.1611 didn’t work with your system. Maybe @111alan can help to find a solution for you.
What firmware is this drive using? It’s possible that it has an old or es firmware that has problems communicating with the driver.
I’ve modded 2 previous versions of drivers(A06 A07). Pls try them both and if one of them works pls tell me which one Also I can’t make signatures for a driver so disable driver signature enforcement before you install. Also update the firmware if you can, there are at least 2 urgent firmware updates for PM1725A at this point, which may save the drive from bricking when unexpected power loss happens https://mega.nz/#!O5kXWQSR!KWmVGiXXdXV6Q…YY-KZ3VJOP6gf1g
@Fernando I found an old A06 version for 32bit win I saved earlier, and found that the content of the actual driver is exactly the same as 64bit ver. I think those Samsung drivers support both 32bit and 64bit systems, so you don’t need to delete those 32bit entries at all
