主页 / unix / 问题

问题[nvme](unix)

Martin Hope
Peter V. Mørch
Asked: 2024-04-25 19:50:29 +0800 CST
  • 5

购买了一台二手电脑，现在在上面安装了 smartd，我收到了 smartd 的“严重警告（0x04）：可靠性”电子邮件（完整的Pastebin）。这Percentage Used: 112%是令人担忧的。smartd 声明“严重警告（0x04）：可靠性”是否足够？

This message was generated by the smartd daemon running on:

   host name:  kosh
   DNS domain: [Empty]

The following warning/error was logged by the smartd daemon:

Device: /dev/nvme0, Critical Warning (0x04): Reliability

Device info:
Samsung SSD 970 EVO Plus 1TB, S/N:S4EWNM0R328374F, FW:2B2QEXM7, 1.00 TB

<snip>

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: FAILED!
- NVM subsystem reliability has been degraded

SMART/Health Information (NVMe Log 0x02)

<snip>
Percentage Used:                    112%
<snip>

Error Information (NVMe Log 0x01, 16 of 64 entries)
Num   ErrCount  SQId   CmdId  Status  PELoc          LBA  NSID    VS  Message
  0       4357     0  0x0010  0x4004      -            0     0     -  Invalid Field in Command

Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
No Self-tests Logged

在我看来，“命令中的无效字段”错误是红色鲱鱼，因为我正在运行 smartmontools 版本 7.4，其中https://www.smartmontools.org/ticket/1222已修复，因此不应导致测试失败。

然后我跑了：

$ sudo smartctl -t short /dev/nvme0n1

现在sudo smartctl --all /dev/nvme0n1结束于：

Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
Num  Test_Description  Status                       Power_on_Hours  Failing_LBA  NSID Seg SCT Code
 0   Short             Completed: failed segments             3535            -     1   2   -    -
 1   Short             Completed: failed segments             3535            -     1   2   -    -

但我不知道如何获取有关“失败片段”的更多信息。

这是否足以让我断定该磁盘已损坏并需要更换，或者仍然有希望？

nvme
Martin Hope
j4nd3r53n
Asked: 2022-07-05 07:00:28 +0800 CST
  • 1

我有一个 U.2 SSD，它在 lsblk 中显示为 nvme1n1：

root@eris:~# lsblk
NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
nvme0n1     259:0    0  3.6T  0 disk 
├─nvme0n1p1 259:1    0  476M  0 part /boot/efi
├─nvme0n1p2 259:2    0 38.1G  0 part /
└─nvme0n1p3 259:3    0  3.6T  0 part /data
nvme1n1     259:4    0  3.5T  0 disk

查看 dmesg，我可以看到：

root@eris:~# dmesg | grep -i nvme
[    0.997417] nvme nvme0: pci function 0000:01:00.0
[    0.997448] nvme nvme1: pci function 0000:04:00.0
...

这匹配：

root@eris:~# ll /sys/bus/pci/drivers/nvme | grep 04:00.0
lrwxrwxrwx 1 root root    0 Jul  4 14:41 0000:04:00.0 -> ../../../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:02.0/0000:04:00.0

这是我以后需要知道的。

我的问题是，有没有更简单的方法可以从/dev/nvme1n1to获得/sys/bus/pci/drivers/nvme/0000:04:00.0？

linux nvme