January 12, 20251 yr Hi, When I upgraded to UNRAID 7 I had issues with none of my Docker containers working or my VMs starting properly so I assumed there was an issue with my cache drive. It shows up fine in the pool configuration and I can browse the files in the "appdata" share with no problem. My cache drive is in a USB NVME adapter so I tried shutting down and moving it to another USB port. That seemed to work for a couple of hours last night but I've woken up this morning to Docker not starting and my system log is absolutely rammed full of errors like: Jan 12 10:04:24 Server kernel: usb 3-4: USB disconnect, device number 63 Jan 12 10:04:24 Server kernel: blk_print_req_error: 60 callbacks suppressed Jan 12 10:04:24 Server kernel: I/O error, dev sda, sector 271446880 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Jan 12 10:04:24 Server kernel: btrfs_dev_stat_inc_and_print: 60 callbacks suppressed Jan 12 10:04:24 Server kernel: BTRFS error (device sda1: state EA): bdev /dev/sda1 errs: wr 35, rd 249237, flush 0, corrupt 0, gen 0 Jan 12 10:04:24 Server kernel: I/O error, dev loop2, sector 34047328 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 2 Jan 12 10:04:24 Server kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 37, rd 185904, flush 1, corrupt 0, gen 0 Jan 12 10:04:24 Server kernel: I/O error, dev sda, sector 271646336 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Jan 12 10:04:24 Server kernel: BTRFS error (device sda1: state EA): bdev /dev/sda1 errs: wr 35, rd 249238, flush 0, corrupt 0, gen 0 Jan 12 10:04:24 Server kernel: I/O error, dev loop2, sector 34571616 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 2 Jan 12 10:04:24 Server kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 37, rd 185905, flush 1, corrupt 0, gen 0 Jan 12 10:04:24 Server kernel: I/O error, dev sda, sector 271446880 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Jan 12 10:04:24 Server kernel: BTRFS error (device sda1: state EA): bdev /dev/sda1 errs: wr 35, rd 249239, flush 0, corrupt 0, gen 0 Jan 12 10:04:24 Server kernel: I/O error, dev loop2, sector 34047328 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 2 Jan 12 10:04:24 Server kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 37, rd 185906, flush 1, corrupt 0, gen 0 Jan 12 10:04:24 Server kernel: I/O error, dev sda, sector 271646336 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Jan 12 10:04:24 Server kernel: BTRFS error (device sda1: state EA): bdev /dev/sda1 errs: wr 35, rd 249240, flush 0, corrupt 0, gen 0 Jan 12 10:04:24 Server kernel: I/O error, dev loop2, sector 34571616 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 2 Jan 12 10:04:24 Server kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 37, rd 185907, flush 1, corrupt 0, gen 0 Jan 12 10:04:25 Server kernel: I/O error, dev sda, sector 271446880 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Jan 12 10:04:25 Server kernel: BTRFS error (device sda1: state EA): bdev /dev/sda1 errs: wr 35, rd 249241, flush 0, corrupt 0, gen 0 Jan 12 10:04:25 Server kernel: I/O error, dev loop2, sector 34047328 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 2 Jan 12 10:04:25 Server kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 37, rd 185908, flush 1, corrupt 0, gen 0 There are hundreds of them over and over again. I'm not sure if this is related though as it mentions /dev/loop2, but I'm at a loss. Can anyone assist please? Thanks server-diagnostics-20250112-0941.zip Edited January 12, 20251 yr by CodeThief More relevant logs
January 12, 20251 yr Author In the meantime I've downgraded back to 6.12.14 and everything is working perfectly again. Docker and VMs back up and running and no BTRFS errors in the system log. If anyone can see what's gone wrong in my diagnostics I'd still appreciate it as I'd like to upgrade. Thanks!
January 12, 20251 yr Community Expert Looks like USB problems, note that USB is not recommended for array or pool devices, please post the output from lsusb -t from v6 and v7
January 13, 20251 yr Author Here's the output from v6. Unfortunately I won't be going back to v7 in the near future if USB is the problem as I can't connect my cache drive in any other way without a new motherboard /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 10000M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M |__ Port 4: Dev 78, If 0, Class=Human Interface Device, Driver=usbfs, 1.5M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/3p, 10000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/9p, 480M |__ Port 8: Dev 2, If 0, Class=Vendor Specific Class, Driver=usbfs, 12M Assuming that you were referring to the USB disconnect in the logs then I guess 3-4 is my UNRAID boot flash drive? Thanks for the reply! Edited January 13, 20251 yr by CodeThief
January 13, 20251 yr Community Expert I would need the same output from v7, you can get it without starting the array.
January 13, 20251 yr Author Sure, I understand. It appears I have the same USB disconnect log messages in v6 with the same device port(?), just without the BTRFS errors. The hid-generic log entry underneath each mentions the model number of my UPS so I guess that's the device that's constantly bouncing on and offline and is probably a red-herring and not the cause of the BTRFS errors: Jan 12 12:11:53 Server kernel: usb 3-4: USB disconnect, device number 70 Jan 12 12:11:56 Server kernel: usb 3-4: new low-speed USB device number 71 using xhci_hcd Jan 12 12:11:56 Server kernel: hid-generic 0003:0764:0501.01BC: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1600ELCD] on usb-0000:26:00.3-4/input0 Jan 12 12:12:04 Server kernel: usb 3-4: USB disconnect, device number 71 Jan 12 12:12:07 Server kernel: usb 3-4: new low-speed USB device number 72 using xhci_hcd Jan 12 12:12:08 Server kernel: hid-generic 0003:0764:0501.01BD: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1600ELCD] on usb-0000:26:00.3-4/input0 Jan 12 12:12:16 Server kernel: usb 3-4: USB disconnect, device number 72 Jan 12 12:12:19 Server kernel: usb 3-4: new low-speed USB device number 73 using xhci_hcd Jan 12 12:12:19 Server kernel: hid-generic 0003:0764:0501.01BE: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1600ELCD] on usb-0000:26:00.3-4/input0 Jan 12 12:12:27 Server kernel: usb 3-4: USB disconnect, device number 73 Jan 12 12:12:30 Server kernel: usb 3-4: new low-speed USB device number 74 using xhci_hcd Jan 12 12:12:30 Server kernel: hid-generic 0003:0764:0501.01BF: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1600ELCD] on usb-0000:26:00.3-4/input0 Jan 12 12:12:38 Server kernel: usb 3-4: USB disconnect, device number 74 Jan 12 12:12:41 Server kernel: usb 3-4: new low-speed USB device number 75 using xhci_hcd Jan 12 12:12:41 Server kernel: hid-generic 0003:0764:0501.01C0: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1600ELCD] on usb-0000:26:00.3-4/input0 Jan 12 12:12:49 Server kernel: usb 3-4: USB disconnect, device number 75 Jan 12 12:12:52 Server kernel: usb 3-4: new low-speed USB device number 76 using xhci_hcd Jan 12 12:12:52 Server kernel: hid-generic 0003:0764:0501.01C1: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1600ELCD] on usb-0000:26:00.3-4/input0 Jan 12 12:13:00 Server kernel: usb 3-4: USB disconnect, device number 76 Jan 12 12:13:03 Server kernel: usb 3-4: new low-speed USB device number 77 using xhci_hcd Jan 12 12:13:04 Server kernel: hid-generic 0003:0764:0501.01C2: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1600ELCD] on usb-0000:26:00.3-4/input0 Thanks for your help Jorge, but unfortunately I won't be rebooting back into v7 as I have some quite important VMs that I can't afford to have offline for long. I was playing with fire updating the other day I guess I'll leave it for a few months in case any bugs are discovered and fixed in a later version.
January 14, 20251 yr Hey JorgeB, I'm having the same problem and have a USB cache drive (not ideal i know). No issues after downgrading back to 6.12.10. I've attached my logs and here is the lsusb -t. Version 7 /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/7p, 480M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 5000M |__ Port 002: Dev 002, If 0, Class=Mass Storage, Driver=uas, 5000M |__ Port 003: Dev 003, If 0, Class=Mass Storage, Driver=usb-storage, 5000M Version 6 /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M |__ Port 3: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 480M If you need any more info let me know. ds9-diagnostics-20250114-0749.zip Edited January 14, 20251 yr by zippo
January 15, 20251 yr I am not having this exact error, but one that is similar. I notice that my docker containers stop working after a while, no matter if I try to stop the docker service and restart it, it never works again until I reboot my machine. When I went to check my syslog I saw it filled with the error like the below. Tower kernel: BTRFS error (device loop2: state EA): level verify failed on logical 46560034816 mirror 1 wanted 1 found 0 Pasted are my diagnostics to help troubleshoot. tower-diagnostics-20250114-1907.zip Edited January 15, 20251 yr by nurollinsiii41
January 15, 20251 yr Community Expert 14 hours ago, zippo said: I'm having the same problem and have a USB cache drive (not ideal i know). No issues after downgrading back to 6.12.10. I've attached my logs and here is the lsusb -t. Try adding this to syslinux.cfg, after /bzroot: usb_storage.quirks=090c:1000:u The reboot and retest.
January 15, 20251 yr Community Expert 9 hours ago, nurollinsiii41 said: I am not having this exact error, but one that is similar. Next time, please start a new thread, or it can get confusing, even when it's the same problem. The diags are after a reboot, and the syslog-previous doesn't show the start of the problem, but post new diags after array start.
January 16, 20251 yr 17 hours ago, JorgeB said: Try adding this to syslinux.cfg, after /bzroot: usb_storage.quirks=090c:1000:u The reboot and retest. Thanks Jorge. Unfortunately that didn't make a difference. Just to confirm, here's my Syslinux: default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS menu default kernel /bzimage append initrd=/bzroot usb_storage.quirks=090c:1000:u label Unraid OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui label Unraid OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Unraid OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest I've also reattached my logs after the change. ds9-diagnostics-20250115-2033.zip
January 19, 20251 yr Hey Jorge, Here is my lsusb -t (I assume that is what you meant) from 6.12.10 after it has been up for a few days: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M |__ Port 3: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 480M I would do v7 but i can't run it for more than a little while since it causes all my docker containers to stop working. I suppose I could disable the cache drive but leave the USB drive plugged in and leave it running that way for a while if you think that would help.
January 19, 20251 yr Community Expert I would need to see it from v7, but you don't need to start the array to get it.
February 6, 20251 yr Hi Jorge. I just now found the time to run through the upgrade again. Here's my v7 lsusb -t /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/7p, 480M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 5000M |__ Port 002: Dev 002, If 0, Class=Mass Storage, Driver=uas, 5000M |__ Port 003: Dev 003, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
February 6, 20251 yr Community Expert It's still using the uasp driver, to confirm the IDs post the output from, lsusb -vt and sorry, could have asked for that in the first place
February 7, 20251 yr no worries, here is it is: 7.0 lsusb -vt /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/7p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 5000M ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 002: Dev 002, If 0, Class=Mass Storage, Driver=uas, 5000M ID 054c:087d Sony Corp. |__ Port 003: Dev 003, If 0, Class=Mass Storage, Driver=usb-storage, 5000M ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive Thanks for all your help
February 7, 20251 yr Community Expert The USB quirk was set for the wrong device, change it on syslinux.cfg to: usb_storage.quirks=054c:087d:u Then reboot
February 12, 20251 yr On 2/7/2025 at 12:00 AM, JorgeB said: The USB quirk was set for the wrong device, change it on syslinux.cfg to: usb_storage.quirks=054c:087d:u Then reboot That seems to have done the trick! Thank you Jorge!
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.