Custom Query (1359 matches)

The nvme self test commands in smartctl fail with a non-zero retval when specifying a namespace (e.g. /dev/nvme0n1). These commands work when specifying the character device (e.g. /dev/nvme0). This issue also affects other smartctl functionality that implies -l selftest.

# smartctl -t short /dev/nvme0n1
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-5.15.0-79-generic] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

Read Self-test Log failed: Invalid Field in Command (0x002)

# smartctl -t short /dev/nvme0
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-5.15.0-79-generic] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

Self-test has begun
Use smartctl -X to abort test

# smartctl -l selftest /dev/nvme0n1
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-5.15.0-79-generic] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF SMART DATA SECTION ===
Read Self-test Log failed: Invalid Field in Command (0x002)

# smartctl -l selftest /dev/nvme0
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-5.15.0-79-generic] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF SMART DATA SECTION ===
Self-test Log (NVMe Log 0x06)
Self-test status: Short self-test in progress (31% completed)
Num  Test_Description  Status                       Power_on_Hours  Failing_LBA  NSID Seg SCT Code
 0   Short             Completed without error                 962            -     -   -   -    -
 1   Short             Completed without error                 962            -     -   -   -    -
 2   Short             Completed without error                 962            -     -   -   -    -

This entry is unnecessarily restrictive:

HFS(480|960|1T9|3T8)G3[2E]FEH-7[4A]10A", tested with HFS480G32FEH-7410A/90037Q00

Replace -7[4A]10A with .* to match other variants. If that is not acceptable, I've included also a diff to match HFS480G32FEH-BA10A explicitly.

Followup from here: https://www.smartmontools.org/ticket/338 dmesg log:

[Jul14 17:50] usb 2-1: new SuperSpeed USB device number 6 using xhci_hcd
[  +0.017371] usb 2-1: New USB device found, idVendor=ab12, idProduct=34cd, bcdDevice= 4.05
[  +0.000005] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  +0.000003] usb 2-1: Product: External Disk
[  +0.000001] usb 2-1: Manufacturer: USB30
[  +0.000002] usb 2-1: SerialNumber: 01600000002D
[  +0.005995] scsi host5: uas
[  +0.000514] scsi 5:0:0:0: Direct-Access     USB30                     0405 PQ: 0 ANSI: 6

This hardware is a SATA to USB adapter enclosure. Exact model: Sveon STG064 Laptop Hard Drive 2.5 Inch Silver in Red (2.5 - Hard Drive, SATA, Serial ATA II, Serial ATA III, 9.5 mm, Hard Drive, 2.0/3.0 (3.1 Gen 1), Hard Drive) Purchase link: ​https://www.amazon.de/-/en/Sveon-STG064-Laptop-Drive-Silver/dp/B0798MCWL8

It requires some hard drive connected to SATA port when connecting the USB to the computer, otherwise dmesg does not output anything.

Test:

# smartctl -H /dev/sdf
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.4.6-arch1-1] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/sdf: Unknown USB bridge [0xab12:0x34cd (0x405)]
Please specify device type with the -d option.

Use smartctl -h to get a usage summary

This works fine:

# smartctl -H /dev/sdf -d sat