7

I've got a Brand New ORICO TCM3-C3 NVMe M.2 SSD enclosure which I am using with a WD Blue WDS500G2B0B-00YS70 500Gb NVMe ssd (also new)

When I plug it in I get the usual ping of a USB device being recognised but when I run lsblk of sudo fdisk -l It does not show up.

dmesg gives the following:

[  851.445300] usb 2-2: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd
[  851.466378] usb 2-2: New USB device found, idVendor=152d, idProduct=0583, bcdDevice= 2.09
[  851.466383] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  851.466386] usb 2-2: Product: External HDD
[  851.466388] usb 2-2: Manufacturer: External USB3.0
[  851.466391] usb 2-2: SerialNumber: DD56419883969
[  851.471581] scsi host0: uas
[  851.472404] scsi 0:0:0:0: Direct-Access     External USB3.0           0209 PQ: 0 ANSI: 6
[  851.473635] sd 0:0:0:0: Attached scsi generic sg0 type 0
[  859.632889] sd 0:0:0:0: [sda] Unit Not Ready
[  859.632896] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] 
[  859.632903] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 
[  859.633498] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  859.633504] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] 
[  859.633510] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 
[  859.633938] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  859.633941] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] 
[  859.633946] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 
[  859.634336] sd 0:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B)
[  859.634339] sd 0:0:0:0: [sda] 0-byte physical blocks
[  859.634699] sd 0:0:0:0: [sda] Test WP failed, assume Write Enabled
[  859.634821] sd 0:0:0:0: [sda] Asking for cache data failed
[  859.634828] sd 0:0:0:0: [sda] Assuming drive cache: write through
[  859.635177] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (0 byt>
[  859.654051] sd 0:0:0:0: [sda] Unit Not Ready
[  859.654060] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] 
[  859.654069] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 
[  859.654498] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  859.654505] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] 
[  859.654512] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 
[  859.654950] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  859.654956] sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] 
[  859.654965] sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 
[  859.656373] sd 0:0:0:0: [sda] Attached SCSI disk

I tried this on my laptop running Ubuntu 20.04 kernel 5.4.0-37-generic and on my raspberry pi4 running the new 64bit pi OS it had basically the same dmesg

Any ideas about if/how I can get this device to work?

Richard J. Acton
  • 201

2 Answers2

2

RTFM Richard RTFM - I picked up sata WD blues not NVMe ones With the correct SSD type for the adapter (NVMe) this works fine.

Richard J. Acton
  • 201
0

I had a similar issue with an ssd (nvme) that had been running Ubuntu. The boot information became corrupted during an upgrade to 20.04. I'm assuming the mbr was damaged, as well. After putting the ssd in an adapter, I couldn't access the drive from any of 3 linux computers (including the one I'd removed the ssd from).

But I was able to recover all of the data in the other partitions using a Macbook Pro with osxfuse and ext4fuse both installed thru homebrew. This is making me think the Linux drivers are not compatible with the adapter.

If you have access to a Mac, you may be able to at least see what's on the drive, and give you a hint at what's wrong. HtH.

DSCherry
  • 1