NVME read error with no SMART errors

pheeenix · 2024-12-10 17:36:28

I just moved my fully working, internal Samsung NVMe to an external case but suddenly can't access the data anymore.

Dmesg gives me the following:

[  456.613956] usb 4-1: new SuperSpeed Plus Gen 2x1 USB device number 2 using xhci_hcd
[  456.650899] usb 4-1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=f0.01
[  456.650921] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  456.650933] usb 4-1: Product: Sabrent
[  456.650942] usb 4-1: Manufacturer: Sabrent
[  456.650950] usb 4-1: SerialNumber: 830700000022
[  456.685474] usb 4-1: Enable of device-initiated U1 failed.
[  456.690317] usb 4-1: Enable of device-initiated U2 failed.
[  456.715853] usb 4-1: Enable of device-initiated U1 failed.
[  456.716457] usb 4-1: Enable of device-initiated U2 failed.
[  456.719794] scsi host1: uas
[  457.155460] scsi 1:0:0:0: Direct-Access     Sabrent  SSD              1.00 PQ: 0 ANSI: 6
[  457.190223] sd 1:0:0:0: Attached scsi generic sg1 type 0
[  460.962919] sd 1:0:0:0: [sdb] 2000409264 512-byte logical blocks: (1.02 TB/954 GiB)
[  460.965024] sd 1:0:0:0: [sdb] Write Protect is off
[  460.965038] sd 1:0:0:0: [sdb] Mode Sense: 37 00 00 08
[  460.968173] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[  460.969244] sd 1:0:0:0: [sdb] Preferred minimum I/O size 512 bytes
[  460.969256] sd 1:0:0:0: [sdb] Optimal transfer size 33553920 bytes
[  468.522237] sd 1:0:0:0: [sdb] Attached SCSI disk
[  476.141034] sd 1:0:0:0: [sdb] tag#16 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=7s
[  476.141063] sd 1:0:0:0: [sdb] tag#16 Sense Key : Illegal Request [current] 
[  476.141073] sd 1:0:0:0: [sdb] tag#16 Add. Sense: Invalid command operation code
[  476.141083] sd 1:0:0:0: [sdb] tag#16 CDB: Read(10) 28 00 77 3b d2 00 00 00 08 00
[  476.141091] critical target error, dev sdb, sector 2000409088 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  479.910818] sd 1:0:0:0: [sdb] tag#17 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
[  479.910847] sd 1:0:0:0: [sdb] tag#17 Sense Key : Illegal Request [current] 
[  479.910858] sd 1:0:0:0: [sdb] tag#17 Add. Sense: Invalid command operation code
[  479.910868] sd 1:0:0:0: [sdb] tag#17 CDB: Read(10) 28 00 77 3b d2 00 00 00 08 00
[  479.910876] critical target error, dev sdb, sector 2000409088 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  479.910897] Buffer I/O error on dev sdb, logical block 250051136, async page read

Checking the drive health via SMART seems to indicate everything is fine though? Not sure if I'm reading out the parameters correctly. `smartctl --xall /dev/sdb`:

=== START OF INFORMATION SECTION ===
Model Number:                       SAMSUNG MZVLB1T0HALR-000L7
Serial Number:                      S3TPNX0K701433
Firmware Version:                   5L2QEXA7
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x002538
Total NVM Capacity:                 1,024,209,543,168 [1.02 TB]
Unallocated NVM Capacity:           0
Controller ID:                      4
NVMe Version:                       1.2
Number of Namespaces:               1
Namespace 1 Size/Capacity:          1,024,209,543,168 [1.02 TB]
Namespace 1 Utilization:            905,886,113,792 [905 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 8781b558e3
Local Time is:                      Tue Dec 10 18:24:04 2024 CET
Firmware Updates (0x16):            3 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x001f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Log Page Attributes (0x03):         S/H_per_NS Cmd_Eff_Lg
Maximum Data Transfer Size:         512 Pages
Warning  Comp. Temp. Threshold:     81 Celsius
Critical Comp. Temp. Threshold:     82 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     7.02W       -        -    0  0  0  0        0       0
 1 +     6.30W       -        -    1  1  1  1        0       0
 2 +     3.50W       -        -    2  2  2  2        0       0
 3 -   0.0760W       -        -    3  3  3  3      210    1200
 4 -   0.0050W       -        -    4  4  4  4     2000    8000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        27 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    1%
Data Units Read:                    38,626,938 [19.7 TB]
Data Units Written:                 47,915,690 [24.5 TB]
Host Read Commands:                 228,527,501
Host Write Commands:                1,654,232,270
Controller Busy Time:               2,622
Power Cycles:                       3,386
Power On Hours:                     2,393
Unsafe Shutdowns:                   119
Media and Data Integrity Errors:    0
Error Information Log Entries:      3,737
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               27 Celsius
Temperature Sensor 2:               27 Celsius

Warning: NVMe Get Log truncated to 0x200 bytes, 0x200 bytes zero filled
Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

Warning: NVMe Get Log truncated to 0x200 bytes, 0x034 bytes zero filled
Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
No Self-tests Logged

I would be very surprised if I bricked the device while removing it. System is a Thinkpad T480. I had set a HDD passwort at some point but removed it in the BIOS before removing it. The drive was working fine after.

Has anyone seen anything like this before? I would at least expect the SMART output to contain errors, leading me to believe something else might be broken?

seth · 2024-12-10 18:08:34

an external case

https://github.com/raspberrypi/linux/issues/4130

lsusb -tv

Does the case allow external power supply?

pheeenix · 2024-12-10 21:56:15

seth wrote:

lsusb -tv

Relevant section:

/:   Bus 002.Port 001: Dev 001, Class-root_hub, Driver=xhci_hcd/6p, 5000M
     ID 1d6b:0003 Linux Foundation 3.0 root hub
     |__ Port 004: Deu 007, If 0, Class-Mass Storage, Driver-uas, 5000M ID Obda: 9210 Realtek Semiconductor Corp. RTL9210 M.2 NUME Adapter

Thanks for the link to the discussion around enclosures using the RTL9210 chipset! Guess that applies to mine as well.

The enclosure is a Sabrent EC-SNVE 10Gbps and sadly does not allow for an external power supply. I would be surprised if it is a power related issue though, as my Samsung 990 Pro works perfectly in the same enclosure, using the same USB-C port and cable, with a higher draw of up to 9.3W. But who knows.

I will try flashing a new firmware once I can locate a Windows PC. Flashing via VM seems a little dicey according to that Github issue.

Arch Linux

#1 2024-12-10 17:36:28

NVME read error with no SMART errors

#2 2024-12-10 18:08:34

Re: NVME read error with no SMART errors

#3 2024-12-10 21:56:15

Re: NVME read error with no SMART errors

Board footer