foxythefoxer

Your change appears to have fixed the issue for me at least. I was getting the Torguard Kernel problem everyone was previously describing.

To roll back you need to manually specify a version. If nothing is specified it will use :latest. but you can figure out the older tags from the github page. To go to the github page you click on the docker container and selecting 'More Info' So to rollback to the stable version before this bug. click on Qbittorrent and 'Edit' Change the Repository to this binhex/arch-qbittorrentvpn:5.1.1-1-01

I also do not have Mover Tuning Plugin. This Post was the fix for me. Thank you for sharing.

Holy crap. THANK YOU. I was tearing my hair out trying to figure out why Mover seemingly just wasn't doing anything. I was freaking out when my Cache Drive was filling up and not moving anything to my data share on the array even when i manually invoke the Mover command. my "data" share had inexplicably been renamed to "Data". Do you think this is some bug upgrading to Unraid 7.x ? I feel like there should be a PSA about this. Because nothing in the Unraid Gui gives any indication that there is anything different/wrong. For anyone who finds this post. If you have a Cache Pool, and the you are sure that the share settings are correct try this fix. For me i have a "data" share where I store all my media. But I use the Cache Pool as the original location for faster writes. Primary Storage -> Cache Secondary Storage -> Array Here is the Fix. -Take note all your shares. (Capitalization matters) -Stop Array -Open terminal and cd /boot/config/shares -ls command to review all [share].cfg files you noted previously. -If you find one that doesn't EXACTLY match you can use the mv command to rename. -My example: mv /boot/config/shares/data /boot/config/shares/data1 -Then : mv /boot/config/shares/data1 /boot/config/shares/data -I rebooted the Server then started the Array Optional: -Unraid Settings > Scheduler > Mover Settings > Mover Logging: Enabled -Move Now -Unraid Tools > System Log > Scroll all the way down. You should see your files being moved. -Make sure you Disable Mover Logging afterwards.

Gotcha. That makes sense. So the Command and message need to wrapped in quotations like this rcon -a 172.17.0.2:25575 -p AdminDocker "Broadcast Server_Mesage" Perfect yep that works. My custom script looks very similar to what that commenter wrote, though theirs is more elegant, I'll read more on the following posts, thanks for the tip! Just want to say you do awesome work! I've only been using Unraid for a few months now and have been learning a lot reading your posts!

So I've run into a problem with this new rcon version. How would you use a server command that itself has an option. Example: Broadcast for Palworld. The --help documentation for the new version says: To run single mode type commands after options flags. Example: rcon -a 127.0.0.1:16260 -p password command1 command2 To run terminal mode just do not specify commands to execute. Example: rcon -a 127.0.0.1:16260 -p password This is fine in Single Mode with a command like Showplayers. It outputs what you would expect. rcon -a 172.17.0.2:25575 -p AdminDocker showplayers But a Palworld Broadcast message SHOULD be rcon -a 127.0.0.2:25575 -p AdminDocker Broadcast Server_Mesage However it fails because it's trying to use Server_Message as a command It does work in terminal mode, but that's no good if I'm scripting it. I'm needing a way to send automated messages on a schedule to warn players of an upcoming game server reboot.

Took me a bit to figure out what was going on. I only updated yesterday. Maybe consider editing this post for others when they search the forums? It was certainly how i figured out to properly script server broadcasts for my Palworld server. Also does this mean that the "timeout 1" condition before the command is no longer necessary?

Good Evening, I'm trying to mount and migrate existing data on a drive (Lets call it 16TB Western Digital) to my newly created Unraid tower and Array, and I'm looking for advice. I hope this is the correct place to post because I believe my issue is with Unassigned Devices not able to mount the drive. The Dev 1 in this screenshot is the drive in question. I expect it to give the option to Mount, but you can see that option isn't available. It is using ext4 file system because I was previously using it in Ubuntu. I still have the boot drive for Ubuntu (it is actually the Dev2 shown) and when i boot back into that OS (which is the same computer, I just change the boot order in mobo bios) the drive mounts fine in ubuntu. Here is the screenshot of Gnome Disks in ubuntu showing it's Ext4 Which I click on "Disk Log Information" these are the logs. I would guess it's something to do with that "'Terminated' Signal received." Attached is Unraid Diagnostic logs, and i've tried to review them myself but I can't seem to figure out why it won't mount. fractalnode-804-diagnostics-20231216-1850.zip