Custom Query (1359 matches)

Based on my own reverse engineering efforts, the current implementation is almost correct, but there are two issues:

• The Number of Dwords Lower (NUMDL) field in this command is two bytes (big-endian), not one byte.
• The final eight bytes of the CDB are the Log Page Offset as a big-endian, 64-bit qword.

The details of this command (and others) can be found in my reverse engineering repo here (see command 0xE6: "Send NVMe Admin Command"): ​https://github.com/cyrozap/usb-to-pcie-re/blob/1f735f5ec9699d95fb802f7d82bc21ad7bd1291a/ASM236x/doc/Notes.md#usb-protocol

Attached is the patch that fixes the above issues, as well as the smartctl -d sntasmedia -q noserial -x output for two different SSD enclosures:

• An Alxum ASM2362-based enclosure with a Crucial P5 Plus SSD
• An ASM2364-based Seagate FireCuda Gaming SSD

After applying the patch, I've confirmed using Wireshark that requesting more than 512 bytes works (the most I saw requested was 1024 bytes / 0x100 dwords), and the responses contain valid data and are not truncated. No command timeouts were experienced during this testing.

This device is based on the ASM2364 USB NVMe bridge. Attached is the output of smartctl -d sntasmedia -q noserial -x and a patch to add the device to drivedb.h.

When I try to execute the update-smart-drivedb.ps1 script in a Powershell or Command Prompt CLI (running as Administrator or not) I receive the error:

& : The term 'gpg.exe gpg.exe' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At update-smart-drivedb.ps1:500 char:16
+   $($input | & $cmdobj @args 2>&1) | %{ $_.ToString() }
+                ~~~~~~~
    + CategoryInfo          : ObjectNotFound: (gpg.exe gpg.exe:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

update-smart-drivedb.ps1 version 5515 2023-07-24 12:58:25Z from smartmontools 7.4, on Windows 10 22H2 64-bit, Powershell 10.0.19041.3636. gpg.exe is in $PATH and works.