Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #79898 > unrolled thread
| Started by | Daniel Swarbrick <dswarbrick@debian.org> |
|---|---|
| First post | 2023-08-02 21:20 +0200 |
| Last post | 2023-08-04 02:20 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
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
| From | Daniel Swarbrick <dswarbrick@debian.org> |
|---|---|
| Date | 2023-08-02 21:20 +0200 |
| Subject | Bug#1041745: smartd[…]: Device: /dev/nvme0, number of Error Log entries increased from … to … |
| Message-ID | <GYpy1-4EXO-1@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
This sounds quite similar to this: https://github.com/linux-nvme/libnvme/issues/550 Even prior to that bug, I noticed that the smart error log counter would increment by one with every reboot. This was not too concerning, but when nvme-cli 2.x started to result in (albeit innocent) errors being logged each time a "nvme list" command was executed, it became an annoyance. As I understand it, it was due to the SSD being fairly old, and the firmware only supporting a fairly outdated version of the NVMe spec (< 1.2) At least the _kernel_ should have fixed this, with commit https://github.com/torvalds/linux/commit/d7ac8dca938cd60cf7bd9a89a229a173c6bcba87 A fix for nvme-cli (via libnvme) is still being worked on, AFAIK.
[toc] | [next] | [standalone]
| From | "Al Ma" <alma0@ro.ru> |
|---|---|
| Date | 2023-08-04 02:20 +0200 |
| Message-ID | <GYQHT-4XlI-1@gated-at.bofh.it> |
| In reply to | #79898 |
[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
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web