Debian + USB3 HDD + UAS:I/O 错误

TCB*_*B13 7 debian usb-drive modprobe

我正在运行 rsync 以将远程机器备份到 ARM SBC 上的 USB 硬盘驱动器,有时 rsync 会因“从输入设备读取错误(I/O 错误)”而停止。我相信这个问题与 UAS + USB 3.0 + rsync 导致高 I/O 负载有关,因为uas_eh_device_reset_handleron /var/log/messages

sd 0:0:0:0: [sda] tag#1 data cmplt err -32 uas-tag 2 inflight: 
sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x28 28 00 38 80 0a 68 00 00 a0 00
sd 0:0:0:0: [sda] tag#0 data cmplt err -32 uas-tag 1 inflight: CMD 
sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 57 50 28 78 00 03 00 00
sd 0:0:0:0: [sda] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD 
sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x28 28 00 38 80 0a 68 00 00 a0 00
sd 0:0:0:0: [sda] tag#2 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD 
sd 0:0:0:0: [sda] tag#2 CDB: opcode=0x2a 2a 00 19 47 7f 20 00 00 90 00
sd 0:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD 
sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 57 50 28 78 00 03 00 00
scsi host0: uas_eh_device_reset_handler start
usb 5-1: reset high-speed USB device number 2 using ehci-platform
scsi host0: uas_eh_device_reset_handler success
sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] tag#0 Sense Key : 0x2 [current] 
sd 0:0:0:0: [sda] tag#0 ASC=0x3a ASCQ=0x0 
sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 57 50 28 78 00 03 00 00
sd 0:0:0:0: [sda] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] tag#1 Sense Key : 0x2 [current] 
sd 0:0:0:0: [sda] tag#1 ASC=0x3a ASCQ=0x0 
sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x2a 2a 00 19 47 7f 20 00 00 90 00
EXT4-fs warning (device sda1): ext4_end_bio:323: I/O error 10 writing to inode 13001563 (offset 0 size 73728 starting block 53014518)
Run Code Online (Sandbox Code Playgroud)

这个 SBC 没有 USB 3 端口,但它仍然使用 UAS 加载硬盘驱动器。据此,UAS在一些高清机箱芯片上被破坏提供解决方案是禁用 UAS但是

1 -如果我的黑名单UAS完全blacklist uas/etc/modprobe.d/blacklist-uas.conf我得到:

lsusb -t
    /:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
        |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=, 480M
Run Code Online (Sandbox Code Playgroud)

看着Class=Mass Storage, Driver=, 480M=> 似乎系统没有加载任何其他方式来处理驱动器。

2-如果我只是尝试为特定的 USB 设备禁用 UAS,就像推荐的帖子一样,它仍然会加载 UAS

echo options usb-storage quirks=174c:55aa:u | tee /etc/modprobe.d/blacklist-uas.conf
update-initramfs -u
reboot

(...)

dmesg | grep sda
[    2.488105] sd 0:0:0:0: [sda] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
[    2.488584] sd 0:0:0:0: [sda] Write Protect is off
[    2.488592] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[    2.489335] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.539288]  sda: sda1
[    2.543875] sd 0:0:0:0: [sda] Attached SCSI disk
[    6.898109] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: errors=remount-ro,data=ordered

lsusb | grep ASMedia
Bus 005 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge

lsusb -t
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 480M
Run Code Online (Sandbox Code Playgroud)

我究竟做错了什么?是否可以禁用 UAS 并使系统仍以其他方式使用 HD?为什么不options usb-storage quirks=174c:55aa:u按应有的方式禁用 UAS?

谢谢你。

一些注意事项

  • 操作系统:4.14.18-sunxi64来自 armbian 的Debian GNU/Linux 9.4 (stretch) 内核
  • SBC:NanoPi NEO2

TCB*_*B13 6

在@AB 的宝贵帮助下,我设法解决了这个问题。正如他所说,我的内核(可能是每个 armbian SBC 内核)没有usb_storage作为模块加载,它是内置的。

在这种情况下,我们需要更改以下可见的引导选项/proc/cmdline

root=UUID=b58.... rootfstype=ext4 console=tty1 console=ttyS0,115200 panic=10 consoleblank=0 loglevel=1 ubootpart=096d26e5-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u   cgroup_enable=memory swapaccount=1
Run Code Online (Sandbox Code Playgroud)

到头来usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u已经定了。我们无法直接编辑此文件,在 armbian 中,此选项存储在文件中/boot/armbianEnv.txt

verbosity=1
console=both
overlay_prefix=sun50i-h5
overlays=usbhost1 usbhost2
rootdev=UUID=b58048d3-ca7b-4ea6-9812-95d403fddadd
rootfstype=ext4
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u
Run Code Online (Sandbox Code Playgroud)

所以我只是在最后一行添加了我的设备,174c:55aa:u,使其:

usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u,174c:55aa:u
Run Code Online (Sandbox Code Playgroud)

以防万一我重新运行update-initramfs -u并重新启动后,USB HD 现在只使用usb-store而不是uas

lsusb -t
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M
Run Code Online (Sandbox Code Playgroud)

正如您在此处看到的,uas现在已为设备正确列入黑名单:

dmesg | grep "usb 5-1"
[    2.308569] usb 5-1: new high-speed USB device number 2 using ehci-platform
[    2.467087] usb 5-1: New USB device found, idVendor=174c, idProduct=55aa
[    2.467106] usb 5-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[    2.467117] usb 5-1: Product: ASM1153E
[    2.467127] usb 5-1: Manufacturer: Inateck
[    2.467137] usb 5-1: SerialNumber: 12345678910E
[    2.468297] usb 5-1: UAS is blacklisted for this device, using usb-storage instead
Run Code Online (Sandbox Code Playgroud)

  • 快速更新:在 USB HD 上运行 `rsync` 和其他一些 I/O 密集型任务 +24 小时后,到目前为止一切正常。 (2认同)