USB error spamming log

[Waltm]

Hiya folks.  I've been having some issues lately so when I checked the log I'm seeing this error repeating constantly. Any clue as to what to do about this?  If it's a hardware failure can I turn it off somehow?

 

For some background, log had filled up so rebooted the machine to clear it.  Replaced a drive that was starting to have errors and was the smallest one on the array.  When the array was rebuilding another drive reported a lot more errors and was disabled overnight. Replacement drive should be here tomorrow.  Cache drive had filled up but has returned to 75%.  Dockers will not start but I though that might be due to the damaged drive in the array.

 

Error in log:
May 15 14:40:28 Tower kernel: usb usb4-port5: Cannot enable. Maybe the USB cable is bad?
May 15 14:40:32 Tower kernel: usb usb4-port5: Cannot enable. Maybe the USB cable is bad?
May 15 14:40:36 Tower kernel: usb usb4-port5: Cannot enable. Maybe the USB cable is bad?
May 15 14:40:40 Tower kernel: usb usb4-port5: Cannot enable. Maybe the USB cable is bad?

 

 

This is what is showing up for usb devices:

USB Devices

Bus 001 Device 001:ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 001 Device 002:ID 8087:800a Intel Corp.

Bus 002 Device 001:ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 002 Device 002:ID 8087:8002 Intel Corp.

Bus 003 Device 001:ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 003 Device 002:ID 0781:5571 SanDisk Corp. Cruzer Fit

Bus 003 Device 003:ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub

Bus 003 Device 004:ID 051d:0002 American Power Conversion Uninterruptible Power Supply

Bus 004 Device 001:ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 004 Device 002:ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub

Bus 005 Device 001:ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 006 Device 001:ID 1d6b:0003 Linux Foundation 3.0 root hub

tower-diagnostics-20220515-1446.zip

[JorgeB]

Try to disconnect every USB cable/device (except the Unraid flash drive) to see if it goes way.

 

14 hours ago, Waltm said:

When the array was rebuilding another drive reported a lot more errors and was disabled overnight.

Because of that there might be some data corruption on the rebuild disk4, unless by luck the error sectors corresponded to empty space there.

 

14 hours ago, Waltm said:

Cache drive had filled up but has returned to 75%.  Dockers will not start

Cache filesystem is fully allocated, you need to run a balance:

https://forums.unraid.net/topic/62230-out-of-space-errors-on-cache-drive/?do=findComment&comment=610551

 

[Waltm]

Good call, I didn't even realize I had anything plugged in but that fixed the USB errors.  New drive is in and rebuilding.  Docker service started with the reboot so I stopped them all for now.  I'll try the balance command once the array is back to normal.

Thanks for the help!