Custom Query (1565 matches)

About

It would be great to add NVMe support to the smartctl. This task is not very trivial - because smart in NVMe is implemented differently then in SCSI/SAS or SATA. This ticket will be used to track changes in smartmontools and to collect important related links.

NVMe standard and vendor specific log pages

• Official specifications: ​http://nvmexpress.org/specifications/
• ​Intel NVMe documentation with Intel-specific log pages (CAh, C5h, DDh, C1h/C2h).
• ​OCZ Z-Drive specification, with vendor-specific smart log page (E0h)

Hardware and emulation

• ​QEMU fork which can emulates NVMe device with most of the features supported, including SMART log pages, namespaces, etc. Tested with Linux and FreeBSD, full list of the options could be found in the ​source code.

Linux NVMe support

• NVMe kernel header ​linux/nvme.h
• ​nvme-cli - NVM-Express user space tooling for Linux
• ​nvme-user - another opensource userspace utility

FreeBSD NVMe support

• NVMe kernel header ​dev/nvme/nvme.h
• ​nvmecontrol utility, ​opensource.

Windows NVMe support

• ​OpenFabrics NVMe driver for Windows. It provides a NVME_PASS_THROUGH I/O-control which is reportedly also supported by the NVMe Windows drivers from Intel and OCZ.
• ​IOCTL_STORAGE_PROTOCOL_COMMAND - NVMe pass-through I/O-control supported by the generic NVMe driver for Windows (Stornvme.sys). Requires Windows 10.
• ​Naraeon NVMe Tools windows ​open source NVMe SMART / Health Information Log Viewer on Windows
  • ​Samsung 950 Pro’s NVMe Commands
  • ​Intel 750 Series’ NVMe Commands
• Intel® ​Solid-State Drive Data Center Tool

OS X NVMe support

• Kind of official support added from 10.10.3, closes source, not documented, only apple-branded NVMe devices are supported. Implements NVMeSMARTClient library, however API is not documented.
• ​MacVidCards NVMe driver - third party closed-source driver, coming with closed-source nvme-cli management utility, which is based on open-source one.

Solaris NVMe support

• ​nvmeadm - NVM Express controller command line interface, interface is unknown
• ​Illumos NVMe driver, ​no management interface/tool yet implemented

It was found that at least some of the drives are built on the phison chipset, but using sandforce attributes. These are similar but not the same, see ​http://media.kingston.com/support/downloads/MKP_521_Phison_SMART_attribute.pdf (phison) and ​http://media.kingston.com/support/downloads/MKP_306_SMART_attribute.pdf (sandforce). We need to split them to the separate drivedb records instead. Need to check which controller belongs to each chipset. This is the list:

bash-3.2$ grep \"KINGS drivedb.h
[?]    "KINGSTON SE50S3(100|240|480)G|" // tested with SE50S3100G/KE1ABBF0
[SF]    "KINGSTON SH10[03]S3(90|120|240|480)G|" // HyperX (3K), SF-2281, tested with
[SF]    "KINGSTON SKC(300S37A|380S3)(60|120|180|240|480)G|" // KC300, SF-2281, tested with
[SF]    "KINGSTON SVP200S3(7A)?(60|90|120|240|480)G|" // V+ 200, SF-2281, tested with
[SF]    "KINGSTON SMS200S3(30|60|120)G|" // mSATA, SF-2241, tested with SMS200S3120G/KC3ABBF0
[SF]    "KINGSTON SMS450S3(32|64|128)G|" // mSATA, SF-2281, tested with SMS450S3128G/503ABBF0
[SF]    "KINGSTON (SV300|SKC100|SE100)S3.*G|" // other SF-2281
[PH]    "KINGSTON SUV300S37A(120|240|480)G" // UV300 SSD, tested with KINGSTON SUV300S37A120G/SAFM11.K
[?]    "KINGSTON SSDNow 40GB",
[??]    "KINGSTON SSDNow 40GB",
[?]    "KINGSTON SNV425S2(64|128)GB|"  // SSDNow V Series (2. Generation, JMF618),
[?]    "KINGSTON SSDNOW 30GB|" // tested with KINGSTON SSDNOW 30GB/AJXA0202
[?]    "KINGSTON SS100S2(8|16)G|"  // SSDNow S100 Series, tested with KINGSTON SS100S28G/D100309a
[?]    "KINGSTON SNVP325S2(64|128|256|512)GB|" // SSDNow V+ Series, tested with KINGSTON SNVP325S2128GB/AGYA0201
    "KINGSTON SVP?100S2B?(64|96|128|256|512)G|"  // SSDNow V100/V+100 Series,
[?]    "KINGSTON SV200S3(64|128|256)G|" // SSDNow V200 Series, tested with KINGSTON SV200S3128G/E120506a

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