Greetings,

The journey continues...

I recently bought a Ugreen USB-3 external NVMe housing and a Samsung 990 Pro 4TB SSD. They worked fine for a few weeks, including yesterday when I used it to back up my LAN server. Today, every attempt to connect it returns a dmesg error: "Read Capacity(10) failed" and of course it can't be connected. I've tried it on three machines, all with the same result.

My quandary is: how can I tell whether the Ugreen controller is not querying the SSD, or the SSD is not answering it? Which component do I return as
faulty?

The full dmesg entry:

usb 3-7: new high-speed USB device number 7 using xhci_hcd
usb 3-7: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=20.01 usb 3-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 3-7: Product: Ugreen Storage Device
usb 3-7: Manufacturer: Ugreen
usb 3-7: SerialNumber: 012938058E61
usb-storage 3-7:1.0: USB Mass Storage device detected
scsi host2: usb-storage 3-7:1.0
scsi 2:0:0:0: Direct-Access Realtek RTL9210 1.00 PQ: 0 ANSI: 6
sd 2:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
sd 2:0:0:0: [sda] Sense Key : Illegal Request [current]
sd 2:0:0:0: [sda] Add. Sense: Invalid field in cdb
sd 2:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B)
sd 2:0:0:0: [sda] 0-byte physical blocks
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 37 00 00 08
sd 2:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
sd 2:0:0:0: [sda] Attached SCSI disk

--
Regards,
Peter.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sunday, 30 March 2025 14:19:47 British Summer Time Michael wrote:

On Sunday, 30 March 2025 13:45:09 British Summer Time Peter Humphrey wrote:

8

sd 2:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK sd 2:0:0:0: [sda] Sense Key : Illegal Request [current]

This "Sense Key" is the response from the block device. It means some command data sent to it was deemed to be illegal and the device bailed out from executing the command. More details to make sense of this message may be in the SCSI specification.

Interesting.

sd 2:0:0:0: [sda] Add. Sense: Invalid field in cdb
sd 2:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B)
sd 2:0:0:0: [sda] 0-byte physical blocks
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 37 00 00 08
sd 2:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA sd 2:0:0:0: [sda] Attached SCSI disk

Does lsblk -a show the partition(s) on the device?

It shows a disk of size 0. (I keep forgetting to try lsblk, which I haven't
had to use until this exercise began.)

Does your Ugreen enclosure come with an external power supply

Nope.

You've already tried it on different PCs, so this problem is not isolated to a single PC.

Have you removed the SSD and connected it directly to the MoBo without any USB intermediary? This will separate a USB Vs SSD hardware problem.

I've a nasty feeling I damaged the SSD by applying too much force while installing it. Cracked track, or something. If so, I don't feel I should
return it as faulty.

[Slumps shoulders...]

Can I justify starting again and spending yet more hundreds? That's the question. Especially as the spinning disk it was to replace hasn't failed yet.

--
Regards,
Peter.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sunday, 30 March 2025 13:45:09 British Summer Time Peter Humphrey wrote:

Greetings,

The journey continues...

I recently bought a Ugreen USB-3 external NVMe housing and a Samsung 990 Pro 4TB SSD. They worked fine for a few weeks, including yesterday when I used
it to back up my LAN server. Today, every attempt to connect it returns a dmesg error: "Read Capacity(10) failed" and of course it can't be
connected. I've tried it on three machines, all with the same result.

My quandary is: how can I tell whether the Ugreen controller is not querying the SSD, or the SSD is not answering it? Which component do I return as faulty?

The full dmesg entry:

usb 3-7: new high-speed USB device number 7 using xhci_hcd
usb 3-7: New USB device found, idVendor=0bda, idProduct=9210,
bcdDevice=20.01 usb 3-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 3-7: Product: Ugreen Storage Device
usb 3-7: Manufacturer: Ugreen
usb 3-7: SerialNumber: 012938058E61
usb-storage 3-7:1.0: USB Mass Storage device detected

The above shows the USB device responded and consequently was detected by the kernel.

scsi host2: usb-storage 3-7:1.0
scsi 2:0:0:0: Direct-Access Realtek RTL9210 1.00 PQ: 0 ANSI: 6

and the controller handles SCSI commands, as expected. So far, so good with respect to the USB controller.

sd 2:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK sd 2:0:0:0: [sda] Sense Key : Illegal Request
[current]

This "Sense Key" is the response from the block device. It means some command data sent to it was deemed to be illegal and the device bailed out from executing the command. More details to make sense of this message may be in the SCSI specification.

sd 2:0:0:0: [sda] Add. Sense: Invalid field in cdb
sd 2:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B)
sd 2:0:0:0: [sda] 0-byte physical blocks
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 37 00 00 08
sd 2:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't
support DPO or FUA sd 2:0:0:0: [sda] Attached SCSI disk

