Issues with LaCie USB3 drive and UAS

Issues with LaCie USB3 drive and UAS

[David C. Partridge]

LUbuntu 20.04.1

root@charon:/home/amonra# lsusb
Bus 002 Device 006: ID 059f:105f LaCie, Ltd 2Big Quadra USB3

Trying to format the above drive using mkfs.ext4 /dev/sdc2

Initially got a 120s Kernel timeout which I resolved by setting the timeout
to 0

However I got LOTS of message groups in the system log looking like this:

Nov 04 06:18:51 charon kernel: scsi host5: uas_eh_device_reset_handler start
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#0 uas_zap_pending 0
uas-tag 1 inflight: 
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#0 CDB: Write Same(10)
41 00 e8 ea 47 fc 00 00 04 00
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#1 uas_zap_pending 0
uas-tag 2 inflight: 
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#1 CDB: Write Same(10)
41 00 e8 e6 48 00 00 ff ff 00
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#2 uas_zap_pending 0
uas-tag 3 inflight: 
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#2 CDB: Write Same(10)
41 00 e8 e9 47 fd 00 ff ff 00
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#3 uas_zap_pending 0
uas-tag 4 inflight: 
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#3 CDB: Write Same(10)
41 00 e8 e8 47 fe 00 ff ff 00
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#4 uas_zap_pending 0
uas-tag 5 inflight: 
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#4 CDB: Write Same(10)
41 00 e8 e7 47 ff 00 ff ff 00
Nov 04 06:18:51 charon kernel: usb 2-1: reset SuperSpeed Gen 1 USB device
number 6 using xhci_hcd
Nov 04 06:18:51 charon kernel: scsi host5: uas_eh_device_reset_handler
success
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#0 FAILED Result:
hostbyte=DID_RESET driverbyte=DRIVER_OK
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#0 CDB: Write Same(10)
41 00 e8 ea 47 fc 00 00 04 00
Nov 04 06:18:51 charon kernel: blk_update_request: I/O error, dev sdc,
sector 3907667964 op 0x9:(WRITE_ZEROES) flags 0x1000800 phys_seg 0 prio
class 0
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#1 FAILED Result:
hostbyte=DID_RESET driverbyte=DRIVER_OK
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#1 CDB: Write Same(10)
41 00 e8 e6 48 00 00 ff ff 00
Nov 04 06:18:51 charon kernel: blk_update_request: I/O error, dev sdc,
sector 3907405824 op 0x9:(WRITE_ZEROES) flags 0x1000000 phys_seg 0 prio
class 0
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#2 FAILED Result:
hostbyte=DID_RESET driverbyte=DRIVER_OK
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#2 CDB: Write Same(10)
41 00 e8 e9 47 fd 00 ff ff 00
Nov 04 06:18:51 charon kernel: blk_update_request: I/O error, dev sdc,
sector 3907602429 op 0x9:(WRITE_ZEROES) flags 0x1000000 phys_seg 0 prio
class 0
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#3 FAILED Result:
hostbyte=DID_RESET driverbyte=DRIVER_OK
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#3 CDB: Write Same(10)
41 00 e8 e8 47 fe 00 ff ff 00
Nov 04 06:18:51 charon kernel: blk_update_request: I/O error, dev sdc,
sector 3907536894 op 0x9:(WRITE_ZEROES) flags 0x1000000 phys_seg 0 prio
class 0
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#4 FAILED Result:
hostbyte=DID_RESET driverbyte=DRIVER_OK
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#4 CDB: Write Same(10)
41 00 e8 e7 47 ff 00 ff ff 00
Nov 04 06:18:51 charon kernel: blk_update_request: I/O error, dev sdc,
sector 3907471359 op 0x9:(WRITE_ZEROES) flags 0x1000000 phys_seg 0 prio
class 0

and while the command apparently ended cleanly it took a *very long* time
(hours)

root@charon:/home/amonra# mkfs.ext4 /dev/sdc2
mke2fs 1.45.5 (07-Jan-2020)
Creating filesystem with 976701696 4k blocks and 244178944 inodes
Filesystem UUID: f45b0cd6-131a-4a3a-988f-c5a848611445
Superblock backups stored on blocks: 
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
    4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 
    102400000, 214990848, 512000000, 550731776, 644972544

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done       

root@charon:/home/amonra# fsck /dev/sdc2
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
/dev/sdc2: clean, 11/244178944 files, 15615751/976701696 blocks
root@charon:/home/amonra#

I'm not 100% convinced it did ...

If I just attach and mount the drive I get:

Nov 08 10:25:40 charon kernel: EXT4-fs (sdc2): recovery complete
Nov 08 10:25:40 charon kernel: EXT4-fs (sdc2): mounted filesystem with
ordered data mode. Opts: (null)
Nov 08 10:26:12 charon kernel: sd 5:0:0:0: [sdc] tag#17 uas_eh_abort_handler
0 uas-tag 1 inflight: OUT 
Nov 08 10:26:12 charon kernel: sd 5:0:0:0: [sdc] tag#17 CDB: Write Same(10)
41 00 00 06 b7 98 00 10 00 00
Nov 08 10:26:12 charon kernel: scsi host5: uas_eh_device_reset_handler start
Nov 08 10:26:12 charon kernel: usb 2-1: reset SuperSpeed Gen 1 USB device
number 2 using xhci_hcd
Nov 08 10:26:12 charon kernel: scsi host5: uas_eh_device_reset_handler
success

I then see a lot of message groups like this in the log:

Nov 08 10:31:21 charon kernel: INFO: task jbd2/sdc2-8:104742 blocked for
more than 241 seconds.
Nov 08 10:31:21 charon kernel:       Not tainted 5.4.0-52-generic #57-Ubuntu
Nov 08 10:31:21 charon kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 08 10:31:21 charon kernel: jbd2/sdc2-8     D    0 104742      2
0x80004000
Nov 08 10:31:21 charon kernel: Call Trace:
Nov 08 10:31:21 charon kernel:  __schedule+0x2e3/0x740
Nov 08 10:31:21 charon kernel:  schedule+0x42/0xb0
Nov 08 10:31:21 charon kernel:  jbd2_journal_commit_transaction+0x258/0x17e8
Nov 08 10:31:21 charon kernel:  ? __switch_to_asm+0x40/0x70
Nov 08 10:31:21 charon kernel:  ? __switch_to_asm+0x34/0x70
Nov 08 10:31:21 charon kernel:  ? __switch_to_asm+0x40/0x70
Nov 08 10:31:21 charon kernel:  ? __switch_to_asm+0x34/0x70
Nov 08 10:31:21 charon kernel:  ? __switch_to_asm+0x40/0x70
Nov 08 10:31:21 charon kernel:  ? __switch_to_asm+0x34/0x70
Nov 08 10:31:21 charon kernel:  ? __switch_to_asm+0x40/0x70
Nov 08 10:31:21 charon kernel:  ? __switch_to_asm+0x40/0x70
Nov 08 10:31:21 charon kernel:  ? __switch_to_asm+0x34/0x70
Nov 08 10:31:21 charon kernel:  ? __switch_to_asm+0x34/0x70
Nov 08 10:31:21 charon kernel:  ? wait_woken+0x80/0x80
Nov 08 10:31:21 charon kernel:  ? try_to_del_timer_sync+0x54/0x80
Nov 08 10:31:21 charon kernel:  kjournald2+0xb6/0x280
Nov 08 10:31:21 charon kernel:  ? wait_woken+0x80/0x80
Nov 08 10:31:21 charon kernel:  kthread+0x104/0x140
Nov 08 10:31:21 charon kernel:  ? commit_timeout+0x20/0x20
Nov 08 10:31:21 charon kernel:  ? kthread_park+0x90/0x90
Nov 08 10:31:21 charon kernel:  ret_from_fork+0x35/0x40
Nov 08 10:31:21 charon kernel: INFO: task ext4lazyinit:104744 blocked for
more than 241 seconds.
Nov 08 10:31:21 charon kernel:       Not tainted 5.4.0-52-generic #57-Ubuntu
Nov 08 10:31:21 charon kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 08 10:31:21 charon kernel: ext4lazyinit    D    0 104744      2
0x80004000
Nov 08 10:31:21 charon kernel: Call Trace:
Nov 08 10:31:21 charon kernel:  __schedule+0x2e3/0x740
Nov 08 10:31:21 charon kernel:  schedule+0x42/0xb0
Nov 08 10:31:21 charon kernel:  schedule_timeout+0x10e/0x160
Nov 08 10:31:21 charon kernel:  io_schedule_timeout+0x1e/0x50
Nov 08 10:31:21 charon kernel:  wait_for_completion_io+0xb1/0x120
Nov 08 10:31:21 charon kernel:  ? wake_up_q+0x70/0x70
Nov 08 10:31:21 charon kernel:  submit_bio_wait+0x60/0x90
Nov 08 10:31:21 charon kernel:  blkdev_issue_zeroout+0x13f/0x220
Nov 08 10:31:21 charon kernel:  ext4_init_inode_table+0x195/0x386
Nov 08 10:31:21 charon kernel:  ext4_lazyinit_thread+0x2c7/0x3b0
Nov 08 10:31:21 charon kernel:  kthread+0x104/0x140
Nov 08 10:31:21 charon kernel:  ? ext4_unregister_li_request+0x70/0x70
Nov 08 10:31:21 charon kernel:  ? kthread_park+0x90/0x90
Nov 08 10:31:21 charon kernel:  ret_from_fork+0x35/0x40
Nov 08 10:32:14 charon kernel: scsi host5: uas_eh_device_reset_handler start
Nov 08 10:32:14 charon kernel: sd 5:0:0:0: [sdc] tag#9 uas_zap_pending 0
uas-tag 1 inflight: 
Nov 08 10:32:14 charon kernel: sd 5:0:0:0: [sdc] tag#9 CDB: Write Same(10)
41 00 00 06 b7 98 00 10 00 00
Nov 08 10:32:14 charon kernel: usb 2-1: reset SuperSpeed Gen 1 USB device
number 2 using xhci_hcd
Nov 08 10:32:14 charon kernel: scsi host5: uas_eh_device_reset_handler
success
Nov 08 10:32:28 charon systemd[1]: Started Run anacron jobs.
Nov 08 10:32:28 charon anacron[107039]: Anacron 2.3 started on 2020-11-08
Nov 08 10:32:28 charon anacron[107039]: Normal exit (0 jobs run)
Nov 08 10:32:28 charon systemd[1]: anacron.service: Succeeded.
Nov 08 10:33:22 charon kernel: INFO: task jbd2/sdc2-8:104742 blocked for
more than 362 seconds.
Nov 08 10:33:22 charon kernel:       Not tainted 5.4.0-52-generic #57-Ubuntu
Nov 08 10:33:22 charon kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 08 10:33:22 charon kernel: jbd2/sdc2-8     D    0 104742      2
0x80004000
Nov 08 10:33:22 charon kernel: Call Trace:
Nov 08 10:33:22 charon kernel:  __schedule+0x2e3/0x740
Nov 08 10:33:22 charon kernel:  schedule+0x42/0xb0
Nov 08 10:33:22 charon kernel:  jbd2_journal_commit_transaction+0x258/0x17e8
Nov 08 10:33:22 charon kernel:  ? __switch_to_asm+0x40/0x70
Nov 08 10:33:22 charon kernel:  ? __switch_to_asm+0x34/0x70
Nov 08 10:33:22 charon kernel:  ? __switch_to_asm+0x40/0x70
Nov 08 10:33:22 charon kernel:  ? __switch_to_asm+0x34/0x70
Nov 08 10:33:22 charon kernel:  ? __switch_to_asm+0x40/0x70
Nov 08 10:33:22 charon kernel:  ? __switch_to_asm+0x34/0x70
Nov 08 10:33:22 charon kernel:  ? __switch_to_asm+0x40/0x70
Nov 08 10:33:22 charon kernel:  ? __switch_to_asm+0x40/0x70
Nov 08 10:33:22 charon kernel:  ? __switch_to_asm+0x34/0x70
Nov 08 10:33:22 charon kernel:  ? __switch_to_asm+0x34/0x70
Nov 08 10:33:22 charon kernel:  ? wait_woken+0x80/0x80
Nov 08 10:33:22 charon kernel:  ? try_to_del_timer_sync+0x54/0x80
Nov 08 10:33:22 charon kernel:  kjournald2+0xb6/0x280
Nov 08 10:33:22 charon kernel:  ? wait_woken+0x80/0x80
Nov 08 10:33:22 charon kernel:  kthread+0x104/0x140
Nov 08 10:33:22 charon kernel:  ? commit_timeout+0x20/0x20
Nov 08 10:33:22 charon kernel:  ? kthread_park+0x90/0x90
Nov 08 10:33:22 charon kernel:  ret_from_fork+0x35/0x40
Nov 08 10:33:22 charon kernel: INFO: task ext4lazyinit:104744 blocked for
more than 362 seconds.
Nov 08 10:33:22 charon kernel:       Not tainted 5.4.0-52-generic #57-Ubuntu
Nov 08 10:33:22 charon kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 08 10:33:22 charon kernel: ext4lazyinit    D    0 104744      2
0x80004000
Nov 08 10:33:22 charon kernel: Call Trace:
Nov 08 10:33:22 charon kernel:  __schedule+0x2e3/0x740
Nov 08 10:33:22 charon kernel:  schedule+0x42/0xb0
Nov 08 10:33:22 charon kernel:  schedule_timeout+0x10e/0x160
Nov 08 10:33:22 charon kernel:  io_schedule_timeout+0x1e/0x50
Nov 08 10:33:22 charon kernel:  wait_for_completion_io+0xb1/0x120
Nov 08 10:33:22 charon kernel:  ? wake_up_q+0x70/0x70
Nov 08 10:33:22 charon kernel:  submit_bio_wait+0x60/0x90
Nov 08 10:33:22 charon kernel:  blkdev_issue_zeroout+0x13f/0x220
Nov 08 10:33:22 charon kernel:  ext4_init_inode_table+0x195/0x386
Nov 08 10:33:22 charon kernel:  ext4_lazyinit_thread+0x2c7/0x3b0
Nov 08 10:33:22 charon kernel:  kthread+0x104/0x140
Nov 08 10:33:22 charon kernel:  ? ext4_unregister_li_request+0x70/0x70
Nov 08 10:33:22 charon kernel:  ? kthread_park+0x90/0x90
Nov 08 10:33:22 charon kernel:  ret_from_fork+0x35/0x40
Nov 08 10:34:15 charon kernel: scsi host5: uas_eh_device_reset_handler start
Nov 08 10:34:15 charon kernel: sd 5:0:0:0: [sdc] tag#1 uas_zap_pending 0
uas-tag 1 inflight: 
Nov 08 10:34:15 charon kernel: sd 5:0:0:0: [sdc] tag#1 CDB: Write Same(10)
41 00 00 06 b7 98 00 10 00 00
Nov 08 10:34:15 charon kernel: usb 2-1: reset SuperSpeed Gen 1 USB device
number 2 using xhci_hcd
Nov 08 10:34:15 charon kernel: scsi host5: uas_eh_device_reset_handler
success

Any guidance and help much appreciated.

David

Re: Issues with LaCie USB3 drive and UAS

[Oliver Neukum]

Am Sonntag, den 08.11.2020, 10:56 +0000 schrieb David C. Partridge:
> LUbuntu 20.04.1
> 
> root@charon:/home/amonra# lsusb
> Bus 002 Device 006: ID 059f:105f LaCie, Ltd 2Big Quadra USB3
> 
> Trying to format the above drive using mkfs.ext4 /dev/sdc2
> 
> Initially got a 120s Kernel timeout which I resolved by setting the timeout
> to 0
> 
> However I got LOTS of message groups in the system log looking like this:
> 
> Nov 04 06:18:51 charon kernel: scsi host5: uas_eh_device_reset_handler start
> Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#0 uas_zap_pending 0
> uas-tag 1 inflight: 
> Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#0 CDB: Write Same(10)
> 41 00 e8 ea 47 fc 00 00 04 00

Write Same? What you are seeing is that the error handling is running
non-stop. I suspect that the device does not understand WRITE SAME.

	Regards
		Oliver

RE: Issues with LaCie USB3 drive and UAS

[David C. Partridge]

I'm sure you are right in your diagnosis (absent any knowledge to the contrary).

Now what's the treatment?  

Would uas black-list provide a work-araound? If so a detailed recipe will be needed by me ...

Fix to the code? Ideal, but takes lots longer, so a work-around may be needed for a while

David


-----Original Message-----
From: Oliver Neukum [mailto:oneukum@suse.com] 
Sent: 09 November 2020 09:30
To: David C. Partridge; linux-usb@vger.kernel.org
Subject: Re: Issues with LaCie USB3 drive and UAS

Am Sonntag, den 08.11.2020, 10:56 +0000 schrieb David C. Partridge:
> LUbuntu 20.04.1
> 
> root@charon:/home/amonra# lsusb
> Bus 002 Device 006: ID 059f:105f LaCie, Ltd 2Big Quadra USB3
> 
> Trying to format the above drive using mkfs.ext4 /dev/sdc2
> 
> Initially got a 120s Kernel timeout which I resolved by setting the timeout
> to 0
> 
> However I got LOTS of message groups in the system log looking like this:
> 
> Nov 04 06:18:51 charon kernel: scsi host5: uas_eh_device_reset_handler start
> Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#0 uas_zap_pending 0
> uas-tag 1 inflight: 
> Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#0 CDB: Write Same(10)
> 41 00 e8 ea 47 fc 00 00 04 00

Write Same? What you are seeing is that the error handling is running
non-stop. I suspect that the device does not understand WRITE SAME.

	Regards
		Oliver

Re: Issues with LaCie USB3 drive and UAS

[Oliver Neukum]

Am Montag, den 09.11.2020, 09:51 +0000 schrieb David C. Partridge:
> I'm sure you are right in your diagnosis (absent any knowledge to the contrary).

It is a guess, merely. Based on long woefull experience with the
quality of some hardware.

> Now what's the treatment?

Use WRITE, not WRITE SAME. That is a task of the SCSI layer, not UAS.

> Would uas black-list provide a work-araound? If so a detailed recipe will be needed by me ...

Indirectly. The storage driver sets no_write_same. UAS does not. It
looks like UAS will need a kernel patch for that.

> Fix to the code? Ideal, but takes lots longer, so a work-around may be needed for a while

Very well. For experimentation, please try blacklisting UAS. If that
fails I have guessed wrong. If it works, I will make a test patch.

	Regards
		Oliver

RE: Issues with LaCie USB3 drive and UAS

[David C. Partridge]

Please could I ask you to provide detailed instructions on how to blacklist UAS for just this device?

Thanks
Daivd

-----Original Message-----
From: Oliver Neukum [mailto:oneukum@suse.com] 
Sent: 09 November 2020 10:14
To: David C. Partridge; linux-usb@vger.kernel.org
Subject: Re: Issues with LaCie USB3 drive and UAS

Am Montag, den 09.11.2020, 09:51 +0000 schrieb David C. Partridge:
> I'm sure you are right in your diagnosis (absent any knowledge to the contrary).

It is a guess, merely. Based on long woefull experience with the
quality of some hardware.

> Now what's the treatment?

Use WRITE, not WRITE SAME. That is a task of the SCSI layer, not UAS.

> Would uas black-list provide a work-araound? If so a detailed recipe will be needed by me ...

Indirectly. The storage driver sets no_write_same. UAS does not. It
looks like UAS will need a kernel patch for that.

> Fix to the code? Ideal, but takes lots longer, so a work-around may be needed for a while

Very well. For experimentation, please try blacklisting UAS. If that
fails I have guessed wrong. If it works, I will make a test patch.

	Regards
		Oliver

RE: Issues with LaCie USB3 drive and UAS

[David C. Partridge]

Update: I found out how to do it! 

Created /etc/modprobe.d/blacklist_uas.conf containing text:

options usb-storage quirks=059f:105f:u

followed by: update-initramfs -u
and rebooted.

Now the device works fine and mkfs.ext4 finishes in seconds rather than hours.

David
-----Original Message-----
From: David C. Partridge [mailto:david.partridge@perdrix.co.uk] 
Sent: 09 November 2020 11:21
To: 'Oliver Neukum'; linux-usb@vger.kernel.org
Subject: RE: Issues with LaCie USB3 drive and UAS

Please could I ask you to provide detailed instructions on how to blacklist UAS for just this device?

Thanks
Daivd

-----Original Message-----
From: Oliver Neukum [mailto:oneukum@suse.com] 
Sent: 09 November 2020 10:14
To: David C. Partridge; linux-usb@vger.kernel.org
Subject: Re: Issues with LaCie USB3 drive and UAS

Am Montag, den 09.11.2020, 09:51 +0000 schrieb David C. Partridge:
> I'm sure you are right in your diagnosis (absent any knowledge to the contrary).

It is a guess, merely. Based on long woefull experience with the
quality of some hardware.

> Now what's the treatment?

Use WRITE, not WRITE SAME. That is a task of the SCSI layer, not UAS.

> Would uas black-list provide a work-araound? If so a detailed recipe will be needed by me ...

Indirectly. The storage driver sets no_write_same. UAS does not. It
looks like UAS will need a kernel patch for that.

> Fix to the code? Ideal, but takes lots longer, so a work-around may be needed for a while

Very well. For experimentation, please try blacklisting UAS. If that
fails I have guessed wrong. If it works, I will make a test patch.

	Regards
		Oliver

RE: Issues with LaCie USB3 drive and UAS

[David C. Partridge]

It would appear that there are an awful lot of Seagate USB3-SATA controllers
out that don't get on too well with uas :(  (LaCie is owned by Seagate).

David

-----Original Message-----
From: David C. Partridge [mailto:david.partridge@perdrix.co.uk] 
Sent: 09 November 2020 15:21
To: 'Oliver Neukum'; linux-usb@vger.kernel.org
Subject: RE: Issues with LaCie USB3 drive and UAS

Update: I found out how to do it! 

Created /etc/modprobe.d/blacklist_uas.conf containing text:

options usb-storage quirks=059f:105f:u

followed by: update-initramfs -u
and rebooted.

Now the device works fine and mkfs.ext4 finishes in seconds rather than hours.

David
-----Original Message-----
From: David C. Partridge [mailto:david.partridge@perdrix.co.uk] 
Sent: 09 November 2020 11:21
To: 'Oliver Neukum'; linux-usb@vger.kernel.org
Subject: RE: Issues with LaCie USB3 drive and UAS

Please could I ask you to provide detailed instructions on how to blacklist UAS for just this device?

Thanks
Daivd

-----Original Message-----
From: Oliver Neukum [mailto:oneukum@suse.com] 
Sent: 09 November 2020 10:14
To: David C. Partridge; linux-usb@vger.kernel.org
Subject: Re: Issues with LaCie USB3 drive and UAS

Am Montag, den 09.11.2020, 09:51 +0000 schrieb David C. Partridge:
> I'm sure you are right in your diagnosis (absent any knowledge to the contrary).

It is a guess, merely. Based on long woefull experience with the
quality of some hardware.

> Now what's the treatment?

Use WRITE, not WRITE SAME. That is a task of the SCSI layer, not UAS.

> Would uas black-list provide a work-araound? If so a detailed recipe will be needed by me ...

Indirectly. The storage driver sets no_write_same. UAS does not. It
looks like UAS will need a kernel patch for that.

> Fix to the code? Ideal, but takes lots longer, so a work-around may be needed for a while

Very well. For experimentation, please try blacklisting UAS. If that
fails I have guessed wrong. If it works, I will make a test patch.

	Regards
		Oliver

Re: Issues with LaCie USB3 drive and UAS

[Oliver Neukum]

[-- Attachment #1: Type: text/plain, Size: 524 bytes --]

Am Montag, den 09.11.2020, 15:21 +0000 schrieb David C. Partridge:
> Update: I found out how to do it! 
> 
> Created /etc/modprobe.d/blacklist_uas.conf containing text:
> 
> options usb-storage quirks=059f:105f:u
> 
> followed by: update-initramfs -u
> and rebooted.
> 
> Now the device works fine and mkfs.ext4 finishes in seconds rather than hours.

Hi,

this is good for now. Could you test the attached patch and replace the
"u" in your module options for usb-storage with a "k" (for the new
quirk)?

	Regards
		Oliver


[-- Attachment #2: 0001-USB-UAS-introduce-a-quirk-to-set-no_write_same.patch --]
[-- Type: text/x-patch, Size: 2087 bytes --]

From 53a5cacbf61ce6a4935723849ad602f38d8f9a52 Mon Sep 17 00:00:00 2001
From: Oliver Neukum <oneukum@suse.com>
Date: Wed, 11 Nov 2020 12:37:15 +0100
Subject: [PATCH] USB: UAS: introduce a quirk to set no_write_same

UAS does not share the pessimistic assumption storage
is making that devices cannot deal with WRITE_SAME.
A few devices supported by UAS, are reported to not
deal well with WRITE_SAME. Those need a quirk.

Signed-off-by: Oliver Neukum <oneukum@suse.com>
---
 drivers/usb/storage/uas.c | 3 +++
 drivers/usb/storage/usb.c | 3 +++
 include/linux/usb_usual.h | 2 ++
 3 files changed, 8 insertions(+)

diff --git a/drivers/usb/storage/uas.c b/drivers/usb/storage/uas.c
index c8a577309e8f..1e1daa3da4b5 100644
--- a/drivers/usb/storage/uas.c
+++ b/drivers/usb/storage/uas.c
@@ -874,6 +874,9 @@ static int uas_slave_configure(struct scsi_device *sdev)
 	if (devinfo->flags & US_FL_NO_READ_CAPACITY_16)
 		sdev->no_read_capacity_16 = 1;
 
+	/* Some disks cannot handle WRITE_SAME */
+	if (devinfo->flags & US_FL_NO_SAME)
+		sdev->no_write_same = 1;
 	/*
 	 * Some disks return the total number of blocks in response
 	 * to READ CAPACITY rather than the highest block number.
diff --git a/drivers/usb/storage/usb.c b/drivers/usb/storage/usb.c
index c2ef367cf257..08b469511043 100644
--- a/drivers/usb/storage/usb.c
+++ b/drivers/usb/storage/usb.c
@@ -541,6 +541,9 @@ void usb_stor_adjust_quirks(struct usb_device *udev, unsigned long *fflags)
 		case 'j':
 			f |= US_FL_NO_REPORT_LUNS;
 			break;
+		case 'k':
+			f |= US_FL_NO_SAME;
+			break;
 		case 'l':
 			f |= US_FL_NOT_LOCKABLE;
 			break;
diff --git a/include/linux/usb_usual.h b/include/linux/usb_usual.h
index 4a19ac3f24d0..6b03fdd69d27 100644
--- a/include/linux/usb_usual.h
+++ b/include/linux/usb_usual.h
@@ -84,6 +84,8 @@
 		/* Cannot handle REPORT_LUNS */			\
 	US_FLAG(ALWAYS_SYNC, 0x20000000)			\
 		/* lies about caching, so always sync */	\
+	US_FLAG(NO_SAME, 0x40000000)				\
+		/* Cannot handle WRITE_SAME */			\
 
 #define US_FLAG(name, value)	US_FL_##name = value ,
 enum { US_DO_ALL_FLAGS };
-- 
2.26.2

RE: Issues with LaCie USB3 drive and UAS

[David C. Partridge]

Oliver I'd love to test your patch - theres only one catch - I haven't a clue how to begin to do that.

I managed to install LUbuntu 20.04.1 but applying source patches to the kernel is a bit beyond my skill level.

PS out of curiosity why 'k' for doesn't support Write Same?

D.

-----Original Message-----
From: Oliver Neukum [mailto:oneukum@suse.com] 
Sent: 11 November 2020 11:44
To: David C. Partridge; linux-usb@vger.kernel.org
Subject: Re: Issues with LaCie USB3 drive and UAS

Am Montag, den 09.11.2020, 15:21 +0000 schrieb David C. Partridge:
> Update: I found out how to do it! 
> 
> Created /etc/modprobe.d/blacklist_uas.conf containing text:
> 
> options usb-storage quirks=059f:105f:u
> 
> followed by: update-initramfs -u
> and rebooted.
> 
> Now the device works fine and mkfs.ext4 finishes in seconds rather than hours.

Hi,

this is good for now. Could you test the attached patch and replace the "u" in your module options for usb-storage with a "k" (for the new quirk)?

	Regards
		Oliver

Re: Issues with LaCie USB3 drive and UAS

[Oliver Neukum]

Am Mittwoch, den 11.11.2020, 15:50 +0000 schrieb David C. Partridge:
> Oliver I'd love to test your patch - theres only one catch - I haven't a clue how to begin to do that.
> 
> I managed to install LUbuntu 20.04.1 but applying source patches to the kernel is a bit beyond my skill level.

Hi,

do you need general help building a kernel or is there a specific
issue?

> PS out of curiosity why 'k' for doesn't support Write Same?

We are running out of letters for quirks.

	Regards
		Oliver

RE: Issues with LaCie USB3 drive and UAS

[David C. Partridge]

I think I need the remedial course ...  I've never done that!

D

-----Original Message-----
From: Oliver Neukum [mailto:oneukum@suse.com] 
Sent: 11 November 2020 19:18
To: David C. Partridge; linux-usb@vger.kernel.org
Subject: Re: Issues with LaCie USB3 drive and UAS

Am Mittwoch, den 11.11.2020, 15:50 +0000 schrieb David C. Partridge:
> Oliver I'd love to test your patch - theres only one catch - I haven't a clue how to begin to do that.
> 
> I managed to install LUbuntu 20.04.1 but applying source patches to the kernel is a bit beyond my skill level.

Hi,

do you need general help building a kernel or is there a specific
issue?

> PS out of curiosity why 'k' for doesn't support Write Same?

We are running out of letters for quirks.

	Regards
		Oliver

Re: Issues with LaCie USB3 drive and UAS

[Oliver Neukum]

Am Mittwoch, den 11.11.2020, 20:54 +0000 schrieb David C. Partridge:
> I think I need the remedial course ...  I've never done that!
> 

Hi,

I just this change can be submitted based on logs. Could you please
send "dmesg -v" with the problematic device attached?

	Regards
		Oliver

RE: Issues with LaCie USB3 drive and UAS

[David C. Partridge]

Hi Oliver

I'm still trying to build a kernel with your patch applied but my Ubuntu system isn't cooperating :(

See the sorry story at https://ubuntuforums.org/showthread.php?t=2453530

Regards and thank you again.
David

-----Original Message-----
From: Oliver Neukum [mailto:oneukum@suse.com] 
Sent: 11 November 2020 11:44
To: David C. Partridge; linux-usb@vger.kernel.org
Subject: Re: Issues with LaCie USB3 drive and UAS

Am Montag, den 09.11.2020, 15:21 +0000 schrieb David C. Partridge:
> Update: I found out how to do it! 
> 
> Created /etc/modprobe.d/blacklist_uas.conf containing text:
> 
> options usb-storage quirks=059f:105f:u
> 
> followed by: update-initramfs -u
> and rebooted.
> 
> Now the device works fine and mkfs.ext4 finishes in seconds rather than hours.

Hi,

this is good for now. Could you test the attached patch and replace the "u" in your module options for usb-storage with a "k" (for the new quirk)?

	Regards
		Oliver

Re: Issues with LaCie USB3 drive and UAS

[Oliver Neukum]

Am Mittwoch, den 25.11.2020, 12:25 +0000 schrieb David C. Partridge:
> Hi Oliver
> 
> I'm still trying to build a kernel with your patch applied but my Ubuntu system isn't cooperating :(
> 
> See the sorry story at 
> https://ubuntuforums.org/showthread.php?t=2453530make ARCH=x86 mrproper
Try using

make ARCH=x86 mrproper

right before

LANG=C fakeroot debian/rules binary

	HTH
		Oliver

RE: Issues with LaCie USB3 drive and UAS

[David C. Partridge]

I tried that but that wiped out the debian folder :(

-----Original Message-----
From: Oliver Neukum [mailto:oneukum@suse.com] 
Sent: 26 November 2020 08:25
To: David C. Partridge; linux-usb@vger.kernel.org
Subject: Re: Issues with LaCie USB3 drive and UAS

Am Mittwoch, den 25.11.2020, 12:25 +0000 schrieb David C. Partridge:
> Hi Oliver
> 
> I'm still trying to build a kernel with your patch applied but my Ubuntu system isn't cooperating :(
> 
> See the sorry story at 
> https://ubuntuforums.org/showthread.php?t=2453530make ARCH=x86 mrproper
Try using

make ARCH=x86 mrproper

right before

LANG=C fakeroot debian/rules binary

	HTH
		Oliver

Re: Issues with LaCie USB3 drive and UAS

[Oliver Neukum]

Am Donnerstag, den 26.11.2020, 09:33 +0000 schrieb David C. Partridge:
> I tried that but that wiped out the debian folder :(

Hi,

that is a pronblem as I do not use Debian, nor know a lot about it.
You can try "make clean" instead of "make mrproper" , as it is milder.
And yes, this is programmer humor.

	HTH
		Oliver

RE: Issues with LaCie USB3 drive and UAS

[David C. Partridge]

A helpful person on the Ubuntu forums sent me a patched usb-storage.ko that was built using your patch file.

Here's what the system had to say when I tried it with the modified /etc/modprobe.d/blacklist-uas.conf w/r:

    options usb-storage quirks=059f:105f:k

Dec 02 11:02:01 charon kernel: usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Dec 02 11:02:01 charon kernel: usb 2-1: New USB device found, idVendor=059f, idProduct=105f, bcdDevice= 0.01
Dec 02 11:02:01 charon kernel: usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Dec 02 11:02:01 charon kernel: usb 2-1: Product: 2Big Quadra USB3
Dec 02 11:02:01 charon kernel: usb 2-1: Manufacturer: LaCie
Dec 02 11:02:01 charon kernel: usb 2-1: SerialNumber: 00000000250e9e711084
Dec 02 11:02:01 charon mtp-probe[2490]: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
Dec 02 11:02:01 charon mtp-probe[2490]: bus: 2, device: 2 was not an MTP device
Dec 02 11:02:01 charon kernel: usb_storage: loading out-of-tree module taints kernel.
Dec 02 11:02:01 charon kernel: usb_storage: module verification failed: signature and/or required key missing - tainting kernel
Dec 02 11:02:01 charon kernel: usbcore: registered new interface driver usb-storage
Dec 02 11:02:01 charon kernel: scsi host5: uas
Dec 02 11:02:01 charon kernel: scsi 5:0:0:0: Direct-Access     LaCie    2Big Quadra v3   051E PQ: 0 ANSI: 6
Dec 02 11:02:01 charon kernel: usbcore: registered new interface driver uas
Dec 02 11:02:01 charon kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0
Dec 02 11:02:01 charon mtp-probe[2499]: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
Dec 02 11:02:01 charon mtp-probe[2499]: bus: 2, device: 2 was not an MTP device
Dec 02 11:02:01 charon kernel: sd 5:0:0:0: [sdc] 7814025564 512-byte logical blocks: (4.00 TB/3.64 TiB)
Dec 02 11:02:01 charon kernel: sd 5:0:0:0: [sdc] Write Protect is off
Dec 02 11:02:01 charon kernel: sd 5:0:0:0: [sdc] Mode Sense: 43 00 00 00
Dec 02 11:02:01 charon kernel: sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec 02 11:02:17 charon kernel: usb 2-1: USB disconnect, device number 2
Dec 02 11:02:17 charon kernel: sd 5:0:0:0: [sdc] Optimal transfer size 33553920 bytes
Dec 02 11:02:18 charon kernel: sd 5:0:0:0: [sdc] Read Capacity(16) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Dec 02 11:02:18 charon kernel: sd 5:0:0:0: [sdc] Sense not available.
Dec 02 11:02:18 charon kernel: sd 5:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Dec 02 11:02:18 charon kernel: sd 5:0:0:0: [sdc] Sense not available.
Dec 02 11:02:18 charon kernel: sd 5:0:0:0: [sdc] 0 512-byte logical blocks: (0 B/0 B)

Regards
David
-----Original Message-----
From: Oliver Neukum [mailto:oneukum@suse.com] 
Sent: 26 November 2020 10:22
To: David C. Partridge; linux-usb@vger.kernel.org
Subject: Re: Issues with LaCie USB3 drive and UAS

Am Donnerstag, den 26.11.2020, 09:33 +0000 schrieb David C. Partridge:
> I tried that but that wiped out the debian folder :(

Hi,

that is a pronblem as I do not use Debian, nor know a lot about it.
You can try "make clean" instead of "make mrproper" , as it is milder.
And yes, this is programmer humor.

	HTH
		Oliver

Re: Issues with LaCie USB3 drive and UAS

[Oliver Neukum]

Am Mittwoch, den 02.12.2020, 11:12 +0000 schrieb David C. Partridge:

Hi,


> A helpful person on the Ubuntu forums sent me a patched usb-storage.ko that was built using your patch file.

that is nice to hear, sorry but I am no good with Ubuntu stuff.
However, the problem is that you need uas.ko.

The log is showing a curious failure. Did you disconnect the device?

	Regards
		Oliver

RE: Issues with LaCie USB3 drive and UAS

[David C. Partridge]

Yes I did unplug the USB cable.

I'll ask for the correct file...

Thanks
David

-----Original Message-----
From: Oliver Neukum [mailto:oneukum@suse.com] 
Sent: 02 December 2020 11:38
To: David C. Partridge; linux-usb@vger.kernel.org
Subject: Re: Issues with LaCie USB3 drive and UAS

Am Mittwoch, den 02.12.2020, 11:12 +0000 schrieb David C. Partridge:

Hi,


> A helpful person on the Ubuntu forums sent me a patched usb-storage.ko that was built using your patch file.

that is nice to hear, sorry but I am no good with Ubuntu stuff.
However, the problem is that you need uas.ko.

The log is showing a curious failure. Did you disconnect the device?

	Regards
		Oliver

RE: Issues with LaCie USB3 drive and UAS

[David C. Partridge]

Now with uas.ko	and usb-storage.ko 

Dec 03 02:05:56 charon kernel: usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Dec 03 02:05:56 charon kernel: usb 2-1: New USB device found, idVendor=059f, idProduct=105f, bcdDevice= 0.01
Dec 03 02:05:56 charon kernel: usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Dec 03 02:05:56 charon kernel: usb 2-1: Product: 2Big Quadra USB3
Dec 03 02:05:56 charon kernel: usb 2-1: Manufacturer: LaCie
Dec 03 02:05:56 charon kernel: usb 2-1: SerialNumber: 00000000250e9e711084
Dec 03 02:05:56 charon mtp-probe[3108]: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
Dec 03 02:05:56 charon mtp-probe[3108]: bus: 2, device: 2 was not an MTP device
Dec 03 02:05:56 charon kernel: usb_storage: loading out-of-tree module taints kernel.
Dec 03 02:05:56 charon kernel: usb_storage: module verification failed: signature and/or required key missing - tainting kernel
Dec 03 02:05:56 charon kernel: usbcore: registered new interface driver usb-storage
Dec 03 02:05:56 charon kernel: scsi host5: uas
Dec 03 02:05:56 charon kernel: usbcore: registered new interface driver uas
Dec 03 02:05:56 charon kernel: scsi 5:0:0:0: Direct-Access     LaCie    2Big Quadra v3   051E PQ: 0 ANSI: 6
Dec 03 02:05:56 charon kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0
Dec 03 02:05:56 charon mtp-probe[3117]: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
Dec 03 02:05:56 charon mtp-probe[3117]: bus: 2, device: 2 was not an MTP device
Dec 03 02:05:56 charon kernel: sd 5:0:0:0: [sdc] 7814025564 512-byte logical blocks: (4.00 TB/3.64 TiB)
Dec 03 02:05:56 charon kernel: sd 5:0:0:0: [sdc] Write Protect is off
Dec 03 02:05:56 charon kernel: sd 5:0:0:0: [sdc] Mode Sense: 43 00 00 00
Dec 03 02:05:56 charon kernel: sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec 03 02:06:13 charon kernel: usb 2-1: USB disconnect, device number 2
Dec 03 02:06:13 charon kernel: sd 5:0:0:0: [sdc] Optimal transfer size 33553920 bytes
Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Read Capacity(16) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Sense not available.
Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Sense not available.
Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] 0 512-byte logical blocks: (0 B/0 B)
Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Attached SCSI disk
Dec 03 02:06:15 charon kernel: usb 2-1: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
Dec 03 02:06:15 charon kernel: usb 2-1: New USB device found, idVendor=059f, idProduct=105f, bcdDevice= 0.01
Dec 03 02:06:15 charon kernel: usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Dec 03 02:06:15 charon kernel: usb 2-1: Product: 2Big Quadra USB3
Dec 03 02:06:15 charon kernel: usb 2-1: Manufacturer: LaCie
Dec 03 02:06:15 charon kernel: usb 2-1: SerialNumber: 00000000250e9e711084
Dec 03 02:06:15 charon kernel: scsi host5: uas
Dec 03 02:06:15 charon kernel: scsi 5:0:0:0: Direct-Access     LaCie    2Big Quadra v3   051E PQ: 0 ANSI: 6
Dec 03 02:06:15 charon kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0
Dec 03 02:06:15 charon kernel: sd 5:0:0:0: [sdc] 7814025564 512-byte logical blocks: (4.00 TB/3.64 TiB)
Dec 03 02:06:15 charon kernel: sd 5:0:0:0: [sdc] Write Protect is off
Dec 03 02:06:15 charon kernel: sd 5:0:0:0: [sdc] Mode Sense: 43 00 00 00
Dec 03 02:06:15 charon kernel: sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec 03 02:06:15 charon mtp-probe[3209]: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
Dec 03 02:06:15 charon mtp-probe[3209]: bus: 2, device: 3 was not an MTP device
Dec 03 02:06:15 charon mtp-probe[3212]: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
Dec 03 02:06:15 charon mtp-probe[3212]: bus: 2, device: 3 was not an MTP device
Dec 03 02:06:46 charon kernel: sd 5:0:0:0: tag#28 uas_eh_abort_handler 0 uas-tag 1 inflight: IN 
Dec 03 02:06:46 charon kernel: sd 5:0:0:0: tag#28 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00
Dec 03 02:06:46 charon kernel: scsi host5: uas_eh_device_reset_handler start
Dec 03 02:06:47 charon kernel: usb 2-1: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
Dec 03 02:06:47 charon kernel: scsi host5: uas_eh_device_reset_handler success
Dec 03 02:07:17 charon kernel: scsi host5: uas_eh_device_reset_handler start
Dec 03 02:07:17 charon kernel: sd 5:0:0:0: tag#28 uas_zap_pending 0 uas-tag 1 inflight: 
Dec 03 02:07:17 charon kernel: sd 5:0:0:0: tag#28 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00
Dec 03 02:07:17 charon kernel: usb 2-1: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
Dec 03 02:07:17 charon kernel: scsi host5: uas_eh_device_reset_handler success

-----Original Message-----
From: Oliver Neukum [mailto:oneukum@suse.com] 
Sent: 02 December 2020 11:38
To: David C. Partridge; linux-usb@vger.kernel.org
Subject: Re: Issues with LaCie USB3 drive and UAS

Am Mittwoch, den 02.12.2020, 11:12 +0000 schrieb David C. Partridge:

Hi,


> A helpful person on the Ubuntu forums sent me a patched usb-storage.ko that was built using your patch file.

that is nice to hear, sorry but I am no good with Ubuntu stuff.
However, the problem is that you need uas.ko.

The log is showing a curious failure. Did you disconnect the device?

	Regards
		Oliver

Re: Issues with LaCie USB3 drive and UAS

[Oliver Neukum]

Am Donnerstag, den 03.12.2020, 02:11 +0000 schrieb David C. Partridge:

Hi,

cool, thank your for testing! You having spent so much time
and effort on this, let's go through the log with a fine comb.

> Now with uas.ko	and usb-storage.ko 
> 
> Dec 03 02:05:56 charon kernel: usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
> Dec 03 02:05:56 charon kernel: usb 2-1: New USB device found, idVendor=059f, idProduct=105f, bcdDevice= 0.01
> Dec 03 02:05:56 charon kernel: usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
> Dec 03 02:05:56 charon kernel: usb 2-1: Product: 2Big Quadra USB3
> Dec 03 02:05:56 charon kernel: usb 2-1: Manufacturer: LaCie
> Dec 03 02:05:56 charon kernel: usb 2-1: SerialNumber: 00000000250e9e711084

This is from usbcore. It reports that a new device has been detected.

> Dec 03 02:05:56 charon mtp-probe[3108]: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
> Dec 03 02:05:56 charon mtp-probe[3108]: bus: 2, device: 2 was not an MTP device

From udev. It basically means that it is not a camera to import
pictures from.

> Dec 03 02:05:56 charon kernel: usb_storage: loading out-of-tree module taints kernel.
> Dec 03 02:05:56 charon kernel: usb_storage: module verification failed: signature and/or required key missing - tainting kernel
> Dec 03 02:05:56 charon kernel: usbcore: registered new interface driver usb-storage

The kernel identified the device as storage and udev has loaded drivers
now being probed.

> Dec 03 02:05:56 charon kernel: scsi host5: uas
> Dec 03 02:05:56 charon kernel: usbcore: registered new interface driver uas

UAS is taking the device.

> Dec 03 02:05:56 charon kernel: scsi 5:0:0:0: Direct-Access     LaCie    2Big Quadra v3   051E PQ: 0 ANSI: 6
> Dec 03 02:05:56 charon kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0

It is identified as a disk.

> Dec 03 02:05:56 charon mtp-probe[3117]: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
> Dec 03 02:05:56 charon mtp-probe[3117]: bus: 2, device: 2 was not an MTP device

Again, not a camera.

> Dec 03 02:05:56 charon kernel: sd 5:0:0:0: [sdc] 7814025564 512-byte logical blocks: (4.00 TB/3.64 TiB)
> Dec 03 02:05:56 charon kernel: sd 5:0:0:0: [sdc] Write Protect is off
> Dec 03 02:05:56 charon kernel: sd 5:0:0:0: [sdc] Mode Sense: 43 00 00 00
> Dec 03 02:05:56 charon kernel: sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Its size and caching attributes are determined. Is the size of 4 TB
correct?

> Dec 03 02:06:13 charon kernel: usb 2-1: USB disconnect, device number 2

A disconnect after 17 seconds. Whether this is a bug or not depends on
whether you pulled the plug. Did you?

> Dec 03 02:06:13 charon kernel: sd 5:0:0:0: [sdc] Optimal transfer size 33553920 bytes
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Read Capacity(16) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Sense not available.
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Sense not available.
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] 0 512-byte logical blocks: (0 B/0 B)
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Attached SCSI disk

This has to happen if the device is unavailable.

> Dec 03 02:06:15 charon kernel: usb 2-1: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
> Dec 03 02:06:15 charon kernel: usb 2-1: New USB device found, idVendor=059f, idProduct=105f, bcdDevice= 0.01
> Dec 03 02:06:15 charon kernel: usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
> Dec 03 02:06:15 charon kernel: usb 2-1: Product: 2Big Quadra USB3
> Dec 03 02:06:15 charon kernel: usb 2-1: Manufacturer: LaCie
> Dec 03 02:06:15 charon kernel: usb 2-1: SerialNumber: 00000000250e9e711084
> Dec 03 02:06:15 charon kernel: scsi host5: uas
> Dec 03 02:06:15 charon kernel: scsi 5:0:0:0: Direct-Access     LaCie    2Big Quadra v3   051E PQ: 0 ANSI: 6
> Dec 03 02:06:15 charon kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0
> Dec 03 02:06:15 charon kernel: sd 5:0:0:0: [sdc] 7814025564 512-byte logical blocks: (4.00 TB/3.64 TiB)
> Dec 03 02:06:15 charon kernel: sd 5:0:0:0: [sdc] Write Protect is off
> Dec 03 02:06:15 charon kernel: sd 5:0:0:0: [sdc] Mode Sense: 43 00 00 00
> Dec 03 02:06:15 charon kernel: sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> Dec 03 02:06:15 charon mtp-probe[3209]: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
> Dec 03 02:06:15 charon mtp-probe[3209]: bus: 2, device: 3 was not an MTP device
> Dec 03 02:06:15 charon mtp-probe[3212]: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
> Dec 03 02:06:15 charon mtp-probe[3212]: bus: 2, device: 3 was not an MTP device

This is basically a repeat of the first event.

> Dec 03 02:06:46 charon kernel: sd 5:0:0:0: tag#28 uas_eh_abort_handler 0 uas-tag 1 inflight: IN 
> Dec 03 02:06:46 charon kernel: sd 5:0:0:0: tag#28 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00

This is a SCSI command: REPORT SUPPORTED OPERATION CODES command
Having this command fail is a bit ironic I suppose.

> Dec 03 02:06:46 charon kernel: scsi host5: uas_eh_device_reset_handler start
> Dec 03 02:06:47 charon kernel: usb 2-1: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
> Dec 03 02:06:47 charon kernel: scsi host5: uas_eh_device_reset_handler success
> Dec 03 02:07:17 charon kernel: scsi host5: uas_eh_device_reset_handler start
> Dec 03 02:07:17 charon kernel: sd 5:0:0:0: tag#28 uas_zap_pending 0 uas-tag 1 inflight: 
> Dec 03 02:07:17 charon kernel: sd 5:0:0:0: tag#28 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00
> Dec 03 02:07:17 charon kernel: usb 2-1: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
> Dec 03 02:07:17 charon kernel: scsi host5: uas_eh_device_reset_handler success

And it happens again. This device is seriously buggy. Is it usable
after that or did you just cut the log?

	Regards & Thanks
		Oliver

RE: Issues with LaCie USB3 drive and UAS

[David C. Partridge]

Yes it is a 4TB device.  

> A disconnect after 17 seconds. Whether this is a bug or not depends on whether you pulled the plug. Did you?

No I didn't pull the USB cable at that point

>And it happens again. This device is seriously buggy. Is it usable after that or did you just cut the log?

I just cut the log at that point and pulled the USB cable.

-----Original Message-----
From: Oliver Neukum [mailto:oneukum@suse.com] 
Sent: 03 December 2020 13:17
To: David C. Partridge; linux-usb@vger.kernel.org
Subject: Re: Issues with LaCie USB3 drive and UAS

Am Donnerstag, den 03.12.2020, 02:11 +0000 schrieb David C. Partridge:

Hi,

cool, thank your for testing! You having spent so much time
and effort on this, let's go through the log with a fine comb.

> Now with uas.ko	and usb-storage.ko 
> 
> Dec 03 02:05:56 charon kernel: usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
> Dec 03 02:05:56 charon kernel: usb 2-1: New USB device found, idVendor=059f, idProduct=105f, bcdDevice= 0.01
> Dec 03 02:05:56 charon kernel: usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
> Dec 03 02:05:56 charon kernel: usb 2-1: Product: 2Big Quadra USB3
> Dec 03 02:05:56 charon kernel: usb 2-1: Manufacturer: LaCie
> Dec 03 02:05:56 charon kernel: usb 2-1: SerialNumber: 00000000250e9e711084

This is from usbcore. It reports that a new device has been detected.

> Dec 03 02:05:56 charon mtp-probe[3108]: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
> Dec 03 02:05:56 charon mtp-probe[3108]: bus: 2, device: 2 was not an MTP device

From udev. It basically means that it is not a camera to import
pictures from.

> Dec 03 02:05:56 charon kernel: usb_storage: loading out-of-tree module taints kernel.
> Dec 03 02:05:56 charon kernel: usb_storage: module verification failed: signature and/or required key missing - tainting kernel
> Dec 03 02:05:56 charon kernel: usbcore: registered new interface driver usb-storage

The kernel identified the device as storage and udev has loaded drivers
now being probed.

> Dec 03 02:05:56 charon kernel: scsi host5: uas
> Dec 03 02:05:56 charon kernel: usbcore: registered new interface driver uas

UAS is taking the device.

> Dec 03 02:05:56 charon kernel: scsi 5:0:0:0: Direct-Access     LaCie    2Big Quadra v3   051E PQ: 0 ANSI: 6
> Dec 03 02:05:56 charon kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0

It is identified as a disk.

> Dec 03 02:05:56 charon mtp-probe[3117]: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
> Dec 03 02:05:56 charon mtp-probe[3117]: bus: 2, device: 2 was not an MTP device

Again, not a camera.

> Dec 03 02:05:56 charon kernel: sd 5:0:0:0: [sdc] 7814025564 512-byte logical blocks: (4.00 TB/3.64 TiB)
> Dec 03 02:05:56 charon kernel: sd 5:0:0:0: [sdc] Write Protect is off
> Dec 03 02:05:56 charon kernel: sd 5:0:0:0: [sdc] Mode Sense: 43 00 00 00
> Dec 03 02:05:56 charon kernel: sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Its size and caching attributes are determined. Is the size of 4 TB
correct?

> Dec 03 02:06:13 charon kernel: usb 2-1: USB disconnect, device number 2

A disconnect after 17 seconds. Whether this is a bug or not depends on
whether you pulled the plug. Did you?

> Dec 03 02:06:13 charon kernel: sd 5:0:0:0: [sdc] Optimal transfer size 33553920 bytes
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Read Capacity(16) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Sense not available.
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Sense not available.
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] 0 512-byte logical blocks: (0 B/0 B)
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Attached SCSI disk

This has to happen if the device is unavailable.

> Dec 03 02:06:15 charon kernel: usb 2-1: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
> Dec 03 02:06:15 charon kernel: usb 2-1: New USB device found, idVendor=059f, idProduct=105f, bcdDevice= 0.01
> Dec 03 02:06:15 charon kernel: usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
> Dec 03 02:06:15 charon kernel: usb 2-1: Product: 2Big Quadra USB3
> Dec 03 02:06:15 charon kernel: usb 2-1: Manufacturer: LaCie
> Dec 03 02:06:15 charon kernel: usb 2-1: SerialNumber: 00000000250e9e711084
> Dec 03 02:06:15 charon kernel: scsi host5: uas
> Dec 03 02:06:15 charon kernel: scsi 5:0:0:0: Direct-Access     LaCie    2Big Quadra v3   051E PQ: 0 ANSI: 6
> Dec 03 02:06:15 charon kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0
> Dec 03 02:06:15 charon kernel: sd 5:0:0:0: [sdc] 7814025564 512-byte logical blocks: (4.00 TB/3.64 TiB)
> Dec 03 02:06:15 charon kernel: sd 5:0:0:0: [sdc] Write Protect is off
> Dec 03 02:06:15 charon kernel: sd 5:0:0:0: [sdc] Mode Sense: 43 00 00 00
> Dec 03 02:06:15 charon kernel: sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> Dec 03 02:06:15 charon mtp-probe[3209]: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
> Dec 03 02:06:15 charon mtp-probe[3209]: bus: 2, device: 3 was not an MTP device
> Dec 03 02:06:15 charon mtp-probe[3212]: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
> Dec 03 02:06:15 charon mtp-probe[3212]: bus: 2, device: 3 was not an MTP device

This is basically a repeat of the first event.

> Dec 03 02:06:46 charon kernel: sd 5:0:0:0: tag#28 uas_eh_abort_handler 0 uas-tag 1 inflight: IN 
> Dec 03 02:06:46 charon kernel: sd 5:0:0:0: tag#28 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00

This is a SCSI command: REPORT SUPPORTED OPERATION CODES command
Having this command fail is a bit ironic I suppose.

> Dec 03 02:06:46 charon kernel: scsi host5: uas_eh_device_reset_handler start
> Dec 03 02:06:47 charon kernel: usb 2-1: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
> Dec 03 02:06:47 charon kernel: scsi host5: uas_eh_device_reset_handler success
> Dec 03 02:07:17 charon kernel: scsi host5: uas_eh_device_reset_handler start
> Dec 03 02:07:17 charon kernel: sd 5:0:0:0: tag#28 uas_zap_pending 0 uas-tag 1 inflight: 
> Dec 03 02:07:17 charon kernel: sd 5:0:0:0: tag#28 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00
> Dec 03 02:07:17 charon kernel: usb 2-1: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
> Dec 03 02:07:17 charon kernel: scsi host5: uas_eh_device_reset_handler success

And it happens again. This device is seriously buggy. Is it usable
after that or did you just cut the log?

	Regards & Thanks
		Oliver

RE: Issues with LaCie USB3 drive and UAS

[David C. Partridge]

Using options usb-storage quirks=059f:105f:ks

Dec 07 10:40:40 charon kernel: usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Dec 07 10:40:40 charon kernel: usb 2-1: New USB device found, idVendor=059f, idProduct=105f, bcdDevice= 0.01
Dec 07 10:40:40 charon kernel: usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Dec 07 10:40:40 charon kernel: usb 2-1: Product: 2Big Quadra USB3
Dec 07 10:40:40 charon kernel: usb 2-1: Manufacturer: LaCie
Dec 07 10:40:40 charon kernel: usb 2-1: SerialNumber: 00000000250e9e711084
Dec 07 10:40:40 charon mtp-probe[2790]: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
Dec 07 10:40:40 charon mtp-probe[2790]: bus: 2, device: 2 was not an MTP device
Dec 07 10:40:40 charon kernel: usb_storage: loading out-of-tree module taints kernel.
Dec 07 10:40:40 charon kernel: usb_storage: module verification failed: signature and/or required key missing - tainting kernel
Dec 07 10:40:40 charon kernel: usbcore: registered new interface driver usb-storage
Dec 07 10:40:40 charon kernel: scsi host5: uas
Dec 07 10:40:40 charon kernel: usbcore: registered new interface driver uas
Dec 07 10:40:40 charon kernel: scsi 5:0:0:0: Direct-Access     LaCie    2Big Quadra v3   051E PQ: 0 ANSI: 6
Dec 07 10:40:40 charon kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0
Dec 07 10:40:40 charon mtp-probe[2799]: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
Dec 07 10:40:40 charon mtp-probe[2799]: bus: 2, device: 2 was not an MTP device
Dec 07 10:40:40 charon kernel: sd 5:0:0:0: [sdc] 7814025564 512-byte logical blocks: (4.00 TB/3.64 TiB)
Dec 07 10:40:40 charon kernel: sd 5:0:0:0: [sdc] Write Protect is off
Dec 07 10:40:40 charon kernel: sd 5:0:0:0: [sdc] Mode Sense: 43 00 00 00
Dec 07 10:40:40 charon kernel: sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec 07 10:40:57 charon kernel: usb 2-1: USB disconnect, device number 2
Dec 07 10:40:57 charon kernel: sd 5:0:0:0: [sdc] Optimal transfer size 33553920 bytes
Dec 07 10:40:57 charon kernel: sd 5:0:0:0: [sdc] Read Capacity(16) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Dec 07 10:40:57 charon kernel: sd 5:0:0:0: [sdc] Sense not available.
Dec 07 10:40:58 charon kernel: sd 5:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Dec 07 10:40:58 charon kernel: sd 5:0:0:0: [sdc] Sense not available.
Dec 07 10:40:58 charon kernel: sd 5:0:0:0: [sdc] 0 512-byte logical blocks: (0 B/0 B)
Dec 07 10:40:58 charon kernel: sd 5:0:0:0: [sdc] Attached SCSI disk
Dec 07 10:40:58 charon kernel: usb 2-1: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
Dec 07 10:40:58 charon kernel: usb 2-1: New USB device found, idVendor=059f, idProduct=105f, bcdDevice= 0.01
Dec 07 10:40:58 charon kernel: usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Dec 07 10:40:58 charon kernel: usb 2-1: Product: 2Big Quadra USB3
Dec 07 10:40:58 charon kernel: usb 2-1: Manufacturer: LaCie
Dec 07 10:40:58 charon kernel: usb 2-1: SerialNumber: 00000000250e9e711084
Dec 07 10:40:58 charon kernel: scsi host5: uas
Dec 07 10:40:58 charon kernel: scsi 5:0:0:0: Direct-Access     LaCie    2Big Quadra v3   051E PQ: 0 ANSI: 6
Dec 07 10:40:58 charon kernel: scsi 5:0:0:0: Attached scsi generic sg3 type 0
Dec 07 10:40:58 charon kernel: sd 5:0:0:0: [sdc] 7814025564 512-byte logical blocks: (4.00 TB/3.64 TiB)
Dec 07 10:40:58 charon kernel: sd 5:0:0:0: [sdc] Write Protect is off
Dec 07 10:40:58 charon kernel: sd 5:0:0:0: [sdc] Mode Sense: 43 00 00 00
Dec 07 10:40:58 charon kernel: sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec 07 10:40:59 charon mtp-probe[2858]: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
Dec 07 10:40:59 charon mtp-probe[2858]: bus: 2, device: 3 was not an MTP device
Dec 07 10:40:59 charon mtp-probe[2861]: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
Dec 07 10:40:59 charon mtp-probe[2861]: bus: 2, device: 3 was not an MTP device
Dec 07 10:41:29 charon kernel: sd 5:0:0:0: tag#6 uas_eh_abort_handler 0 uas-tag 1 inflight: IN 
Dec 07 10:41:29 charon kernel: sd 5:0:0:0: tag#6 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00
Dec 07 10:41:29 charon kernel: scsi host5: uas_eh_device_reset_handler start
Dec 07 10:41:29 charon kernel: usb 2-1: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
Dec 07 10:41:29 charon kernel: scsi host5: uas_eh_device_reset_handler success

David

Re: Issues with LaCie USB3 drive and UAS

[Oliver Neukum]

Am Montag, den 07.12.2020, 10:53 +0000 schrieb David C. Partridge:
> Using options usb-storage quirks=059f:105f:ks
> 
> Dec 07 10:40:40 charon kernel: usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
> Dec 07 10:40:40 charon kernel: usb 2-1: New USB device found, idVendor=059f, idProduct=105f, bcdDevice= 0.01
> Dec 07 10:40:40 charon kernel: usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
> Dec 07 10:40:40 charon kernel: usb 2-1: Product: 2Big Quadra USB3
> Dec 07 10:40:40 charon kernel: usb 2-1: Manufacturer: LaCie
> Dec 07 10:40:40 charon kernel: usb 2-1: SerialNumber: 00000000250e9e711084
> Dec 07 10:40:40 charon mtp-probe[2790]: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
> Dec 07 10:40:40 charon mtp-probe[2790]: bus: 2, device: 2 was not an MTP device
> Dec 07 10:40:40 charon kernel: usb_storage: loading out-of-tree module taints kernel.
> Dec 07 10:40:40 charon kernel: usb_storage: module verification failed: signature and/or required key missing - tainting kernel
> Dec 07 10:40:40 charon kernel: usbcore: registered new interface driver usb-storage
> Dec 07 10:40:40 charon kernel: scsi host5: uas
> Dec 07 10:40:40 charon kernel: usbcore: registered new interface driver uas
> Dec 07 10:40:40 charon kernel: scsi 5:0:0:0: Direct-Access     LaCie    2Big Quadra v3   051E PQ: 0 ANSI: 6
> Dec 07 10:40:40 charon kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0
> Dec 07 10:40:40 charon mtp-probe[2799]: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
> Dec 07 10:40:40 charon mtp-probe[2799]: bus: 2, device: 2 was not an MTP device
> Dec 07 10:40:40 charon kernel: sd 5:0:0:0: [sdc] 7814025564 512-byte logical blocks: (4.00 TB/3.64 TiB)
> Dec 07 10:40:40 charon kernel: sd 5:0:0:0: [sdc] Write Protect is off
> Dec 07 10:40:40 charon kernel: sd 5:0:0:0: [sdc] Mode Sense: 43 00 00 00
> Dec 07 10:40:40 charon kernel: sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> Dec 07 10:40:57 charon kernel: usb 2-1: USB disconnect, device number 2

Again, did you plug the cable or did the device spontaneously
disconnect?

> Dec 07 10:40:57 charon kernel: sd 5:0:0:0: [sdc] Optimal transfer size 33553920 bytes
> Dec 07 10:40:57 charon kernel: sd 5:0:0:0: [sdc] Read Capacity(16) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
> Dec 07 10:40:57 charon kernel: sd 5:0:0:0: [sdc] Sense not available.
> Dec 07 10:40:58 charon kernel: sd 5:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
> Dec 07 10:40:58 charon kernel: sd 5:0:0:0: [sdc] Sense not available.
> Dec 07 10:40:58 charon kernel: sd 5:0:0:0: [sdc] 0 512-byte logical blocks: (0 B/0 B)
> Dec 07 10:40:58 charon kernel: sd 5:0:0:0: [sdc] Attached SCSI disk

To be expected in that case.

> Dec 07 10:40:58 charon kernel: usb 2-1: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
> Dec 07 10:40:58 charon kernel: usb 2-1: New USB device found, idVendor=059f, idProduct=105f, bcdDevice= 0.01
> Dec 07 10:40:58 charon kernel: usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
> Dec 07 10:40:58 charon kernel: usb 2-1: Product: 2Big Quadra USB3
> Dec 07 10:40:58 charon kernel: usb 2-1: Manufacturer: LaCie
> Dec 07 10:40:58 charon kernel: usb 2-1: SerialNumber: 00000000250e9e711084
> Dec 07 10:40:58 charon kernel: scsi host5: uas
> Dec 07 10:40:58 charon kernel: scsi 5:0:0:0: Direct-Access     LaCie    2Big Quadra v3   051E PQ: 0 ANSI: 6
> Dec 07 10:40:58 charon kernel: scsi 5:0:0:0: Attached scsi generic sg3 type 0
> Dec 07 10:40:58 charon kernel: sd 5:0:0:0: [sdc] 7814025564 512-byte logical blocks: (4.00 TB/3.64 TiB)
> Dec 07 10:40:58 charon kernel: sd 5:0:0:0: [sdc] Write Protect is off
> Dec 07 10:40:58 charon kernel: sd 5:0:0:0: [sdc] Mode Sense: 43 00 00 00
> Dec 07 10:40:58 charon kernel: sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> Dec 07 10:40:59 charon mtp-probe[2858]: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
> Dec 07 10:40:59 charon mtp-probe[2858]: bus: 2, device: 3 was not an MTP device
> Dec 07 10:40:59 charon mtp-probe[2861]: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
> Dec 07 10:40:59 charon mtp-probe[2861]: bus: 2, device: 3 was not an MTP device
> Dec 07 10:41:29 charon kernel: sd 5:0:0:0: tag#6 uas_eh_abort_handler 0 uas-tag 1 inflight: IN 
> Dec 07 10:41:29 charon kernel: sd 5:0:0:0: tag#6 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00

OK, the SCSI layer is not reacting as desired.

> Dec 07 10:41:29 charon kernel: scsi host5: uas_eh_device_reset_handler start
> Dec 07 10:41:29 charon kernel: usb 2-1: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
> Dec 07 10:41:29 charon kernel: scsi host5: uas_eh_device_reset_handler success

In this case, could you retry with
usb-storage quirks=059f:105f:kf
?

	Regards
		Oliver

RE: Issues with LaCie USB3 drive and UAS

[David C. Partridge]

>> 2-1: USB disconnect, device number 2

>Again, did you plug the cable or did the device spontaneously disconnect?

That was a spontaneous disconnect.

> In this case, could you retry with
> usb-storage quirks=059f:105f:kf

Sure! The results are in general a lot more promising (apart from the first line) - plus I was able to read/write files without problems:

Dec 08 15:47:48 charon kernel: usb usb2-port6: config error
Dec 08 15:47:49 charon kernel: usb 1-6: new high-speed USB device number 4 using xhci_hcd
Dec 08 15:47:49 charon kernel: usb 1-6: New USB device found, idVendor=059f, idProduct=105f, bcdDevice= 0.01
Dec 08 15:47:49 charon kernel: usb 1-6: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Dec 08 15:47:49 charon kernel: usb 1-6: Product: 2Big Quadra USB3
Dec 08 15:47:49 charon kernel: usb 1-6: Manufacturer: LaCie
Dec 08 15:47:49 charon kernel: usb 1-6: SerialNumber: 00000000250e9e711084
Dec 08 15:47:49 charon mtp-probe[5230]: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6"
Dec 08 15:47:49 charon mtp-probe[5230]: bus: 1, device: 4 was not an MTP device
Dec 08 15:47:49 charon kernel: usb_storage: loading out-of-tree module taints kernel.
Dec 08 15:47:49 charon kernel: usb_storage: module verification failed: signature and/or required key missing - tainting kernel
Dec 08 15:47:49 charon kernel: usbcore: registered new interface driver usb-storage
Dec 08 15:47:49 charon kernel: scsi host5: uas
Dec 08 15:47:49 charon kernel: usbcore: registered new interface driver uas
Dec 08 15:47:49 charon kernel: scsi 5:0:0:0: Direct-Access     LaCie    2Big Quadra v3   051E PQ: 0 ANSI: 6
Dec 08 15:47:49 charon mtp-probe[5239]: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6"
Dec 08 15:47:49 charon mtp-probe[5239]: bus: 1, device: 4 was not an MTP device
Dec 08 15:47:49 charon kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0
Dec 08 15:47:49 charon kernel: sd 5:0:0:0: [sdc] 7814025564 512-byte logical blocks: (4.00 TB/3.64 TiB)
Dec 08 15:47:49 charon kernel: sd 5:0:0:0: [sdc] Write Protect is off
Dec 08 15:47:49 charon kernel: sd 5:0:0:0: [sdc] Mode Sense: 43 00 00 00
Dec 08 15:47:49 charon kernel: sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec 08 15:47:49 charon kernel: sd 5:0:0:0: [sdc] Optimal transfer size 33553920 bytes
Dec 08 15:47:49 charon kernel:  sdc: sdc1 sdc2
Dec 08 15:47:49 charon kernel: sd 5:0:0:0: [sdc] Attached SCSI disk
Dec 08 15:47:55 charon polkitd(authority=local)[760]: Operator of unix-session:7 successfully authenticated as unix-user:amonra to gain ONE-SHOT authorization for action org.freedesktop.udisks2.filesystem-mount-other-seat for system-bus-name::1.135 [/usr/libexec/gvfs-udisks2-volume-monitor] (owned by unix-user:amonra)
Dec 08 15:47:55 charon kernel: exfat: module is from the staging directory, the quality is unknown, you have been warned.
Dec 08 15:47:55 charon kernel: exFAT: Version 1.3.0
Dec 08 15:47:55 charon kernel: [EXFAT] trying to mount...
Dec 08 15:47:55 charon kernel: [EXFAT] mounted successfully
Dec 08 15:47:55 charon systemd[1]: Created slice system-clean\x2dmount\x2dpoint.slice.
Dec 08 15:47:55 charon systemd[1]: Finished Clean the /media/amonra/4TB mount point.

Re: Issues with LaCie USB3 drive and UAS

[Alan Stern]

On Tue, Dec 08, 2020 at 04:06:49PM -0000, David C. Partridge wrote:
> >> 2-1: USB disconnect, device number 2
> 
> >Again, did you plug the cable or did the device spontaneously disconnect?
> 
> That was a spontaneous disconnect.
> 
> > In this case, could you retry with
> > usb-storage quirks=059f:105f:kf
> 
> Sure! The results are in general a lot more promising (apart from the first line) - plus I was able to read/write files without problems:
> 
> Dec 08 15:47:48 charon kernel: usb usb2-port6: config error
> Dec 08 15:47:49 charon kernel: usb 1-6: new high-speed USB device number 4 using xhci_hcd

This is puzzling.  The device connected at SuperSpeed in the previous 
tests.  Clearly this is related to the warning in the preceding line 
(the port failed to configure its link partner).

What could have happened?  A problem in the cable?

The usb-storage quirk setting would not have affected this.

Alan Stern

RE: Issues with LaCie USB3 drive and UAS

[David C. Partridge]

>This is puzzling.  The device connected at SuperSpeed in the previous
tests.  Clearly this is related to the warning in the preceding line (the
port failed to configure its link partner).

>What could have happened?  A problem in the cable?

Previous test was using a 3m long cable.

Tried again with a 1m cable:

Dec 08 16:38:30 charon kernel: usb 2-1: new SuperSpeed Gen 1 USB device
number 2 using xhci_hcd
Dec 08 16:38:30 charon kernel: usb 2-1: New USB device found, idVendor=059f,
idProduct=105f, bcdDevice= 0.01
Dec 08 16:38:30 charon kernel: usb 2-1: New USB device strings: Mfr=2,
Product=3, SerialNumber=1
Dec 08 16:38:30 charon kernel: usb 2-1: Product: 2Big Quadra USB3
Dec 08 16:38:30 charon kernel: usb 2-1: Manufacturer: LaCie
Dec 08 16:38:30 charon kernel: usb 2-1: SerialNumber: 00000000250e9e711084
Dec 08 16:38:30 charon kernel: scsi host5: uas
Dec 08 16:38:30 charon kernel: scsi 5:0:0:0: Direct-Access     LaCie    2Big
Quadra v3   051E PQ: 0 ANSI: 6
Dec 08 16:38:30 charon kernel: scsi 5:0:0:0: Attached scsi generic sg3 type
0
Dec 08 16:38:30 charon mtp-probe[15990]: checking bus 2, device 2:
"/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
Dec 08 16:38:30 charon mtp-probe[15990]: bus: 2, device: 2 was not an MTP
device
Dec 08 16:38:30 charon mtp-probe[15993]: checking bus 2, device 2:
"/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
Dec 08 16:38:30 charon mtp-probe[15993]: bus: 2, device: 2 was not an MTP
device
Dec 08 16:38:30 charon kernel: sd 5:0:0:0: [sdc] 7814025564 512-byte logical
blocks: (4.00 TB/3.64 TiB)
Dec 08 16:38:30 charon kernel: sd 5:0:0:0: [sdc] Write Protect is off
Dec 08 16:38:30 charon kernel: sd 5:0:0:0: [sdc] Mode Sense: 43 00 00 00
Dec 08 16:38:30 charon kernel: sd 5:0:0:0: [sdc] Write cache: enabled, read
cache: enabled, doesn't support DPO or FUA
Dec 08 16:38:30 charon kernel: sd 5:0:0:0: [sdc] Optimal transfer size
33553920 bytes
Dec 08 16:38:30 charon kernel:  sdc: sdc1 sdc2
Dec 08 16:38:30 charon kernel: sd 5:0:0:0: [sdc] Attached SCSI disk
Dec 08 16:38:31 charon sshd[15980]: Accepted password for amonra from
192.168.129.64 port 59740 ssh2
Dec 08 16:38:31 charon sshd[15980]: pam_unix(sshd:session): session opened
for user amonra by (uid=0)
Dec 08 16:38:31 charon systemd-logind[773]: New session 19 of user amonra.
Dec 08 16:38:31 charon systemd[1]: Started Session 19 of user amonra.
Dec 08 16:38:32 charon /usr/sbin/x2gocleansessions[899]:
amonra-50-1607445512_stDLXQt_dp32: state file for this session does not
exist: /tmp>
Dec 08 16:38:34 charon /usr/bin/x2gostartagent[16250]: successfully started
X2Go Agent session with ID amonra-50-1607445512_stDLXQt_dp32
Dec 08 16:38:41 charon /usr/bin/x2goruncommand[16445]: launching session
with Xsession-x2go mechanism, using STARTUP="startlxqt"
Dec 08 16:38:41 charon /usr/bin/x2goruncommand[16446]: dbus wrapper
available as /usr/bin/dbus-run-session
Dec 08 16:38:41 charon /usr/bin/x2gomountdirs[16312]: successfully mounted
amonra@127.0.0.1:42471/cygdrive/C/Users/amonra/X2GO~1/S-BA8C~1/sp>
Dec 08 16:38:42 charon polkitd(authority=local)[760]: Registered
Authentication Agent for unix-session:19 (system bus name :1.148 [/usr/bin/>
Dec 08 16:38:42 charon NetworkManager[730]: <info>  [1607445522.3927]
agent-manager: agent[c5fafd67353e3850,:1.150/org.freedesktop.nm-applet>
Dec 08 16:38:49 charon polkitd(authority=local)[760]: Operator of
unix-session:19 successfully authenticated as unix-user:amonra to gain ONE>
Dec 08 16:38:49 charon kernel: [EXFAT] trying to mount...
Dec 08 16:38:49 charon kernel: [EXFAT] mounted successfully
Dec 08 16:38:49 charon systemd[1]: Finished Clean the /media/amonra/4TB
mount point.
Dec 08 16:38:49 charon udisksd[775]: Mounted /dev/sdc2 at /media/amonra/4TB
on behalf of uid 1000

I then tried again using the 3m long cable and got the same error as before
and connected at high-speed not SuperSpeed

Should I expect problems with a 3m long cable or does this say the 3m long
cable is faulty? 

David

-----Original Message-----
From: Alan Stern <stern@rowland.harvard.edu> 
Sent: 08 December 2020 16:27
To: David C. Partridge <david.partridge@perdrix.co.uk>
Cc: 'Oliver Neukum' <oneukum@suse.com>; linux-usb@vger.kernel.org
Subject: Re: Issues with LaCie USB3 drive and UAS

On Tue, Dec 08, 2020 at 04:06:49PM -0000, David C. Partridge wrote:
> >> 2-1: USB disconnect, device number 2
> 
> >Again, did you plug the cable or did the device spontaneously disconnect?
> 
> That was a spontaneous disconnect.
> 
> > In this case, could you retry with
> > usb-storage quirks=059f:105f:kf
> 
> Sure! The results are in general a lot more promising (apart from the
first line) - plus I was able to read/write files without problems:
> 
> Dec 08 15:47:48 charon kernel: usb usb2-port6: config error Dec 08 
> 15:47:49 charon kernel: usb 1-6: new high-speed USB device number 4 
> using xhci_hcd

This is puzzling.  The device connected at SuperSpeed in the previous tests.
Clearly this is related to the warning in the preceding line (the port
failed to configure its link partner).

What could have happened?  A problem in the cable?

The usb-storage quirk setting would not have affected this.

Alan Stern

Re: Issues with LaCie USB3 drive and UAS

['Alan Stern']

On Tue, Dec 08, 2020 at 04:47:44PM -0000, David C. Partridge wrote:
> >This is puzzling.  The device connected at SuperSpeed in the previous
> tests.  Clearly this is related to the warning in the preceding line (the
> port failed to configure its link partner).
> 
> >What could have happened?  A problem in the cable?
> 
> Previous test was using a 3m long cable.
> 
> Tried again with a 1m cable:
> 
> Dec 08 16:38:30 charon kernel: usb 2-1: new SuperSpeed Gen 1 USB device
> number 2 using xhci_hcd
...

So it worked.

> I then tried again using the 3m long cable and got the same error as before
> and connected at high-speed not SuperSpeed
> 
> Should I expect problems with a 3m long cable or does this say the 3m long
> cable is faulty? 

IT depends on the thickness (gauge) of the wires inside the cable.  
There's a table (11-3) in the USB-3.1 spec that lists maximum cable 
length for a variety of gauges.

For AWG 28 the maximum cable length is 0.8 meters.  For AWG 20 the 
maximum length is 5.3 meters.  Your cable is likely to be somewhere in 
that range, but I don't know where.

On the bright side, it looks like you have found the answer to all the 
problems.  :-)

Alan Stern

RE: Issues with LaCie USB3 drive and UAS

[David C. Partridge]

Thank you to both Oliver and to you.

I'll chase up the supplier over the cable.

Would I be right to assume that this LaCie device (and other Seagate USB
devices) will the added to the database of quirks? So that when Oliver's fix
goes "mainstream" no-one will need to add options for modprobe?

Hmm I wonder how long it will take the Ubuntu Kernel to catch up with
Olivers patch?

Thanks again,
David

-----Original Message-----
From: 'Alan Stern' <stern@rowland.harvard.edu> 
Sent: 08 December 2020 17:45
To: David C. Partridge <david.partridge@perdrix.co.uk>
Cc: 'Oliver Neukum' <oneukum@suse.com>; linux-usb@vger.kernel.org
Subject: Re: Issues with LaCie USB3 drive and UAS

On Tue, Dec 08, 2020 at 04:47:44PM -0000, David C. Partridge wrote:
> >This is puzzling.  The device connected at SuperSpeed in the previous
> tests.  Clearly this is related to the warning in the preceding line (the
> port failed to configure its link partner).
> 
> >What could have happened?  A problem in the cable?
> 
> Previous test was using a 3m long cable.
> 
> Tried again with a 1m cable:
> 
> Dec 08 16:38:30 charon kernel: usb 2-1: new SuperSpeed Gen 1 USB device
> number 2 using xhci_hcd
...

So it worked.

> I then tried again using the 3m long cable and got the same error as
before
> and connected at high-speed not SuperSpeed
> 
> Should I expect problems with a 3m long cable or does this say the 3m long
> cable is faulty? 

IT depends on the thickness (gauge) of the wires inside the cable.  
There's a table (11-3) in the USB-3.1 spec that lists maximum cable 
length for a variety of gauges.

For AWG 28 the maximum cable length is 0.8 meters.  For AWG 20 the 
maximum length is 5.3 meters.  Your cable is likely to be somewhere in 
that range, but I don't know where.

On the bright side, it looks like you have found the answer to all the 
problems.  :-)

Alan Stern

Re: Issues with LaCie USB3 drive and UAS

[Oliver Neukum]

Am Dienstag, den 08.12.2020, 20:00 +0000 schrieb David C. Partridge:

Hi,

> I'll chase up the supplier over the cable.

What we have often seen is that cables go right to the edge of what is
allowed and so do devices and - lo and behold - the combination does
not work.

> Would I be right to assume that this LaCie device (and other Seagate USB
> devices) will the added to the database of quirks? So that when Oliver's fix
> goes "mainstream" no-one will need to add options for modprobe?

Yes. I have submitted it.

> Hmm I wonder how long it will take the Ubuntu Kernel to catch up with
> Olivers patch?

Greg usually applies such patches to the stable tree. Weeks to a few 
months or so I'd say. I cannot comment on Ubuntu's update policies.

	Regards
		Oliver

Re: Issues with LaCie USB3 drive and UAS

[Oliver Neukum]

Am Donnerstag, den 03.12.2020, 02:11 +0000 schrieb David C. Partridge:
> Now with uas.ko	and usb-storage.ko 

Hi,

upon further reading, could you repeat the test with an additional
SINGLE_LUN quirk?

	Regards
		Oliver

RE: Issues with LaCie USB3 drive and UAS

[David C. Partridge]

> upon further reading, could you repeat the test with an additional SINGLE_LUN quirk?

Happy to do that if you can confirm what the blacklist-uas.conf should look like to achieve that?

Should it read: options usb-storage quirks=059f:105f:ks

David
-----Original Message-----
From: Oliver Neukum [mailto:oneukum@suse.com] 
Sent: 03 December 2020 14:07
To: David C. Partridge; linux-usb@vger.kernel.org
Subject: Re: Issues with LaCie USB3 drive and UAS

Am Donnerstag, den 03.12.2020, 02:11 +0000 schrieb David C. Partridge:
> Now with uas.ko	and usb-storage.ko 

Hi,

upon further reading, could you repeat the test with an additional
SINGLE_LUN quirk?

	Regards
		Oliver

Re: Issues with LaCie USB3 drive and UAS

[Alan Stern]

On Thu, Dec 03, 2020 at 02:46:47PM -0000, David C. Partridge wrote:
> > upon further reading, could you repeat the test with an additional SINGLE_LUN quirk?
> 
> Happy to do that if you can confirm what the blacklist-uas.conf should look like to achieve that?
> 
> Should it read: options usb-storage quirks=059f:105f:ks
> 
> David
> -----Original Message-----
> From: Oliver Neukum [mailto:oneukum@suse.com] 
> Sent: 03 December 2020 14:07
> To: David C. Partridge; linux-usb@vger.kernel.org
> Subject: Re: Issues with LaCie USB3 drive and UAS
> 
> Am Donnerstag, den 03.12.2020, 02:11 +0000 schrieb David C. Partridge:
> > Now with uas.ko	and usb-storage.ko 
> 
> Hi,
> 
> upon further reading, could you repeat the test with an additional
> SINGLE_LUN quirk?
> 
> 	Regards
> 		Oliver

By the way, we do have an 'f' quirk for US_FL_NO_REPORT_OPCODES.  You 
could try that one rather than 's'.

Alan Stern