Opened 12 months ago
Closed 12 months ago
#1785 closed enhancement (worksforme)
Decipher NVMe errors
Reported by: | Artem S. Tashkinov | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | Release 7.4 |
Component: | all | Version: | 7.4 |
Keywords: | nvme | Cc: |
Description
Currently smartctl doesn't properly parse and decode NVMe log errors.
Would be nice if you did.
https://github.com/linux-nvme/nvme-cli/issues/800#issuecomment-685462375
Change History (3)
comment:1 by , 12 months ago
comment:2 by , 12 months ago
Component: | smartctl → all |
---|---|
Keywords: | nvme added |
Milestone: | → undecided |
Type: | enhancement → defect |
Please be more specific and provide a sample smartctl -l error
output with an incorrectly decoded error in the Message
column. Make sure to use smartctl 7.4 or at least a CI build of r5471 or later.
comment:3 by , 12 months ago
Milestone: | undecided → Release 7.4 |
---|---|
Resolution: | → worksforme |
Status: | new → closed |
Type: | defect → enhancement |
This feature is available since r5471 and included in smartmontools 7.4.
Feel free to reopen this ticket if you could provide a sample output with incorrect translation of a NVMe status to an error message.
Note:
See TracTickets
for help on using tickets.
Also:
https://superuser.com/a/1814225