05-30-2018, 06:20 AM
(This post was last modified: 05-30-2018, 06:29 AM by AnythingIsFine.)
Hello,
I know I'm late to the party, but I've been encountering the very same issue described here on my Rock64 4GB model, running Armbian 5.42
I have a 500GB 2.5' Hitachi drive, enclosed in a ICYBOX IB231StU3 connected via USB 3.0 to the Rock64 which I use for storage.
I noticed when I had high disk utilization, I got some messages as below in my system log and the Rock just "froze", I had to unplug/plug it back up in order to get it running.
I tried blacklisting the "uas" kernel module as described in this thread by @rotant, yet post reboot my external HDD driver was still stuck to "uas"
I found this post, which uses Armbian's config file to blacklist the "uas" kernel module for the respective device and this did the trick for me.
To summarize:
1. Use
to identify which devices use the dreaded "uas" module.
2.
to identify that device's ID. (just like user rotant pointed out)
3. Edit the /boot/ArmbianEnv.txt. Go to the line:
and add you device ID these as so(please note the commas between entries):
4. Update initramfs
5. reboot and verify with "lsusb -t" that the device driver is now "usb-storage" as oppossed to "uas"
* Please note, this will affect the read/write sped on your HDD, using "uas" I had ~120 MB/s, whereas with "usb-storage" I get ~ 77 MB/s, but now it's stable...
I know I'm late to the party, but I've been encountering the very same issue described here on my Rock64 4GB model, running Armbian 5.42
I have a 500GB 2.5' Hitachi drive, enclosed in a ICYBOX IB231StU3 connected via USB 3.0 to the Rock64 which I use for storage.
I noticed when I had high disk utilization, I got some messages as below in my system log and the Rock just "froze", I had to unplug/plug it back up in order to get it running.
Code:
May 30 11:50:37 localhost kernel: [ 805.828012] sd 0:0:0:0: [sda] tag#4 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD OUT
May 30 11:50:37 localhost kernel: [ 805.828053] sd 0:0:0:0: [sda] tag#4 CDB: opcode=0x2a 2a 00 01 2e ac 00 00 04 00 00
May 30 11:50:37 localhost kernel: [ 805.828137] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
May 30 11:50:37 localhost kernel: [ 805.828170] xhci-hcd xhci-hcd.9.auto: @00000000f36e4a60 00000000 00000000 1b000000 010c8000
May 30 11:50:37 localhost kernel: [ 805.828384] sd 0:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD OUT
May 30 11:50:37 localhost kernel: [ 805.828423] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 01 2e a8 00 00 04 00 00
May 30 11:50:37 localhost kernel: [ 805.828505] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
May 30 11:50:37 localhost kernel: [ 805.828537] xhci-hcd xhci-hcd.9.auto: @00000000f36e4a80 00000000 00000000 1b000000 010c8000
I tried blacklisting the "uas" kernel module as described in this thread by @rotant, yet post reboot my external HDD driver was still stuck to "uas"
I found this post, which uses Armbian's config file to blacklist the "uas" kernel module for the respective device and this did the trick for me.
To summarize:
1. Use
Code:
lsbusb -t
to identify which devices use the dreaded "uas" module.
2.
Code:
lsusb
to identify that device's ID. (just like user rotant pointed out)
3. Edit the /boot/ArmbianEnv.txt. Go to the line:
Code:
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u
and add you device ID these as so(please note the commas between entries):
Code:
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u,0x174c:0x55aa:u
4. Update initramfs
Code:
update-initramfs -u
5. reboot and verify with "lsusb -t" that the device driver is now "usb-storage" as oppossed to "uas"
* Please note, this will affect the read/write sped on your HDD, using "uas" I had ~120 MB/s, whereas with "usb-storage" I get ~ 77 MB/s, but now it's stable...