Having bought a used PC and now installing smartd on it, I'm getting smartd "Critical Warning (0x04): Reliability" emails about it (full [pastebin](https://pastebin.com/2rc5cvwg)) . The
Percentage Used: 112%
is concerning. Is that enough for smartd to declare "Critical Warning (0x04): Reliability"?
This message was generated by the smartd daemon running on:
host name: kosh
DNS domain: [Empty]
The following warning/error was logged by the smartd daemon:
Device: /dev/nvme0, Critical Warning (0x04): Reliability
Device info:
Samsung SSD 970 EVO Plus 1TB, S/N:S4EWNM0R328374F, FW:2B2QEXM7, 1.00 TB
=== 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)
Percentage Used: 112%
Error Information (NVMe Log 0x01, 16 of 64 entries)
Num ErrCount SQId CmdId Status PELoc LBA NSID VS Message
0 4357 0 0x0010 0x4004 - 0 0 - Invalid Field in Command
Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
No Self-tests Logged
It looks to me like the "Invalid Field in Command" errors are red herrings since I'm running smartmontools version 7.4 where https://www.smartmontools.org/ticket/1222 has been fixed, so that should not cause tests to fail.
I then ran:
$ sudo smartctl -t short /dev/nvme0n1
and now sudo smartctl --all /dev/nvme0n1
ends with:
Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
Num Test_Description Status Power_on_Hours Failing_LBA NSID Seg SCT Code
0 Short Completed: failed segments 3535 - 1 2 - -
1 Short Completed: failed segments 3535 - 1 2 - -
But I don't know how to get more information about the "failed segments".
Is this enough for me to conclude that the disk is bad and needs replacement, or it there still hope for it?
Asked by Peter V. Mørch
(665 rep)
Apr 25, 2024, 11:50 AM
Last activity: Apr 25, 2024, 01:38 PM
Last activity: Apr 25, 2024, 01:38 PM