Does lsblk -a show the partition(s) on the device?

Does your Ugreen enclosure come with an external power supply and if yes, have you powered it up from the mains? I'm thinking aloud here, this might be a matter of providing adequate power to it - but it does not explain why it suddenly started happening today.

You've already tried it on different PCs, so this problem is not isolated to a single PC.

Have you removed the SSD and connected it directly to the MoBo without any USB intermediary? This will separate a USB Vs SSD hardware problem.

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmfpRPMACgkQseqq9sKV ZxmgwA//dxhrDUPqMFp7Xj9htJP9/3PoF1fvP5CH3djWUd7fjiHC1B9tm6lG/rzU mpzwrSQBgVpgZ7QKsezVx9hyfmP+Q009pIsR+R46F9ipiw/KcY54hPBzRPYy4LRP Pc0qqOb1OxltnXC+bHJHZ/wwOAOVOgR781Sum6jR2ypHi+QBbwVJiWsjAbyEBRE2 s6eS2vFlSW3OY6zJdHW8u8Hqki/Vn/J5j6CYye1r71cqc5TpktxmLDbDiOMnoWEo evSihEc+Vc0Vdw4nlppOVzLABH0eiVpHKEH7EyD/EYMUAl9LQVB84Py03517OC4P CPAdpPuTIY1VLQzccb7CcJlFg908//arzSQgDs0Fywta41l4MauBfYb1XBh33rOp frbfHk556tnry1wc5CN0R8m8EuZ2dKjj2VCyn6WKuqa2R6mSs7JhRTKa5bs6JQKD AI1bBHTa8Jy9Y0ZF3goFKJyDA7v9BzSQqvzLnQ7s5HRiTcSmWSrTwW19IzrXDwu5 +mh6TZ5L53f8lOhsOEyOVyiPnNVa2up+FmdHjTm5U6ZVyFv9YE/wmhvlxU09Kc4a CgH9PRveFjUo5rB1VHhuQDqzNgfsK+BvkUQdH+b68BA4JI0qnWufiEqufg+xdTzW U+bBMSQ1Vo5NAFiBl3yB848lw7VIpxpLR9DLgcwB+EOaQpSfeVw=
=h8vr
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sunday, 30 March 2025 16:05:29 British Summer Time Peter Humphrey wrote:

I've a nasty feeling I damaged the SSD by applying too much force while installing it. Cracked track, or something. If so, I don't feel I should return it as faulty.

[Slumps shoulders...]

Can I justify starting again and spending yet more hundreds? That's the question. Especially as the spinning disk it was to replace hasn't failed yet.

Regretfully accidents do happen, as I well know first hand. ;-)

As I suggested you can connect briefly the SSD directly on a MoBo port to confirm if there is a problem with it. If it shows up and the partitions are all in place, then the fault must be with the USB enclosure.
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmfpYDoACgkQseqq9sKV ZxmybRAArrD9qoo3nb6nAj3IubKXy3lPfQtmqq8Xq2PIr37GKFHEVvrIR6LRPpzb 8h/0UEToFbepkskdgtR2jhGT6xEJV9ZqCyLDPSiLjzt+Ck1PxcxDfhSXzCMy4EbQ TzBqgyQK6brSbnBrMnrHdsImWWsjLvNSIXfWWsHrJO+CcqHRr1lsbuqx0guqy+AS dUA7/OwjCCqFC3IufAbCRfaH40E1ZyE/lRj/mWmE54uj0xxmVmbx6V3cFRcdoo58 aGxtlS7UFJuhLpr+tAyf/1IeqwGDE12a9NnjofzqA4yUfJjtWKGk3htPn73Ugsto Uw9H7lvKJpZaWeBlLGw7AuWTaMZHPYmrZRxIsx88tIzvKmJqkB8xvno2hBLuNY/1 SXK8uc5mBkUyIDmKDvNFpO03SgPQb96Mmt+hb/aAwqO8VdvP69f1D5ghH3LXnUxM Mxz+OFMka1wLbec685u/tJWBqTAEQyLExotnU/kXkdR6JkwvIxR35+dci3P/qvs0 5PztZT7fXqJrsC25aEzVCrqx6sSYVndw+dgs4WlIgFlbweGHTG28hYch6btU/BYt VAMeJ2/EVNUz4fVl3omTgvzUADyXFU2nF5aKugh+26zQz6tzcDfRkf/B3dcanqiE nhVI6e60gP1SxhODo3OfNYkOQqDmfczYTOuEifT8XZDwUGattxc=
=5oJV
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)