Linux-USB Archive on lore.kernel.org
 help / color / Atom feed
From: "Till Dörges" <doerges@pre-sense.de>
To: linux-usb@vger.kernel.org
Subject: Ext. HDDs not working under Linux via USB 3.0 but under Windows
Date: Sat, 23 May 2020 16:57:50 +0200
Message-ID: <512118bc-e639-2387-e608-56b7e30fc3b2@pre-sense.de> (raw)

Hello all,

I'm trying to get external HDDs from Sony to work under Linux with USB 3.0.

They do work OK under Windows (USB 2.0 and 3.0).

They also work OK under Linux for USB 2.0.


The drives are from the PSZ-HA
(https://pro.sony/en_AU/products/portable-storage/psz-ha-series) and PSZ-HC
(https://pro.sony/ue_US/products/portable-storage/psz-hc-series) series.

I know those are both discontinued, but there still seem to be quite a few of those
around.

The drives I'm looking at have these vendor and product IDs:

 - PSZ-HA2T: idVendor=054c, idProduct=087d
 - PSZ-HA1T: idVendor=054c, idProduct=087d
 - PSZ-HA50: idVendor=054c, idProduct=087d
 - PSZ-HC1T: idVendor=054c, idProduct=0c4f


I've tried several Linux Kernels (4.4.x and 5.3.x) and several USB 3.0 host
controllers, e.g.
 - Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI
 - Renesas Technology Corp. uPD720202 USB 3.0 Host Controller
 - NEC Corporation uPD720200 USB 3.0 Host Controller


I've also tried several of the quirk settings
(https://github.com/torvalds/linux/blob/ead751507de86d90fa250431e9990a8b881f713c/drivers/usb/storage/usb.c#L527).


Unfortunately the problem (drives won't work under Linux when attached via USB 3.0)
persists.


For example, when attaching a PSZ-HA2T via USB 3.0 with Kernel 5.3.18 (from upcoming
openSUSE Leap 15.2) I get this in dmesg:

--- snip ---
[  767.481938] usb 6-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[  767.505381] usb 6-1: New USB device found, idVendor=054c, idProduct=087d,
bcdDevice= 0.0a
[  767.505385] usb 6-1: New USB device strings: Mfr=10, Product=11, SerialNumber=3
[  767.505387] usb 6-1: Product: Portable Storage
[  767.505388] usb 6-1: Manufacturer: Sony
[  767.505389] usb 6-1: SerialNumber: 230877290443
[  767.522588] scsi host5: uas
[  771.524123] scsi 5:0:0:0: Direct-Access     Sony     PSZ-H            320: PQ: 0
ANSI: 6
[  777.526863] sd 5:0:0:0: Attached scsi generic sg7 type 0
[  777.527091] sd 5:0:0:0: [sdf] Spinning up disk...
[  778.537372]
..................................................................................................not
responding...
[  885.868786] sd 5:0:0:0: [sdf] 281474976710656 512-byte logical blocks: (144 PB/128
PiB)
[  885.868789] sd 5:0:0:0: [sdf] 4096-byte physical blocks
[  887.869495] sd 5:0:0:0: [sdf] Write Protect is off
[  887.869498] sd 5:0:0:0: [sdf] Mode Sense: 67 00 10 08
[  891.870798] sd 5:0:0:0: [sdf] Write cache: enabled, read cache: enabled, supports
DPO and FUA
[  922.741387] sd 5:0:0:0: tag#11 uas_eh_abort_handler 0 uas-tag 1 inflight: IN
[  922.741393] sd 5:0:0:0: tag#11 CDB: Report supported operation codes a3 0c 01 12
00 00 00 00 02 00 00 00
[  922.757393] scsi host5: uas_eh_device_reset_handler start
[  922.887214] usb 6-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[  922.917578] scsi host5: uas_eh_device_reset_handler success
[  953.465374] scsi host5: uas_eh_device_reset_handler start
[  953.465837] sd 5:0:0:0: tag#11 uas_zap_pending 0 uas-tag 1 inflight:
[  953.465842] sd 5:0:0:0: tag#11 CDB: Report supported operation codes a3 0c 01 12
00 00 00 00 02 00 00 00
[  953.595235] usb 6-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
--- snap ---


So, when I blacklist UAS for the drive:
--- snip ---
$  cat /sys/module/usb_storage/parameters/quirks
054c:087d:u,054c:0c4f:u
--- snap ---


dmesg shows this when attaching the PSZ-HA2T:
--- snip ---
[87130.955521] usb 4-2: new SuperSpeed Gen 1 USB device number 13 using xhci_hcd
[87130.979047] usb 4-2: New USB device found, idVendor=054c, idProduct=087d,
bcdDevice= 0.0a
[87130.979051] usb 4-2: New USB device strings: Mfr=10, Product=11, SerialNumber=3
[87130.979052] usb 4-2: Product: Portable Storage
[87130.979053] usb 4-2: Manufacturer: Sony
[87130.979054] usb 4-2: SerialNumber: 230877290443
[87130.983677] usb 4-2: UAS is blacklisted for this device, using usb-storage instead
[87130.983679] usb-storage 4-2:1.0: USB Mass Storage device detected
[87130.983753] usb-storage 4-2:1.0: Quirks match for vid 054c pid 087d: 800000
[87130.983770] scsi host5: usb-storage 4-2:1.0
[87134.003728] scsi 5:0:0:0: Direct-Access     Sony     PSZ-H            320: PQ: 0
ANSI: 6
[87134.003936] sd 5:0:0:0: Attached scsi generic sg7 type 0
[87140.006762] sd 5:0:0:0: [sdf] Spinning up disk...
[87143.042934] ................not responding...
[87254.168509] sd 5:0:0:0: [sdf] Read Capacity(10) failed: Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[87254.168513] sd 5:0:0:0: [sdf] Sense Key : Not Ready [current]
[87254.168515] sd 5:0:0:0: [sdf] Add. Sense: Logical unit is in process of becoming ready
[87254.168518] sd 5:0:0:0: [sdf] 0 512-byte logical blocks: (0 B/0 B)
[87254.168519] sd 5:0:0:0: [sdf] 0-byte physical blocks
[87256.170408] sd 5:0:0:0: [sdf] Test WP failed, assume Write Enabled
[87258.172158] sd 5:0:0:0: [sdf] Asking for cache data failed
[87258.172172] sd 5:0:0:0: [sdf] Assuming drive cache: write through
[87268.192507] sd 5:0:0:0: [sdf] Spinning up disk...
--- snap ---


So UAS might not be the problem after all. Particularly because when attaching the
drive in Windows 10 I notice some popup saying something about "UAS".


Since the drives do work under Windows with USB 3.0 I'm still guessing that the
drives fail to correctly implement parts of USB 3.0.


Is there any way to pinpoint the problem(s)? Or do I have to try all possible quirk
combinations and hope I find the one that's working?


Any insights on this would greatly be appreciated!


Thanks and regards -- Till
-- 
Dipl.-Inform. Till Dörges                  doerges@pre-sense.de
PRESENSE Technologies GmbH             Nagelsweg 41, D-20097 HH
Geschäftsführer/Managing Directors       AG Hamburg, HRB 107844
Till Dörges, Jürgen Sander               USt-IdNr.: DE263765024

             reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-23 14:57 Till Dörges [this message]
2020-05-23 15:48 ` Alan Stern
2020-05-23 20:05   ` Till Dörges
2020-05-23 20:33     ` Alan Stern
2020-05-24  7:46       ` Till Dörges
2020-05-24 14:34         ` Alan Stern

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=512118bc-e639-2387-e608-56b7e30fc3b2@pre-sense.de \
    --to=doerges@pre-sense.de \
    --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

Linux-USB Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-usb/0 linux-usb/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-usb linux-usb/ https://lore.kernel.org/linux-usb \
		linux-usb@vger.kernel.org
	public-inbox-index linux-usb

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-usb


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git