Smasung 970 Pro NVMe

[Zetanova]

I used sedutil-cli successfuly for many Samsung SSD models under windows.
Few times there where only some bugs with drivers.

But i could never get a Smasung NVMe to work.
It is always listed with no opal support.
I tried the windows nvme driver and all samsung nvme up to 3.2

Is this a sedutil-cli, driver or firmeware issue?

under windows:
sedutil-cli --scan
Scanning for Opal compliant disks
\.\PhysicalDrive0 2 KINGSTON SUV500120G 003056RI
\.\PhysicalDrive1 2 Samsung SSD 860 EVO 1TB RVT02B6Q
\.\PhysicalDrive2 2 Samsung SSD 860 EVO 1TB RVT02B6Q
\.\PhysicalDrive3 No Samsung SSD 970 PRO 512GB 1B2QEXP7
\.\PhysicalDrive4 No Samsung SSD 970 PRO 512GB 1B2QEXP7

A hint would be appreciated.

[oom-is]

This is a fault in DTA official "vanilla" SEDutil which does not formally support NVMe devices under Windows (and unfortunately is lacking updates since 2017). Please feel free to take a look at the precompiled binaries in my fork, or the original lukefor fork from which I sourced the Windows NVMe patch, or ChubbyAnt's fork also derived from @lukefor's code, for binaries that do support NVMe on Windows.

As a first step, you could also take the Linux64 Rescue disk image from here (or the corresponding image from my releases or ChubbyAnt's, or the Rescue ISO image I created) and put it onto a USB or CD so you can boot the Linux rescue disk (and you should be able to "see" OPAL 2.0 functions on the NVMe drives under Linux).

NOTE that at least mine and @ChubbyAnt's use SHA2/SHA512 for hashing the user auth password that is stored to the drive, so they are NOT backward compatible with a drive that was previously managed/encrypted by "vanilla" DTA SEDutil 1.15.1.

Please drop a line in this thread with follow-ups, and I'll try to keep an eye out.

[Zetanova]

Thank you for the informative message and your work.
I dont know why, but i stopped looking into forks long time ago.

I will test both out.

The NVMe is not the boot device and should get unlocked under windows.

[ghost]

Smasung 970 Pro NVMe

Correct typo

[BabaYB]

Hi @oom-is ,I have the same problem like @Zetanova had.
I allways get the resault as:

Scanning for Opal compliant disks
\.\PhysicalDrive0 No
\.\PhysicalDrive1 No
\.\PhysicalDrive2 No
No more disks present ending scan

MY ENV:
windows 7
samsung 970 EVO Plus via USB 3.0 converter

thanks,
Baba_Yb

[Zetanova]

@BabaYB USB will most likely not work and RAID driver are not working most of the time.
Both suppressing the ATA commands to the drive.

[ayushkumar024]

hi @Zetanova I got the same issue over USB as @BabaYB explained.

Then I found an excellent SCSI sendCmd implementation in a fork adding support for SAS drives, which I modify for NVMe over USB, This work with discovery message but I am unable to get proper response(property exchange failure) for any other command like initial setup or get msid.

Is this Implementation works according to you. Or do you have any suggestion how we can run sedutil commands on NVMe over USB.

My Environment
Windows 10
Kingston A2000 NVMe drive
JMicron USB convertor

Thanks in advance.

[Zetanova]

@ayushkumar024 On the USB-NVMe platin is a USB3-ATA-PCIe controller that wraps all data package in USB3 packages.
the only thing that it needs to do is to relay all raw Control-Packages to the drive.

They easiest way to test for functionality is to use some kind of SMART-Commands.
If they are working the SED-commands should work too (at least with an patched sedutil binary)

I bought my first USB3-NVMe Device last week and i will play around myself soon.

[ayushkumar024]

Thanks @Zetanova

[Sed-Research]

Solutions for external NVME drives across all platforms:

#115 (comment)

[Sed-Research]

This is a fault in DTA official "vanilla" SEDutil which does not formally support NVMe devices under Windows (and unfortunately is lacking updates since 2017). Please feel free to take a look at the precompiled binaries in my fork, or the original lukefor fork from which I sourced the Windows NVMe patch, or ChubbyAnt's fork also derived from @lukefor's code, for binaries that do support NVMe on Windows.

This thread contains a precompiled Lukefor executable for Windows which works:

ChubbyAnt#2

However @oom-is a small correction to what you wrote, ChubbyAnt's fork does not integrate the lukefor nvme in windows code, on sedutil.com they say they support nvme in windows only by unlocking using PBA first.

[neo125874]

@oom-is Hello, would the windows sedutil-integ version suppport nvme psid-revert etc. function,
or only support scan & query on windows now?