Custom Query (1438 matches)

Current status:

1. Smartctl 5.37 is distributed within system (eCS 2.2). It is compiled by IBM VAC compiler according to the version info (i386-pc-ibmvac)
2. Files os_os2.{cpp,h} were never properly integrated to the release and are missing in the autoconf and resulted targz. This should be easy to fix.
3. File os_os2.cpp is very outdated and currently not compiling properly. It seems that it will need some efforts to compile.
4. Smartmontools itself compiles under GCC/OS2 with some minimal autoconf tweaks and blames that application is not ported. Because of 2.

Todo:

1. Include os_os* to the official tarball, and patch configure.ac and related files.
2. fix os_os2.cpp to make it compile.
3. Test it on VPC (at least -i should work)
4. Ask someone to test it on a real hw.
5. Update man and wiki

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.

SanDisk SD8SBAT128G1002 in an ASUS R417NA/E402N/E402NA laptop. Not found in drivedb.h, revision 4949 of 2019-08-20.

It seems to be the same as ticket #799, except for the form factor (M.2 2280 for SD8SBAT, 2.5”/7mm cased for SD8SNAT).

To keep the discussion in one place, I will post additional info in ticket #799. Just creating this separate ticket as instructed by the FAQ.