Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #79907

Bug#1041745: smartd[…]: Device: /dev/nvme0, number of Error Log entries increased from … to …

From "Al Ma" <alma0@ro.ru>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#1041745: smartd[…]: Device: /dev/nvme0, number of Error Log entries increased from … to …
Date 2023-08-04 02:20 +0200
Message-ID <GYQHT-4XlI-1@gated-at.bofh.it> (permalink)
References <GYpy1-4EXO-1@gated-at.bofh.it> <GUuPD-24Zn-1@gated-at.bofh.it> <GUuPD-24Zn-1@gated-at.bofh.it> <GUuPD-24Zn-1@gated-at.bofh.it> <GYpy1-4EXO-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

Thanks for looking into this. The solid-state–memory device in question is Samsung SSD 970 EVO 1TB, S/N:…, FW:2B2QEXE7, 1.00 TB. It's no longer sold on samsung.com but still sold as new on amazon (ASIN B07CGJNLBB; the Web site says it has been sold there since April 24, 2018). So yes, given the dates in https://en.wikipedia.org/wiki/NVM_Express#Specifications https://en.wikipedia.org/wiki/NVM_Express#Specifications, the drive might be aware of the NVMe 1.2 or 1.3 specification but, again hypothetically, not 1.4 or even 2.0. I wouldn't know how to check this, and firmware upgrades seem unavailable ( https://semiconductor.samsung.com/consumer-storage/support/tools/ http://semiconductor.samsung.com/consumer-storage/support/tools/ mentions the same version 2B2QEXE7). Just in case this helps, the motherboard is Asus WS C422 PRO/SE.
Here is some debugging data:
$ sudo nvme error-log -e 2 /dev/nvme0
Error Log Entries for device:nvme0 entries:2
.................
Entry[ 0]
.................
error_count     : 1885
sqid            : 0
cmdid           : 0x14
status_field    : 0x2002(Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag       : 0
parm_err_loc    : 0xffff
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     : 0
sqid            : 0
cmdid           : 0
status_field    : 0(Successful Completion: The command completed without error)
phase_tag       : 0
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
.................
$ sudo nvme list
Node                  Generic               SN                   Model                                    Namespace Usage                      Format           FW Rev
--------------------- --------------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme0n1          /dev/ng0n1            Anonymized S.N.      Samsung SSD 970 EVO 1TB                  1         135,04  GB /   1,00  TB    512   B +  0 B   2B2QEXE7
$ sudo nvme error-log -e 2 /dev/nvme0
Error Log Entries for device:nvme0 entries:2
.................
Entry[ 0]
.................
error_count     : 1885
sqid            : 0
cmdid           : 0x14
status_field    : 0x2002(Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag       : 0
parm_err_loc    : 0xffff
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     : 0
sqid            : 0
cmdid           : 0
status_field    : 0(Successful Completion: The command completed without error)
phase_tag       : 0
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
.................
As you see, the output is slightly different from that in https://github.com/linux-nvme/libnvme/issues/550 https://github.com/linux-nvme/libnvme/issues/550, and `nvme list` does not increase error_count (or at least not directly). If there's anything else I can help with, please let me know.
Gratefully,
AlMa

Back to linux.debian.kernel | Previous | NextPrevious in thread | Find similar | Unroll thread


Thread

Bug#1041745: smartd[…]: Device: /dev/nvme0, number of Error Log entries increased from … to … Daniel Swarbrick <dswarbrick@debian.org> - 2023-08-02 21:20 +0200
  Bug#1041745: smartd[…]: Device: /dev/nvme0, number of Error Log entries increased from … to … "Al Ma" <alma0@ro.ru> - 2023-08-04 02:20 +0200

csiph-web