From: bugzilla-daemon@kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 219652] READ CAPACITY(16) not used on large USB-attached drive in recent kernels
Date: Fri, 03 Jan 2025 03:01:04 +0000 [thread overview]
Message-ID: <bug-219652-11613-x7rrreeyvD@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219652-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219652
--- Comment #9 from Kris Karas (bugs-a21@moonlit-rail.com) ---
Just saw Alan's comment #7 (posting race).
FWIW, there are two drives showing this error. The first is a Toshiba
DT01ACA300, and the second, a Seagate ST3000DM001. So it's rather unlikely to
be a drive firmware bug.
Given that this patch has been out since 6.9.1 (if I read git correctly), it's
a bit odd that my searches for relevant/duplicate bug reports came up empty.
Hardware bug with this particular USB/SATA bridge? I checked the
manufacturer's website, and the model 1610 sports an embedded 8051 uP with
downloadable firmware; however, there are no firmware resources on their
website.
I found one "smoking gun" in this report from site hddguru:
https://forum.hddguru.com/viewtopic.php?t=33369
It indicates that other initio USB-to-SATA adapters report sector_count-1 in
some cases.
If this is specific to Initio adapters, perhaps the easiest patch here is to
assume that if read_capacity_10 is reported as 0xfffffffe, then it's buggy
hardware, treat it as 0xffffffff and proceed thusly.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2025-01-03 3:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 0:57 [Bug 219652] New: READ CAPACITY(16) not used on large USB-attached drive in recent kernels bugzilla-daemon
2025-01-02 0:58 ` [Bug 219652] " bugzilla-daemon
2025-01-02 0:59 ` bugzilla-daemon
2025-01-02 5:22 ` bugzilla-daemon
2025-01-02 5:26 ` bugzilla-daemon
2025-01-02 15:38 ` bugzilla-daemon
2025-01-02 23:07 ` bugzilla-daemon
2025-01-03 0:53 ` [Bug 219652] New: " Mike Christie
2025-01-03 0:53 ` [Bug 219652] " bugzilla-daemon
2025-01-03 2:02 ` bugzilla-daemon
2025-01-03 2:26 ` bugzilla-daemon
2025-01-03 3:01 ` bugzilla-daemon [this message]
2025-01-03 3:30 ` bugzilla-daemon
2025-01-04 3:50 ` Mike Christie
2025-01-03 3:37 ` bugzilla-daemon
2025-01-04 3:50 ` bugzilla-daemon
2025-01-06 20:33 ` bugzilla-daemon
2025-01-06 21:08 ` bugzilla-daemon
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=bug-219652-11613-x7rrreeyvD@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-scsi@vger.kernel.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