4 ms·
Is there a way to look up that error log?
by cool_hw 4y ago
Is there a way to look up that error log?
- frankjr 4y agoError Information (NVMe Log 0x01, 16 of 64 entries) Num ErrCount SQId CmdId Status PELoc LBA NSID VS 0 16 0 0x0000 0x4016 0x004 0 1 - 1 15 0 0x0000 0x4016 0x004 0 1 - 2 14 0 0x0000 0x4016 0x004 0 1 - 3 13 0 0x0000 0x4016 0x004 0 1 - 4 12 0 0x0000 0x4016 0x004 0 1 - 5 11 0 0x0000 0x4016 0x004 0 1 - 6 10 0 0x0000 0x4016 0x004 0 1 - 7 9 0 0x0000 0x4016 0x004 0 1 - 8 8 0 0x0000 0x4016 0x004 0 1 - 9 7 0 0x0000 0x4016 0x004 0 1 - 10 6 0 0x0000 0x4016 0x004 0 1 - 11 5 0 0x0000 0x4016 0x004 0 1 - 12 4 0 0x0000 0x4016 0x004 0 1 - 13 3 0 0x0000 0x4016 0x004 0 1 - 14 2 0 0x0000 0x4016 0x004 0 1 - 15 1 0 0x0000 0x4016 0x004 0 1 - ... (48 entries not read) To be honest I'm not sure how to interpret it. There are some tools on Linux to read this information but the output doesn't really seem more useful.
- cool_hw 4y agoI did a quick search earlier and it seems these are informational only and not necessarily persistent warnings. Some discussion suggested that some unsupported requests to the disk can result in these, but I don't know for sure.