Leaderboard

Summary: Support Thread for ich777 Gameserver Dockers (CounterStrike: Source & ConterStrike: GO, TeamFortress 2, ArmA III,... - complete list in the second post) Application: SteamCMD DockerHub: https://hub.docker.com/r/ich777/steamcmd All dockers are easy to set up and are highly customizable, all dockers are tested with the standard configuration (port forwarding,...) if the are reachable and show up in the server list form the "outside". The default password for the gameservers if enabled is: Docker It there is a admin password the default password is: adminDocker Please read the discription of each docker and the variables that you install (some dockers need special variables to run). The Steam Username and Password is only needed in templates where the two fields are marked as requirde with the red * Created a Steam Group: https://steamcommunity.com/groups/dockersforunraid If you like my work, please consider making a donation

The unbalance plugin will do what you want, it's a graphical front end that utilizes rsync command line to do the work. There also is a procedure that takes some of the risk out of moving data off of one array member, emulated or not, where you exclude the drive from the global shares configuration. That will allow you to enable disk shares and "safely" copy from that disk to the user share system, which will allocate the data according to your split level and disk allocation strategy. If you don't GLOBALLY exclude the disk from user shares, not just the regular exclude, it's going to corrupt the data if you try to copy from disk to user share. Unbalance operates from disk to disk instead of user share, so it's not effected. Also, I'd recommend copying instead of moving. It will be faster, and have the same end result. You will have to rebuild parity without that disk after you get the data safe. In any case, I hope the rest of your drives are perfectly healthy, because you are relying on them to perform flawlessly for the entire duration of this procedure. You say you plan on upgrading, it would be safer to go ahead with the upgrade and rebuild on to a larger disk. You would be operating at risk for less time.

I'm glad I did a little bit of hunting. I have a Mac Pro from that same era. Officially a Mac Pro 2009, 4,1 flashed to work as a 2010/5,1. I have an identical kernel panic. By the looks of it, it has something to do with how the EFI passes off XHCI, which, mind, isn't something we can control. I'm going to try some tricks with Plop Boot Manager later, though. The only thread I can find, mind you, talks about changing usb drives, and that fixed it for him. Sucks for us.

Glad you like the script, thanks.

Thank you for this information!

White this may be somewhat advanced topic - I have heard from time to time that linux on Mac's can run into an issue or two. I guess what I'm saying is don't assume it will work like a PC does. It's possible it needs some kind of boot wrapper or a kernel boot option that you can enter at the beginning. I'd suggest you first google how to install generic linux on your Mac - if there's nothing special then it's probably OK. Then I'd suggest googling if there are any kernel issues with your version of Mac. The Kernel version can be retrieved via the command uname -r (as root). So for the latest Unraid it's Kernel 4.19.41-Unraid. Unraid probably has some customisations - but generally speaking there may be some info this way. Hope that helps.

Hey, i had similar issues with switching from afp to smb and i just registered to let you know how i solved it here. First of all i've seen that the console app and the log inside there told me that authentication did fail. So i went ahead and googled around and found this: https://apple.stackexchange.com/a/246244 This states that maybe some "security.plist" is broken, so i went ahead and looked at that file which was completely broken here. It was just a scramble of hex / asci mix and nowhere near valid xml. So i kept a copy and replaced it with the content from stack overflow <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>SecItemSynchronizable</key> <true/> </dict> </plist> This did not fix the issue but maybe together with the second step i took did: I went to the time machine prefpane and removed the disk again. Opened up a terminal and executed: sudo tmutil setdestination -ap smb://username@myserver/Backup This asked me for my local user password and the remote destination password, since then its working here. No changes were made to the smb conf files or extra confs and the setup is as all the screenshots here have shown. Hope that may helps some of you.

That hardware doesn't really seem appropriate for Unraid. What did you intend to have Unraid do with it?

This container runs in host mode, so you cannot and should not define any ports. Sent from my EML-L29 using Tapatalk

Depending on what exactly you did, be aware that it's probably not the whole computer that is routed through the VPN, most likely it's only the specific browser you configured.

