Custom Query (1414 matches)

Hello, we are using a NVME "SAMSUNG MZVLB512HAJQ-00000" The Smartmontool is reporting the following error:

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: FAILED!
- NVM subsystem reliability has been degraded

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x04

The Attribut "Critical Warning" has different bits, signaling different status. According to the documentation the flag for bit 4 is: "If set to ‘1’, then the volatile memory backup device has failed. This field is only valid if the controller has a volatile memory backup solution"

The referred documentation is at ​https://nvmexpress.org/wp-content/uploads/NVM-Express-1_4-2019.06.10-Ratified.pdf (page 122).

Currently the bit 4 is reported as an error but this depends on the model (whether it has a capacitor for power loss protection).

Either this should be detected or maybe a parameter could be used to signal whether this is an error or not.

Output of:

sudo smartctl -q noserial -x /dev/sda -d megaraid,2 > "Seagate Barracuda.txt"

On a server where said drive is part of RAID array in slot 2.

As requested, file attached (if it works).

Submitting because:

sudo smartctl -i /dev/sda -d megaraid,2

displays (among other things):

Device is: Not in smartctl database [for details use: -P showall]

The ICY BOX IB-120StU3 uses a Prolific PL2773 chip, which is currently not supported by smartmontools. By reverse engineering the Windows tool iSmart.exe i have made the included patch. It seems to work well and supports all of smartctl -a.

Please review and consider including in your next release.