February 10, 20251 yr So, I’ve been trying to download a linux iso with NZBGet and everytime it gets to a specific nzb when I am downloading the file I get an error similar to this: xhci_hcd 0000:00:14.0: ERROR Unknown event condition 10 for slot 4 ep 10 , HC probably busted. It will try to fix it and then if I don’t stop the container in time will crash my entire server and makes me have to power it off and on again. Does anyone know a fix for this. This happens everytime I try to download a nzb file after a few that work correctly with Sonarr. Feb 10 02:06:52 UnBiggerBoy kernel: sd 4:0:0:0: [sdb] tag#2 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN Feb 10 02:06:52 UnBiggerBoy kernel: sd 4:0:0:0: [sdb] tag#2 CDB: opcode=0x28 28 00 32 24 82 e0 00 01 00 00 Feb 10 02:06:52 UnBiggerBoy kernel: sd 4:0:0:0: [sdb] tag#1 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD OUT Feb 10 02:06:52 UnBiggerBoy kernel: sd 4:0:0:0: [sdb] tag#1 CDB: opcode=0x2a 2a 00 38 9a 56 68 00 00 30 00 Feb 10 02:06:52 UnBiggerBoy kernel: sd 4:0:0:0: [sdb] tag#0 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN Feb 10 02:06:52 UnBiggerBoy kernel: sd 4:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 32 24 83 e0 00 01 00 00 Feb 10 02:06:53 UnBiggerBoy kernel: sd 4:0:0:0: [sdb] tag#4 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD OUT Feb 10 02:06:53 UnBiggerBoy kernel: sd 4:0:0:0: [sdb] tag#4 CDB: opcode=0x2a 2a 00 3b 9e a9 40 00 01 40 00 Feb 10 02:07:24 UnBiggerBoy kernel: sd 4:0:0:0: [sdb] tag#3 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD Feb 10 02:07:24 UnBiggerBoy kernel: sd 4:0:0:0: [sdb] tag#3 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00 Feb 10 02:07:32 UnBiggerBoy kernel: sd 4:0:0:0: [sdb] tag#5 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD IN Feb 10 02:07:32 UnBiggerBoy kernel: sd 4:0:0:0: [sdb] tag#5 CDB: opcode=0x85 85 08 0e 00 00 00 01 00 00 00 00 00 00 00 ec 00 Feb 10 02:07:32 UnBiggerBoy kernel: scsi host4: uas_eh_device_reset_handler start Feb 10 02:07:32 UnBiggerBoy kernel: usb 4-2: reset SuperSpeed Plus Gen 2x1 USB device number 3 using xhci_hcd Feb 10 02:07:32 UnBiggerBoy kernel: scsi host4: uas_eh_device_reset_handler success Feb 10 02:07:42 UnBiggerBoy kernel: sd 4:0:0:0: [sdb] tag#2 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD Feb 10 02:07:42 UnBiggerBoy kernel: sd 4:0:0:0: [sdb] tag#2 CDB: opcode=0x0 00 00 00 00 00 00 Feb 10 02:07:42 UnBiggerBoy kernel: scsi host4: uas_eh_device_reset_handler start Feb 10 02:07:48 UnBiggerBoy kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command Feb 10 02:07:54 UnBiggerBoy kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command Feb 10 02:07:54 UnBiggerBoy kernel: usb 4-2: device not accepting address 3, error -62 Feb 10 02:08:00 UnBiggerBoy kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command Feb 10 02:08:05 UnBiggerBoy kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command Feb 10 02:08:06 UnBiggerBoy kernel: usb 4-2: device not accepting address 3, error -62 Feb 10 02:08:11 UnBiggerBoy kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command Feb 10 02:08:17 UnBiggerBoy kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command Feb 10 02:08:17 UnBiggerBoy kernel: usb 4-2: device not accepting address 3, error -62 Feb 10 02:08:22 UnBiggerBoy kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command Feb 10 02:08:28 UnBiggerBoy kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command Feb 10 02:08:28 UnBiggerBoy kernel: usb 4-2: device not accepting address 3, error -62 Feb 10 02:08:28 UnBiggerBoy kernel: scsi host4: uas_eh_device_reset_handler FAILED err -19 Feb 10 02:08:28 UnBiggerBoy kernel: sd 4:0:0:0: Device offlined - not ready after error recovery Feb 10 02:08:28 UnBiggerBoy kernel: usb 4-2: USB disconnect, device number 3 Feb 10 02:08:28 UnBiggerBoy kernel: sd 4:0:0:0: Device offlined - not ready after error recovery Feb 10 02:08:28 UnBiggerBoy kernel: sd 4:0:0:0: Device offlined - not ready after error recovery Feb 10 02:08:28 UnBiggerBoy kernel: sd 4:0:0:0: Device offlined - not ready after error recovery Feb 10 02:08:28 UnBiggerBoy kernel: sd 4:0:0:0: Device offlined - not ready after error recovery Feb 10 02:08:28 UnBiggerBoy kernel: sd 4:0:0:0: Device offlined - not ready after error recovery Feb 10 02:08:28 UnBiggerBoy kernel: sd 4:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=125s Feb 10 02:08:28 UnBiggerBoy kernel: sd 4:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 32 24 83 e0 00 01 00 00 Feb 10 02:08:28 UnBiggerBoy kernel: I/O error, dev sdb, sector 841253856 op 0x0:(READ) flags 0x80700 phys_seg 32 prio class 2 Feb 10 02:08:28 UnBiggerBoy kernel: sd 4:0:0:0: [sdb] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=125s Feb 10 02:08:28 UnBiggerBoy kernel: sd 4:0:0:0: [sdb] tag#2 CDB: opcode=0x28 28 00 32 24 82 e0 00 01 00 00 Feb 10 02:08:28 UnBiggerBoy kernel: I/O error, dev sdb, sector 841253600 op 0x0:(READ) flags 0x80700 phys_seg 32 prio class 2 Feb 10 02:08:28 UnBiggerBoy kernel: device offline error, dev sdb, sector 1000253696 op 0x1:(WRITE) flags 0x9800 phys_seg 8 prio class 2 Feb 10 02:08:28 UnBiggerBoy kernel: device offline error, dev sdb, sector 1000253760 op 0x1:(WRITE) flags 0x9800 phys_seg 40 prio class 2 Feb 10 02:08:28 UnBiggerBoy kernel: device offline error, dev sdb, sector 841253752 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2 Feb 10 02:08:28 UnBiggerBoy kernel: device offline error, dev sdb, sector 949638760 op 0x1:(WRITE) flags 0x100000 phys_seg 6 prio class 2 Feb 10 02:08:28 UnBiggerBoy kernel: device offline error, dev sdb, sector 841253600 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Feb 10 02:08:28 UnBiggerBoy kernel: XFS (sdb1): log I/O error -19 Feb 10 02:08:28 UnBiggerBoy kernel: device offline error, dev sdb, sector 949638808 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 2 Feb 10 02:08:28 UnBiggerBoy kernel: XFS (sdb1): Filesystem has been shut down due to log error (0x2). Feb 10 02:08:28 UnBiggerBoy kernel: device offline error, dev sdb, sector 949639832 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 2 Feb 10 02:08:28 UnBiggerBoy kernel: XFS (sdb1): Please unmount the filesystem and rectify the problem(s). Feb 10 02:08:28 UnBiggerBoy kernel: device offline error, dev sdb, sector 949640856 op 0x1:(WRITE) flags 0x100000 phys_seg 24 prio class 2 Feb 10 02:08:28 UnBiggerBoy kernel: XFS (sdb1): log I/O error -19 Feb 10 02:08:28 UnBiggerBoy kernel: sdb1: writeback error on inode 1342222673, offset 0, sector 949624024 Feb 10 02:08:28 UnBiggerBoy kernel: XFS (sdb1): log I/O error -19 Feb 10 02:08:28 UnBiggerBoy kernel: XFS (sdb1): log I/O error -19 Feb 10 02:08:28 UnBiggerBoy kernel: XFS (sdb1): log I/O error -19 Feb 10 02:08:28 UnBiggerBoy kernel: XFS (sdb1): log I/O error -19 Feb 10 02:08:30 UnBiggerBoy kernel: sd 4:0:0:0: [sdb] Synchronizing SCSI cache Feb 10 02:08:30 UnBiggerBoy kernel: sd 4:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=DRIVER_OK Feb 10 02:08:36 UnBiggerBoy kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command Feb 10 02:08:41 UnBiggerBoy kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command Feb 10 02:08:41 UnBiggerBoy kernel: usb 4-2: device not accepting address 4, error -62 Feb 10 02:08:47 UnBiggerBoy kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command Feb 10 02:08:52 UnBiggerBoy kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command Feb 10 02:08:53 UnBiggerBoy kernel: usb 4-2: device not accepting address 5, error -62 Feb 10 02:08:53 UnBiggerBoy kernel: usb usb4-port2: attempt power cycle Feb 10 02:08:59 UnBiggerBoy kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command Feb 10 02:09:04 UnBiggerBoy kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command Feb 10 02:09:04 UnBiggerBoy kernel: usb 4-2: device not accepting address 6, error -62 Feb 10 02:09:10 UnBiggerBoy kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command Feb 10 02:09:15 UnBiggerBoy kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command Feb 10 02:09:16 UnBiggerBoy kernel: usb 4-2: device not accepting address 7, error -62 Feb 10 02:09:16 UnBiggerBoy kernel: usb usb4-port2: unable to enumerate USB device Feb 10 02:10:30 UnBiggerBoy kernel: traps: smartctl_type[137092] general protection fault ip:8d4022 sp:7fff380af1e0 error:0 in php[600000+3ce000] Edited February 10, 20251 yr by JJones2003 found source
February 10, 20251 yr Community Expert If possible, try using a SATA port instead, if you only USB try a different port, different cable, or a different USB enclosure.
February 10, 20251 yr Author @JorgeBright now I’ve been using a das enclosure and it’s been working great for the past half year. If I don’t run anything with sonar/radar and don’t download anything the server runs fine with my Emby and plex containers running for weeks Edited February 10, 20251 yr by JJones2003
February 10, 20251 yr Community Expert 1 hour ago, JJones2003 said: If I don’t run anything with sonar/radar and don’t download anything the server runs fine with my Emby and plex containers running for weeks Probably emby and plex are only reading one disk at a time, but writing with parity must access multiple disks simultaneously.
February 10, 20251 yr Author @trurlI actually don’t have any parity drives in my build (yet). However, I took @JorgeB advice and for my external ssd im using to be my download cache. It seems to be working now…. It’s so weird I’ve been dealing with small errors on my server all week it’s been fun :).] Edit: I checked the downloads I had going for my nzb files and they most keep failing, and my Webui for unraid is frozen, I’ve read online in a reddit post that having a separate download ssd would help with bugginess on my server so I now have a secondary ssd download cache drive. But it still crashes my UI eventually and I cant figure out what’s going on cause I can’t see my logs. Edited February 10, 20251 yr by JJones2003 more info
February 10, 20251 yr Author I shutdown my NZBGet image and was able to screenshot this error in my logs:
February 10, 20251 yr Author I know what it’s saying about the brtfs error image corrupt because I unplugged the drive a second ago.
February 12, 20251 yr Author @trurl sorry for the late response I’ve been busy at work. It keeps giving me this error code and then shortly crashing the whole server after when downloading files in Sabnzbd. I’ve been using sabnzbd for a little under a year with no issues up to this point unbiggerboy-diagnostics-20250212-0902.zip
February 12, 20251 yr Community Expert Why do you have 80G docker.img? Have you had problems filling it? Not the cause of your problem, but appdata and system shares have files on the array.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.