Why? If you are indeed using binhex's delugevpn docker with the VPN enabled, privoxy is already installed and ready to use in his docker. Just set the variable ENABLE_PRIVOXY to yes, and add your server IP and port 8118 as an http proxy in your preferred browser.

You misunderstand parity protection as it applies to single disks. The mdX devices are protected by parity, so there is no difference in protection whether you use /mnt/user/appdata or /mnt/diskX/appdata. In either case a single disk failure is still emulated by parity. The only thing you are losing is the ability to automatically spread the ../appdata folder across multiple disks and use a single point of access, /mnt/user/appdata. BTW, parity doesn't provide a resilient filesystem, only device failure protection. Each disk has a separate independent file system. The /mnt/user fuse is just the combination of all the root folder paths on each separate disk.

As long as you ran the file system repair either from the Unraid GUI or from a command line against a /dev/mdX type device then parity will have been maintained (and updated appropriately as the repair took place). You can run a parity check if you like but it should not be necessary (although doing so will not do any harm either).

im not sure what this means, can you post a screenshot?

Start the array, disk should mount now.

Rebuilding a disk won't help with filesystem corruption, you need to check filesystem on disk17: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui or https://wiki.unraid.net/Check_Disk_Filesystems#Drives_formatted_with_XFS Seems to be relatively common some xfs disks going unmountable after a kernel upgrade, it happened before and it's happening to some users now, likely newer kernel is detecting some previous undetected corruption.

I just upgraded. During the reboot the machine had problems during the BIOS boot and I had to turn it off again. 6.7.0 then reported one disk as "Unmountable: No file system". I am not sure if this is a 6.7.0 problem or maybe a hardware glitch. I have reported it here:

You are not supposed to edit any files if changing ports. You just change the container template. If you already had it working, check your log. post it and the docker run command.

@Eadword: I have a thread opened for Docker Isolation with no replies, but you should add Linux namespaces / subuids for Docker to your list, as well as not using root and 777 permissions everywhere in the OS would be some good changes. It's been this way for a long time, I doubt it will change because unraid has always been a "don't expose to outside world" kind of distro for a long time.

Here is a script that will remove directories within a source directory less than a certain size limit. I used 100M, but you can change it to any size in MB. The script can be easily changed to KB, GB, TB etc... Don't forget to set your source directory. #!/bin/bash limit=100M source="/mnt/user/Movies" limit=$(echo $limit | cut -d 'M' -f 1) for dir in "$source"/*/ do size=$(du -sBM "$dir" | cut -d 'M' -f 1) if (( $limit > $size )) then echo remove: $dir rm -rf "$dir" fi done removeDirUnderSize.sh

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md https://www.privoxy.org/user-manual/quickstart.html Substitute 127.0.0.1:8118 with the IP of your unraid server and the privoxy port defined in the docker config.

You can plug your USB flash device into a PC and then make a backup (just drag contents to a temp folder on your desktop). Next use the USB Creator Tool to re-install Unraid OS on your flash. You can put the last version you were running, or try 6.7 again. Then copy the contents of your 'config' folder backup to the USB flash 'config' folder. If you had any custom 'syslinux' settings, you could restore that too. Eject flash, reboot server and 'should work' 👍

It's normal. /mnt/user = data on disks and cache /mnt/user0 = just data on disks

There's not a lot of support for Thunderbolt 3 YET... But I would say this is the way to go if investing in hardware right now. Plenty of future-proofing that way. Look up Linus Sebastian's home setup (Linus Tech Tips guy). He uses UnRaid to host VMs KVM-connected with TB3 card in server to TB3 docks via long optical cables. Rather expensive right now (100 foot optical TB3 cable is well over $200), but very elegant way to hook up a few KVM setups on the other side of the house. By the time you get cables & docks you're talking $500+ per connection. A few cheaper alternatives out there right now, if not using 4K. I hope to get into this type of thing at some point in my UnRaid adventures. I'll be acquiring a decent TB3 card for the server in not too distant future; can be used for all sorts of nifty USB connections for VMs. Sometime down the road I'll get a pcie extension/expansion card for more TB3 cards.

See this thread for some insight into how this is supposed to work.