Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

JJones2003

Members
  • Joined

  • Last visited

Everything posted by JJones2003

  1. 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]
  2. @echoing-backseat4387Hey were you able to figure out what was wrong with your server? I have been having the exact same issue you’ve been experiencing.
  3. @JorgeB thanks again! Will do this after I get home from work.
  4. @JorgeBhate to keep asking you questions but by you saying back up the cache you mean to the array right? And then after reformatting copying it over and then everything should work as it did before with the files removed?
  5. @JorgeB if I do a backup wouldn’t it still be corrupted once I add it all back to the cache?
  6. Hello, I recently had a corrupt cache drive that I was able to thankfully recover most of the data. However, there are six more files I need to delete and I’m not too sure where they are. I read the logs that are created and they do tell me where the corruption is drive-wise, but I can’t find where in that specific drive it is after I finish doing a scrub - it gives me general information as to where it is but I don’t know where to look. If anyone could help me I’d appreciate it.
  7. @JorgeB Thank you sir. After doing what you said with scrubbing the drive I found what was corrupted in the logs. Thankfully it was my plex media server of which I have a backup saved in array and everything works again. Thanks again for all the help given. Gentleman and a scholar
  8. heres the results of the scrub: UUID: b374d000-020f-47af-8f1a-79720960db22 Scrub started: Thu Jan 30 11:24:00 2025 Status: finished Duration: 0:04:26 Total to scrub: 213.83GiB Rate: 823.18MiB/s Error summary: verify=604 csum=79965 Corrected: 80369 Uncorrectable: 200 Unverified: 0
  9. @JorgeBOoooh I thought you were talking about the array ill run it on the cache pool. Reason I was thinking it was my array drive was someone on a different reddit said something could be wrong with that so I assumed that’s what you were talking about.
  10. @JorgeB Would you suggest doing this with the dynamix file integrity plugin? The only way I seem to be able to do it is with that. Another thing that’s been happening that is happening as I write this is that some docker containers will return an error when i am trying to start them. For instance my Plex, Sonarr radarr and pretty much everything is running fine right now, but my photoprisim returns with the “Execution Error” screen popup.
  11. Hello, so I’ve had UnRaid about a year and it’s been working great with my current set up. However these past two months I’ve been having very strange issues. Lately it’s gotten really bad. Some dockers crash my entire server. I can’t transfer files to external ssd’s anymore. I’ve put my log and my diagnostics in with this post. If someone could help me out I’d really appreciate it. KINGSTON_OM8SEP4512N-A0_50026B7381ED49A7-2024-11-26 cache (nvme0).txt unbiggerboy-syslog-20250130-0524.zip

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.