You are not logged in.

#26 2023-01-07 11:25:40

seth
Member
Registered: 2012-09-03
Posts: 36,887

Re: [RESOLVED] Dying SSD?

What if we don't grep that?

Offline

#27 2023-01-07 11:51:19

smoneck
Member
Registered: 2014-05-14
Posts: 105

Re: [RESOLVED] Dying SSD?

seth wrote:

What if we don't grep that?

> sudo nvme error-log /dev/nvme0
Error Log Entries for device:nvme0 entries:4
.................
 Entry[ 0]   
.................
error_count	: 573
sqid		: 0
cmdid		: 0x7
status_field	: 0x6002(Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag	: 0x1
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[ 1]   
.................
error_count	: 572
sqid		: 0
cmdid		: 0x10
status_field	: 0x6002(Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag	: 0x1
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[ 2]   
.................
error_count	: 571
sqid		: 0
cmdid		: 0
status_field	: 0x6002(Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag	: 0x1
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[ 3]   
.................
error_count	: 570
sqid		: 0
cmdid		: 0xc
status_field	: 0x6002(Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag	: 0x1
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................

Offline

#28 2023-01-07 13:57:59

seth
Member
Registered: 2012-09-03
Posts: 36,887

Re: [RESOLVED] Dying SSD?

https://github.com/linux-nvme/nvme-cli/issues/542
Looks like a generic "some error" and is likely a protocol error - but indeed no further details in the output.

Offline

Board footer

Powered by FluxBB