socono

I became too impatient and went ahead with the xfs_repair and it seems to have resolved the issue.

High level overview of recent events on my Server: 1. Parity Disked swapped out for larger size. Completed successfully no errors in logs. 2. Data disk (md2) swapped out for larger disk. During the rebuild, syslog noted some failed command: READ FPDMA QUEUED errors on two other data drives. Rebuild paused and server powered off to reset cables. 3. Server powered on and md1 and md6 both would not mount. However, the array autostarted and rebuild said it continued on md2. 4. Powered off server , sata cables replaced for md1 and md6 and powered on. ATA errors no longer seen in log for md1 and md6 but both will not mount. Log indicated corruptions. 5. Array put into maint. mode and xfs_repair run on both md1 and md6 successfully. 6. Array started and data rebuild for md2 continued. During this time the log begins to report XFS (md2): Corruption detected. Unmount and run xfs_repair. I let the rebuild complete. 7. After rebuild complete, ran xfs_repair -n on md2 and see the message Inode allocation btrees are too corrupted, skipping phases 6 and 7 which I have never seen before. Can I safely run xfs_repair on md2? Thanks for your time. tower-diagnostics-20220417-2145.zip

I had the same errors and found the comment in the below link about adding " --user telegraf:$(stat -c '%g' /var/run/docker.sock) " to the container parameters worked for me. https://github.com/influxdata/telegraf/issues/10050

And right after posting I find the new spot when selecting the container and it is in the drop down. Disregard!

Hello! from what I can tell, after my upgrade to 6.9, I no longer have the link at the far right of each container that would open up the log window for that specific container. In it's place is the arrows to re-arrange the start order. Was this moved somewhere else? Thanks for your assistance.

I'm working through the same problem. This started after the upgrade to 6.7.0 for me. I have 35 Docker containers on my list and about 5 of them no longer show the WebUI link in the drop down where they did before. Their Webui field in advance settings is defined and I've tried setting it to the actual link as well as using the http://[IP]:[PORT:8083]/ to no avail. Can't see anything in syslog or the Docker log that is complaining.

Wondering if someone can provide some safe steps I can take to get the firmware file 'BCM20702A1-0b05-17cb.hcd' into /lib/firmware ? I have read a variety of methods some have used to unpack bzroot and repackage with the new file, but I'm fairly new to this and do not want to mess around with what looks like a fairly vital component to the Unraid boot process. I see some mentions of using the go script to copy things in place but not sure if that is applicable to the firmware path. Thanks for any guidance / insight.

Hello, Just updated to 6.7.0 and am looking to pass a USB bluetooth into a docker container. The adapter is model ASUS USB-BT400 USB. The logs report this on insert: May 20 01:39:52 Tower kernel: Bluetooth: HCI device and connection manager initialized May 20 01:39:52 Tower kernel: Bluetooth: HCI socket layer initialized May 20 01:39:52 Tower kernel: Bluetooth: L2CAP socket layer initialized May 20 01:39:52 Tower kernel: Bluetooth: SCO socket layer initialized May 20 01:39:53 Tower kernel: usbcore: registered new interface driver btusb May 20 01:39:53 Tower kernel: Bluetooth: hci0: BCM: chip id 63 May 20 01:39:53 Tower kernel: Bluetooth: hci0: BCM: features 0x07 May 20 01:39:53 Tower kernel: Bluetooth: hci0: BCM20702A May 20 01:39:53 Tower kernel: Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000 May 20 01:39:53 Tower kernel: bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0b05-17cb.hcd failed with error -2 May 20 01:39:53 Tower kernel: Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cb.hcd not found I can find that file on github. Not exactly sure where to put it on Unraid? Any help is appreciated. Thanks!

I had the problem as a few who have posted where right after install the UI is not available. Note the docker installer defaults to 'eth0' for the 'Interface' value. My interface on my Unraid local network is not eth0. Changed this value to br0 in my case and I can access the UI right after install now. So log into your Unraid console and do an ifconfig. find the interface with your IP on your local network and put that in the key for 'Container Variable: INTERFACE'