runraid

I was able to get it working by following this thread I installed "nerd tools" via community apps, went to the plugins tab in unraid and clicked the "nerd tools" icon... and then i searched for "bluez" and turned it on. Next I putting the following in my /boot/config/go file. I also ran all it manually once # Configure the Bluetooth driver sudo curl -L https://raw.githubusercontent.com/Realtek-OpenSource/android_hardware_realtek/rtk1395/bt/rtkbt/Firmware/BT/rtl8761b_config -o /tmp/rtl8761bu_config.bin sudo mv /tmp/rtl8761bu_config.bin /lib/firmware/rtl_bt/rtl8761bu_config.bin sudo curl -L https://raw.githubusercontent.com/Realtek-OpenSource/android_hardware_realtek/rtk1395/bt/rtkbt/Firmware/BT/rtl8761b_fw -o /tmp/rtl8761bu_fw.bin sudo mv /tmp/rtl8761bu_fw.bin /lib/firmware/rtl_bt/rtl8761bu_fw.bin # Start Bluetooth /etc/rc.d/rc.bluetooth start Then I had to unplug the usb device, plug it back in and running some combination of the following made it work /etc/rc.d/rc.bluetooth stop /etc/rc.d/rc.bluetooth start sudo bluetoothctl

Also +1'ing this. Home assistant now supports Bluetooth. Those of us running Home Assistant via docker will hit this issue. I'm not sure how to get the above work arounds working so as for now, I can't use the USB bluetooth receiver I bought to control bluetooth devices with Home Assistant.

Yeah but what I'm concerned about is the fact that something was changed from underneath me. I didn't make these changes but suddenly there's this https://myunraid.ru/ showing up in my unraid templates. My template completely changed, seemed to be changed by a 3rd party actor. These templates are weird - https://github.com/Muwahhidun/unraid-docker-templates and something nefarious seems to be going on. The githistory on that repo is very recent. Yet I was using the VPN template for two years. So how did my unraid switch to a new template? Let me know if this thread isn't the right place to talk about this. I will switch to your template (Thanks for providing it!)

Thanks. Looking at the history of this https://github.com/Muwahhidun/unraid-docker-templates/commits/main/my-openvpn-antizapret.xml i don't see how I would have switched to this container. I've been using this VPN container for like 2 years... and the git history shows it was recently created. I didn't make any changes to my VPN config at all... Do you have any idea how this could have been switched?

This is the template URL -- No idea how this was added https://raw.githubusercontent.com/Muwahhidun/unraid-docker-templates/main/my-openvpn-antizapret.xml

@ich777i'm very concerned and not sure what's going on right now. I upgraded my dperson/openvpn-client via the unraid "update all containers" and it's now pointing at something russia related. See the screenshot... anyone have any idea what this is?

I got this figured out and am able to use the MariaDB inside the container to make this work. No need to run a dedicated MariaDB docker instance. First, make sure the shinobipro docker container is running. Log into the console of the container, either by using the unraid feature or by this command: docker exec -ti shinobipro sh Next, create the database and tables... mysql source sql/framework.sql; source sql/user.sql; exit Now restart the container and it will work.

This should be, PRIVILEGES not PRIVILAGES. GRANT ALL PRIVILEGES ON shinobi.* TO 'shinobi' IDENTIFIED BY 'password';

Upgrading in hopes it fixes the SQLite db corruption problem many of us are plagued by since upgrading to 6.7.0

Support thread for the pgadmin Docker template. Application Name: pgadmin Application Site: https://www.pgadmin.org/ Docker Hub: https://hub.docker.com/r/fenglc/pgadmin4/ Application Github: https://github.com/postgres/pgadmin4 Template Github: https://github.com/rroller/unraid-templates Admins: Please configure https://github.com/rroller/unraid-templates for use with CA. Thanks!

USB stick is now in a USB 2.0 port (was a 3.0). Stopped the array. Rebooted the system. Came up with "unclean shutdown detected". It's now doing a full parity check. Nothing appears to have been lost (I love unraid). > Array Started•Parity-Check 0.1 %• Dynamix webGui v2017.03.30 I'm going to purchase a high quality USB stick. I wish unraid didn't depend on the USB stick though

Put the USB drive into my PC and it immediately said it had errors. Running checkdisk now. This is two USB sticks with issues in about 4 days.

Thanks all. I'll do a shutdown, USB swap, then parity check. I'll report back if it this happens again.

Also, it's showing as a flash drive and as Unmounted. See the attached pic.

@Squid when I did a shut down in the UI, at that time I was not having any USB issues. A day later (right now) I've started having the issue

@trurl Yes I did use the UI to shut down. But the odd thing is, when it started back up, it said I did an unclean shutdown and it had to do a full parity check. I might have been ssh'ed into the machine at that time which could have prevented a clean shutdown. For now on, I will stop the array, then do the shut down just to make sure I get a clean shutdown.

@trurl I shut it down a day or two ago, but things were fine until today. I did not do anything else on the machine. @Squid I want to say that I have it plugged into a USB 3 port (during both failures). I'll move to a USB 2 port.

I didn't shut the system down at all. Nor was I working on it. I just opened the UI and noticed the errors. The first time this happened, I had the USB stick plugged in the front USB port. The second time (this time), with a brand new, completely different USB stick, I have it plugged in the back USB port. Can I just unplug the USB stick to run checkdisk without my unraid server going down?

This is the second time that this has happened in 4 days. It's happened across two different USB sticks (brand new ones). I assume I need to replace the USB stick yet again? Apr 10 14:26:58 Tower kernel: FAT-fs (sda1): Directory bread(block 8199) failed Apr 10 14:26:58 Tower kernel: FAT-fs (sda1): Directory bread(block 8200) failed Apr 10 14:26:58 Tower kernel: FAT-fs (sda1): Directory bread(block 8201) failed Apr 10 14:27:01 Tower root: Apr 10 14:27:01 Tower root: Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php on line 35 Apr 10 14:27:01 Tower root: Apr 10 14:27:01 Tower root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39 Apr 10 14:27:07 Tower kernel: fat__get_entry: 150 callbacks suppressed Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8192) failed Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8193) failed Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8194) failed Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8195) failed Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8196) failed Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8197) failed Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8198) failed Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8199) failed Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8200) failed Apr 10 14:27:07 Tower kernel: FAT-fs (sda1): Directory bread(block 8201) failed Apr 10 14:27:16 Tower kernel: fat__get_entry: 54 callbacks suppressed Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8192) failed Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8193) failed Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8194) failed Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8195) failed Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8196) failed Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8197) failed Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8198) failed Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8199) failed Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8200) failed Apr 10 14:27:16 Tower kernel: FAT-fs (sda1): Directory bread(block 8201) failed Apr 10 14:27:25 Tower kernel: fat__get_entry: 54 callbacks suppressed Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8192) failed Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8193) failed Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8194) failed Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8195) failed Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8196) failed Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8197) failed Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8198) failed Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8199) failed Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8200) failed Apr 10 14:27:25 Tower kernel: FAT-fs (sda1): Directory bread(block 8201) failed