From: Thomas Schweikle <tschweikle@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] USB NVMe connection problem
Date: Sun, 30 Mar 2025 15:03:47 +0200 [thread overview]
Message-ID: <CA+rGx5c4pB+fsTzBR2awj27BsFd-E5dWOjT4ZWPd0hSWg8SuRg@mail.gmail.com> (raw)
In-Reply-To: <4970686.GXAFRqVoOG@cube>
[-- Attachment #1: Type: text/plain, Size: 2281 bytes --]
Any second USB NVMe disk housing available? If yes, test the disk out in
there. If it works: you found out the disk housing is defective. If it does
not work: it may be the disk.
Do you have a second NVMe disk available? Switch disks. Then check if the
second disk works with this maybe defective disk housing. If it does, the
disk may be defective. If it does not, the housing is defective.
It may even be both are defective: the disk and the housing.
On Sun, Mar 30, 2025 at 2:45 PM Peter Humphrey <peter@prh.myzen.co.uk>
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
> 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.
>
>
>
>
>
--
Thomas
[-- Attachment #2: Type: text/html, Size: 2842 bytes --]
next prev parent reply other threads:[~2025-03-30 13:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-30 12:45 [gentoo-user] USB NVMe connection problem Peter Humphrey
2025-03-30 13:03 ` Thomas Schweikle [this message]
2025-03-30 13:19 ` Michael
2025-03-30 15:05 ` Peter Humphrey
2025-03-30 15:16 ` Michael
2025-03-30 20:19 ` [OT} " Peter Humphrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+rGx5c4pB+fsTzBR2awj27BsFd-E5dWOjT4ZWPd0hSWg8SuRg@mail.gmail.com \
--to=tschweikle@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox