[Solved] UAS problem with Seagate disk and enclosure

Post Reply
winstonyin
Posts: 20
Joined: Sat May 26, 2018 5:37 pm
languages_spoken: english, chinese, german
ODROIDs: XU4
Has thanked: 0
Been thanked: 0
Contact:

[Solved] UAS problem with Seagate disk and enclosure

Unread post by winstonyin » Sat Jun 16, 2018 7:44 am

I've been getting errors when reading/writing to a Seagate 4TB Extension Portable hard drive with an ext4 partition:

Code: Select all

Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#29 uas_eh_abort_handler 0 uas-tag 30 inflight: CMD IN 
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#29 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 f8 00 00 00 08 00 00
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#28 uas_eh_abort_handler 0 uas-tag 29 inflight: CMD IN 
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#28 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 f0 00 00 00 08 00 00
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#27 uas_eh_abort_handler 0 uas-tag 28 inflight: CMD IN 
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#27 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 e8 00 00 00 08 00 00
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#26 uas_eh_abort_handler 0 uas-tag 27 inflight: CMD IN 
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#26 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 e0 00 00 00 08 00 00
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#25 uas_eh_abort_handler 0 uas-tag 26 inflight: CMD IN 
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#25 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 d8 00 00 00 08 00 00
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#24 uas_eh_abort_handler 0 uas-tag 25 inflight: CMD IN 
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#24 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 d0 00 00 00 08 00 00
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#23 uas_eh_abort_handler 0 uas-tag 24 inflight: CMD IN 
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#23 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 c8 00 00 00 08 00 00
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#22 uas_eh_abort_handler 0 uas-tag 23 inflight: CMD IN 
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#22 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 c0 00 00 00 08 00 00
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#21 uas_eh_abort_handler 0 uas-tag 22 inflight: CMD IN 
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#21 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 b8 00 00 00 08 00 00
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#20 uas_eh_abort_handler 0 uas-tag 21 inflight: CMD IN 
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#20 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 b0 00 00 00 08 00 00
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#19 uas_eh_abort_handler 0 uas-tag 20 inflight: CMD IN 
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#19 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 a8 00 00 00 08 00 00
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#18 uas_eh_abort_handler 0 uas-tag 19 inflight: CMD IN 
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#18 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 a0 00 00 00 08 00 00
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#17 uas_eh_abort_handler 0 uas-tag 18 inflight: CMD IN 
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#17 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 98 00 00 00 08 00 00
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: CMD IN 
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#16 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 90 00 00 00 08 00 00
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#15 uas_eh_abort_handler 0 uas-tag 16 inflight: CMD IN 
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#15 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 88 00 00 00 08 00 00
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#14 uas_eh_abort_handler 0 uas-tag 15 inflight: CMD IN 
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#14 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 80 00 00 00 08 00 00
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#13 uas_eh_abort_handler 0 uas-tag 14 inflight: CMD IN 
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#13 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 78 00 00 00 08 00 00
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#12 uas_eh_abort_handler 0 uas-tag 13 inflight: CMD IN 
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#12 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 70 00 00 00 08 00 00
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#11 uas_eh_abort_handler 0 uas-tag 12 inflight: CMD IN 
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#11 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 68 00 00 00 08 00 00
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#10 uas_eh_abort_handler 0 uas-tag 11 inflight: CMD IN 
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#10 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 60 00 00 00 08 00 00
Jun 16 04:59:18 feynman kernel: sd 1:0:0:0: [sdb] tag#9 uas_eh_abort_handler 0 uas-tag 10 inflight: CMD IN 
Jun 16 04:59:19 feynman kernel: sd 1:0:0:0: [sdb] tag#9 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 58 00 00 00 08 00 00
Jun 16 04:59:19 feynman kernel: sd 1:0:0:0: [sdb] tag#8 uas_eh_abort_handler 0 uas-tag 9 inflight: CMD IN 
Jun 16 04:59:19 feynman kernel: sd 1:0:0:0: [sdb] tag#8 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 50 00 00 00 08 00 00
Jun 16 04:59:19 feynman kernel: sd 1:0:0:0: [sdb] tag#7 uas_eh_abort_handler 0 uas-tag 8 inflight: CMD IN 
Jun 16 04:59:19 feynman kernel: sd 1:0:0:0: [sdb] tag#7 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 48 00 00 00 08 00 00
Jun 16 04:59:19 feynman kernel: sd 1:0:0:0: [sdb] tag#6 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD IN 
Jun 16 04:59:19 feynman kernel: sd 1:0:0:0: [sdb] tag#6 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 40 00 00 00 08 00 00
Jun 16 04:59:19 feynman kernel: sd 1:0:0:0: [sdb] tag#5 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD IN 
Jun 16 04:59:19 feynman kernel: sd 1:0:0:0: [sdb] tag#5 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 38 00 00 00 08 00 00
Jun 16 04:59:19 feynman kernel: sd 1:0:0:0: [sdb] tag#4 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD IN 
Jun 16 04:59:19 feynman kernel: sd 1:0:0:0: [sdb] tag#4 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 30 00 00 00 08 00 00
Jun 16 04:59:19 feynman kernel: sd 1:0:0:0: [sdb] tag#3 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD IN 
Jun 16 04:59:19 feynman kernel: sd 1:0:0:0: [sdb] tag#3 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 28 00 00 00 08 00 00
Jun 16 04:59:19 feynman kernel: sd 1:0:0:0: [sdb] tag#2 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD IN 
Jun 16 04:59:19 feynman kernel: sd 1:0:0:0: [sdb] tag#2 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 20 00 00 00 08 00 00
Jun 16 04:59:19 feynman kernel: sd 1:0:0:0: [sdb] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN 
Jun 16 04:59:19 feynman kernel: sd 1:0:0:0: [sdb] tag#1 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 18 00 00 00 08 00 00
Jun 16 04:59:19 feynman kernel: sd 1:0:0:0: [sdb] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN 
Jun 16 04:59:19 feynman kernel: sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 5c 00 13 10 00 00 00 08 00 00
Jun 16 04:59:19 feynman kernel: scsi host1: uas_eh_device_reset_handler start
Jun 16 04:59:19 feynman kernel: usb 4-1.1: reset SuperSpeed USB device number 3 using xhci-hcd
Jun 16 04:59:19 feynman kernel: scsi host1: uas_eh_device_reset_handler success
Jun 16 04:59:55 feynman kernel: sd 1:0:0:0: [sdb] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN 
Jun 16 04:59:55 feynman kernel: sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 52 81 1d 28 00 00 00 08 00 00
Jun 16 04:59:55 feynman kernel: scsi host1: uas_eh_device_reset_handler start
Jun 16 04:59:55 feynman kernel: usb 4-1.1: reset SuperSpeed USB device number 3 using xhci-hcd
Jun 16 04:59:55 feynman kernel: scsi host1: uas_eh_device_reset_handler success
Having read https://bbs.archlinux.org/viewtopic.php?id=183190 and other relevant threads about similar problems, I added ignore_uas.conf inside /etc/modprobe.d/ to disable UAS for this drive in particular, and performed mkinitcpio before rebooting. However, the same UAS errors continue to appear. When I use lsusb -t, it still shows "Driver=uas" under this drive. How can I properly disable UAS for this drive?

For your information, lsusb lists this drive under Bus 4:

Code: Select all

Bus 004 Device 004: ID 174c:55aa ASMedia Technology Inc. Name: ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge
Bus 004 Device 003: ID 0bc2:231a Seagate RSS LLC Expansion Portable
Bus 004 Device 002: ID 05e3:0616 Genesys Logic, Inc. hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
lsusb -t shows the following for this drive:

Code: Select all

/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 5000M
        |__ Port 1: Dev 3, If 0, Class=Mass Storage, Driver=uas, 5000M
        |__ Port 2: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
I have tried setting the quirk for 0bc2:231a alone, as well as 0bc2:231a, 174c:55aa, 05e3:0616 together, to no avail. After a reboot, UAS continues to show up.

I'm running Arch with the kernel package linux-odroid-xu3 4.14.47-1

SOLUTION: The usb-storage module is loaded as a built-in module of the Arch linux kernel for Odroid XU4. Its options cannot be set through a file at /etc/modprobe.d/, but has to be set in the bootloader. In /boot/boot.txt, modify the line

Code: Select all

setenv bootargs "..."
to

Code: Select all

setenv bootargs "... usb-storage.quirks=0x0bc2:0x231a:u"
where 0x0bc2:0x231a should be replaced according to the output of lsusb for your specific drive.

After boot.txt is saved, boot image needs to be rebuilt:

Code: Select all

cd /boot/
./mkscr
This may prompt you to install the uboot-tools package. Do that and run mkscr again. Just to be safe, I also ran

Code: Select all

mkinitcpio -p linux-odroid-xu3
After a reboot, lsusb -t no longer shows Driver=uas, but rather the desired Driver=usb-storage. The dmesg also shows

Code: Select all

usb 1-1: UAS is blacklisted for this device, using usb-storage instead
(All Seagate external drives have an ATA-to-USB enclosure that is incompatible with UAS. One must manually disable the use of the uas module by setting the quirks option of the usb-storage module.)
Last edited by winstonyin on Sat Jun 16, 2018 7:35 pm, edited 1 time in total.

crashoverride
Posts: 4731
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1
Has thanked: 0
Been thanked: 196 times
Contact:

Re: UAS problem with Seagate disk and enclosure

Unread post by crashoverride » Sat Jun 16, 2018 11:32 am

winstonyin wrote:I have tried setting the quirk for 0bc2:231a alone, as well as 0bc2:231a, 174c:55aa, 05e3:0616 together, to no avail.
https://wiki.odroid.com/odroid-xu4/os_i ... s_and_tips

Code: Select all

usb-storage.quirks=0x0bc2:0x2322:u
Note the ":u" flag at the end of hte VID:PID.

winstonyin
Posts: 20
Joined: Sat May 26, 2018 5:37 pm
languages_spoken: english, chinese, german
ODROIDs: XU4
Has thanked: 0
Been thanked: 0
Contact:

Re: UAS problem with Seagate disk and enclosure

Unread post by winstonyin » Sat Jun 16, 2018 4:14 pm

Yes. The line I have added in /etc/modprobe.d/ignore_uas.conf is

Code: Select all

options usb-storage quirks=0bc2:231a:u
I have also tried

Code: Select all

options usb-storage quirks=0x0bc2:0x231a:u
as well as an additional

Code: Select all

blacklist uas
all with no effect. The link you've provided references a boot.ini file, which doesn't exist for Arch, as far as I know...

winstonyin
Posts: 20
Joined: Sat May 26, 2018 5:37 pm
languages_spoken: english, chinese, german
ODROIDs: XU4
Has thanked: 0
Been thanked: 0
Contact:

Re: UAS problem with Seagate disk and enclosure

Unread post by winstonyin » Sat Jun 16, 2018 7:20 pm

I have solved the problem by a different means. Please see edit of original post.

User avatar
rooted
Posts: 7266
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 453 times
Been thanked: 127 times
Contact:

Re: [Solved] UAS problem with Seagate disk and enclosure

Unread post by rooted » Sun Jun 17, 2018 10:49 am

Good work figuring it out and posting the solution.

mcmanuf
Posts: 5
Joined: Sat Apr 28, 2018 5:03 pm
languages_spoken: english
ODROIDs: HC1
Has thanked: 0
Been thanked: 1 time
Contact:

Re: [Solved] UAS problem with Seagate disk and enclosure

Unread post by mcmanuf » Sun Dec 22, 2019 7:04 pm

Can anyone assist me on how to add multiple drives, that needs to be blacklisted in the boot.ini.
No matter what I do, I can only add one drive?

User avatar
mad_ady
Posts: 7360
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2, Go, Go Advance
Location: Bucharest, Romania
Has thanked: 350 times
Been thanked: 255 times
Contact:

Re: [Solved] UAS problem with Seagate disk and enclosure

Unread post by mad_ady » Sun Dec 22, 2019 7:14 pm

Try by specifying the quirks option multiple times in bootargs: usb-storage.quirks=0x174c:0x1153:u usb-storage.quirks=0x152d:0x0578:u[/c[

mcmanuf
Posts: 5
Joined: Sat Apr 28, 2018 5:03 pm
languages_spoken: english
ODROIDs: HC1
Has thanked: 0
Been thanked: 1 time
Contact:

Re: [Solved] UAS problem with Seagate disk and enclosure

Unread post by mcmanuf » Sun Dec 22, 2019 8:23 pm

Not really working.
However I have made it work by the following
usb-storage.quirks="0x174c:0x1153:u,0x152d:0x0578:u"
These users thanked the author mcmanuf for the post:
mad_ady (Mon Dec 23, 2019 12:04 am)

Post Reply

Return to “Issues”

Who is online

Users browsing this forum: No registered users and 1 guest