From: Johann Klammer <klammerj@a1.net>
To: linux-usb@vger.kernel.org
Subject: Re: possible regression in usb-storage?
Date: Fri, 25 Sep 2026 08:20:19 +0200 [thread overview]
Message-ID: <be5899e3-3e3e-4977-e4aa-32ca368f06cd@a1.net> (raw)
In-Reply-To: <605c0845-cfd4-0702-4322-53d9c8037b70@a1.net>
On 9/25/26 6:37 AM, Johann Klammer wrote:
>
>
> On 9/25/26 4:03 AM, Alan Stern wrote:
>>
>> Maybe the drive doesn't like the 100-byte INQUIRY, even though it
>> claims to support it. You can test this by doing (as root):
>>
>> echo 'Seagate:Expansion SW:1024' >/proc/scsi/device_info
>>
>> before you plug in the drive. That should suppress the 100-byte
>> INQUIRY command.
>>
>> Alan Stern
>>
> I don't seem to have that file. Am I missing a module?
Nevermind. I put it in modprobe.d
kernel 6.9.9 with no usb quirks and
options scsi_mod dev_flags="Seagate:Expansion SW:1024"
I did not get crashing threads this time. but a slew of errors.
and a 0 bytes sdd device.
> [ 125.722585] usb 5-6: new high-speed USB device number 4 using ehci-pci
> [ 125.927652] usb 5-6: New USB device found, idVendor=0bc2, idProduct=2039, bcd
> [ 125.927686] usb 5-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [ 125.927713] usb 5-6: Product: Expansion SW
> [ 125.927733] usb 5-6: Manufacturer: Seagate
> [ 125.927752] usb 5-6: SerialNumber: 00000000NACD256B
> [ 125.928687] scsi host5: uas
> [ 125.929390] scsi 5:0:0:0: Direct-Access Seagate Expansion SW 1901 PQ
> [ 125.934625] scsi 5:0:0:0: Attached scsi generic sg3 type 0
> [ 157.950205] sd 5:0:0:0: [sdd] Unit Not Ready
> [ 157.951286] sd 5:0:0:0: [sdd] Sense Key : Hardware Error [current].
> [ 157.952357] sd 5:0:0:0: [sdd] ASC=0x44 <<vendor>>ASCQ=0x81.
> [ 157.953828] sd 5:0:0:0: [sdd] Read Capacity(16) failed: Result: hostbyte=DID_
> [ 157.954921] sd 5:0:0:0: [sdd] Sense Key : Hardware Error [current].
> [ 157.952357] sd 5:0:0:0: [sdd] ASC=0x44 <<vendor>>ASCQ=0x81.
> [ 157.953828] sd 5:0:0:0: [sdd] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
> [ 157.954921] sd 5:0:0:0: [sdd] Sense Key : Hardware Error [current].
> [ 157.956034] sd 5:0:0:0: [sdd] ASC=0x44 <<vendor>>ASCQ=0x81.
> [ 157.957578] sd 5:0:0:0: [sdd] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
> [ 157.958688] sd 5:0:0:0: [sdd] Sense Key : Hardware Error [current].
> [ 157.959789] sd 5:0:0:0: [sdd] ASC=0x44 <<vendor>>ASCQ=0x81.
> [ 157.960958] sd 5:0:0:0: [sdd] 0 512-byte logical blocks: (0 B/0 B)
> [ 157.962042] sd 5:0:0:0: [sdd] 0-byte physical blocks
> [ 157.963454] sd 5:0:0:0: [sdd] Test WP failed, assume Write Enabled
> [ 157.964703] sd 5:0:0:0: [sdd] Asking for cache data failed
> [ 157.965753] sd 5:0:0:0: [sdd] Assuming drive cache: write through
> [ 157.967330] sd 5:0:0:0: [sdd] Preferred minimum I/O size 4096 bytes not a multiple of physical block size (0 bytes)
> [ 157.968382] sd 5:0:0:0: [sdd] Optimal transfer size 33553920 bytes not a multiple of physical block size (0 bytes)
> [ 157.969763] sd 5:0:0:0: [sdd] Attached SCSI disk
> [ 310.080965] usb 5-6: USB disconnect, device number 4
next prev parent reply other threads:[~2026-09-25 6:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 17:43 possible regression in usb-storage? Johann Klammer
2026-09-23 20:01 ` Johann Klammer
2026-09-24 2:08 ` Alan Stern
2026-09-24 5:00 ` Johann Klammer
2026-09-24 14:24 ` Alan Stern
2026-09-24 17:29 ` Johann Klammer
2026-09-24 5:18 ` Johann Klammer
2026-09-24 14:28 ` Alan Stern
2026-09-24 17:30 ` Johann Klammer
2026-09-24 17:53 ` Johann Klammer
2026-09-25 2:03 ` Alan Stern
2026-09-25 4:37 ` Johann Klammer
2026-09-25 6:20 ` Johann Klammer [this message]
2026-09-25 7:51 ` Johann Klammer
2026-09-25 13:06 ` Alan Stern
2026-09-25 17:28 ` Johann Klammer
2026-09-26 14:46 ` Alan Stern
2026-09-26 20:44 ` Johann Klammer
2026-09-28 1:22 ` Alan Stern
2026-09-28 3:15 ` Johann Klammer
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=be5899e3-3e3e-4977-e4aa-32ca368f06cd@a1.net \
--to=klammerj@a1.net \
--cc=linux-usb@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