ich777

No not really but this could be also a reason why it's not working. I can only thing of a permission issue. Run from a terminal something like this: chmod -R 777 "/mnt/user/disks/Seagate Backup 6TB" chown -R 99:100 "/mnt/user/disks/Seagate Backup 6TB" (please change the path to the disks if it's not correct, I've read that from your screenshot - typos included... ) I would also recommend that you first change the name from the partition to something without spaces. Spaces are never really good in Linux, at least from my experience.

Warum lässt du den so oft laufen? Nur meine persönliche Meinung aber das genügt Quartalsmäßig, also alle 3 Monate... Und genau das hat dir @alturismo hier gezeigt, du willst das er bis 6Uhr morgens läuft also stellst du bei "Increment pause time" 06:00 ein und du willst das er ab 22Uhr weiter läuft also stellst du bei "Increment resume time" 22:00 ein, die "Increment frequency" stellst auf Daily (damit er das jeden Tag so macht) und die anderen Einstellungen lässt du so wie im Screenshot von @alturismo. Tipp: wenn du das auch für manuell ausgelöste Parity Checks aktivieren willst dann musst du "Use increments for manual Parity Check" auch auf Yes stellen.

You have to fix the startup commands, or at least the variables from "GAME_PARAMS" yourself in the template since my templates doesn't update itself if I change anything, see this post here how to do it: Should be enough to change it like:

Are you sure that it's set to read/write and not only to read? I think you aren't running luckyBackup as root?

Ist der Sync auf einem Unassigned Devices Share/Platte?

In the Docker template in the mount point (EDIT button) make sure to select Read/Write Slave.

This drive is mounted through UD or am I wrong, how did you mount it? Have you selected "Read/Write Slave"?

I would recommend to use XFS or ext4

First would be to don't use NTFS or you could also tick the checkbox in the advanced settings for the sync that this is a sync to a Windows filesystem.

Linuxsserver oder? Ich hab mit denen eigentlich nichts zu tuhen. Funktioniert auch in meinem Debian container. Würd aber eher Chromium empfehlen da es das nativ für die ganzen Linux Distributionen gibt. Hab übrigens auch einen Chromium container in der CA App mit der nix installiert werden muss, nur Chromium über VNC.

Von meiner Seite eher nein, sorry. Ein Forum ist genug für mich, ich möchte auch noch ein Leben haben und momentan bin ich sowieso grad ziemlich ausgelastet im echten Leben.

What? Ist das echt dein Ernst? Das wärst der erste der das so empfindet. Für was willst du ein eigenes Forum? Ist doch so üblich das Englisch die Hauptsprache ist (wenn es denn kein rein deutsches Forum ist) und es dann Unterforen mit den jeweiligen Sprachen gibt. Linus Tech Tips? Du meinst vermutlich LT also Limetech oder? @mgutt was sagst du hierzu...

What path have you choosen for LXC? Please keep in mind that I never recommend that you don‘t use the FUSE path /mnt/user/… always use the real path like /mnt/cache/… or /mnt/diskX/… (like described on the plugin configuration page).

@alexmercer I would not describe this as a solution because if you want to use the LXC plugin it's definitely not solved... What path did you choose for LXC? EDIT: As described in the plugin, please don't use the FUSE file path /mnt/user/... use the real path instead, for example /mnt/cache/lxc or /mnt/disk1/lxc or on whatever disk your lxc share is on. **The following is not related to LXC but please also give this attention** EDIT2: From what I see in your syslog, your i915 module crashed after activating it: May 28 13:00:27 AlexStation kernel: i915 0000:00:02.0: drm_WARN_ON(!IS_PLATFORM(dev_priv, INTEL_SKYLAKE) && !IS_PLATFORM(dev_priv, INTEL_KABYLAKE)) May 28 13:00:27 AlexStation kernel: WARNING: CPU: 2 PID: 3893 at drivers/gpu/drm/i915/intel_pch.c:61 intel_pch_type+0x560/0x9d2 [i915] May 28 13:00:27 AlexStation kernel: Modules linked in: i915(+) iosf_mbi i2c_algo_bit ttm drm_kms_helper drm intel_gtt agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops efivarfs ip6table_filter ip6_tables iptable_filter ip_tables x_tables bonding e1000e r8169 realtek x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel nvme crypto_simd cryptd rapl intel_cstate intel_uncore i2c_i801 i2c_smbus i2c_core nvme_core ahci libahci fan thermal video backlight acpi_pad button [last unloaded: e1000e] May 28 13:00:27 AlexStation kernel: CPU: 2 PID: 3893 Comm: modprobe Tainted: G U 5.15.43-Unraid #1 May 28 13:00:27 AlexStation kernel: Hardware name: BIOSTAR Group GAMING H170T/GAMING H170T, BIOS 5.12 09/17/2021 May 28 13:00:27 AlexStation kernel: RIP: 0010:intel_pch_type+0x560/0x9d2 [i915] May 28 13:00:27 AlexStation kernel: Code: 4c 8b 67 50 4d 85 e4 75 03 4c 8b 27 e8 38 7c 10 e1 48 c7 c1 0a b1 58 a0 4c 89 e2 48 c7 c7 9d ae 58 a0 48 89 c6 e8 93 80 3c e1 <0f> 0b b8 04 00 00 00 e9 62 04 00 00 48 85 ff 74 04 48 8b 7f 08 48 May 28 13:00:27 AlexStation kernel: RSP: 0018:ffffc9000397fb80 EFLAGS: 00010282 May 28 13:00:27 AlexStation kernel: RAX: 0000000000000000 RBX: ffff88814b520000 RCX: 0000000000000027 May 28 13:00:27 AlexStation kernel: RDX: 0000000000000003 RSI: ffffc9000397fa08 RDI: ffff888267d1c510 May 28 13:00:27 AlexStation kernel: RBP: 000000000018a100 R08: ffffffff822b4e28 R09: 0000000000000000 May 28 13:00:27 AlexStation kernel: R10: 000000000000005c R11: 0000000000000210 R12: ffff8881010503e0 May 28 13:00:27 AlexStation kernel: R13: ffff88810018a144 R14: ffff88814b526bb0 R15: ffff88814b5207d0 May 28 13:00:27 AlexStation kernel: FS: 0000152660836740(0000) GS:ffff888267d00000(0000) knlGS:0000000000000000 May 28 13:00:27 AlexStation kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 May 28 13:00:27 AlexStation kernel: CR2: 000015266066f000 CR3: 0000000106062003 CR4: 00000000003706e0 May 28 13:00:27 AlexStation kernel: Call Trace: May 28 13:00:27 AlexStation kernel: <TASK> May 28 13:00:27 AlexStation kernel: intel_detect_pch+0x7a/0x1e2 [i915] May 28 13:00:27 AlexStation kernel: i915_driver_probe+0x27e/0xb81 [i915] May 28 13:00:27 AlexStation kernel: ? _raw_spin_unlock_irqrestore+0x19/0x1b May 28 13:00:27 AlexStation kernel: local_pci_probe+0x44/0x85 May 28 13:00:27 AlexStation kernel: pci_device_probe+0x145/0x197 May 28 13:00:27 AlexStation kernel: really_probe+0x11e/0x2e8 May 28 13:00:27 AlexStation kernel: __driver_probe_device+0x91/0xc0 May 28 13:00:27 AlexStation kernel: driver_probe_device+0x1e/0x73 May 28 13:00:27 AlexStation kernel: __driver_attach+0xb1/0xc5 May 28 13:00:27 AlexStation kernel: ? __device_attach_driver+0x85/0x85 May 28 13:00:27 AlexStation kernel: bus_for_each_dev+0x74/0xa9 May 28 13:00:27 AlexStation kernel: bus_add_driver+0x108/0x1b9 May 28 13:00:27 AlexStation kernel: driver_register+0x9e/0xd7 May 28 13:00:27 AlexStation kernel: i915_init+0x20/0x8f [i915] May 28 13:00:27 AlexStation kernel: ? 0xffffffffa068f000 May 28 13:00:27 AlexStation kernel: do_one_initcall+0x78/0x178 May 28 13:00:27 AlexStation kernel: ? do_init_module+0x23/0x1f9 May 28 13:00:27 AlexStation kernel: ? kmem_cache_alloc_trace+0x11f/0x146 May 28 13:00:27 AlexStation kernel: do_init_module+0x4b/0x1f9 May 28 13:00:27 AlexStation kernel: __do_sys_init_module+0xb6/0xf5 May 28 13:00:27 AlexStation kernel: do_syscall_64+0x83/0xa5 May 28 13:00:27 AlexStation kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae May 28 13:00:27 AlexStation kernel: RIP: 0033:0x15266096d18a May 28 13:00:27 AlexStation kernel: Code: 48 8b 0d e1 7c 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d ae 7c 0c 00 f7 d8 64 89 01 48 May 28 13:00:27 AlexStation kernel: RSP: 002b:00007ffd5867e578 EFLAGS: 00000246 ORIG_RAX: 00000000000000af May 28 13:00:27 AlexStation kernel: RAX: ffffffffffffffda RBX: 00000000004293a0 RCX: 000015266096d18a May 28 13:00:27 AlexStation kernel: RDX: 0000000000428780 RSI: 00000000004705d0 RDI: 00001526601ff010 May 28 13:00:27 AlexStation kernel: RBP: 00001526601ff010 R08: 0000000000000007 R09: 0000000000428330 May 28 13:00:27 AlexStation kernel: R10: 0000000000000001 R11: 0000000000000246 R12: 0000000000428780 May 28 13:00:27 AlexStation kernel: R13: 0000000000000000 R14: 00000000004294b0 R15: 00000000004293a0 May 28 13:00:27 AlexStation kernel: </TASK> May 28 13:00:27 AlexStation kernel: ---[ end trace d4df3113f797b978 ]--- Maybe try to disable VT-d in your BIOS if you don't need it, this might solves this issue. EDIT3: Please remove this entry from your go file if you got the Intel-GPU-TOP or Intel-GVT-g plugin installed: #Setup drivers for hardware transcoding in Plex modprobe i915 ***line removed*** chmod 0777 /dev/dri/* May I also ask why you got the GVT-g plugin installed? You have no VMs installed where you make use of it, it would be better to stick to the Intel-GPU-TOP plugin if you only want to use your iGPU for transcoding for Plex. EDIT4: Please also consider upgrading to 6.10.3 because this is the latest version. I can only tell that I've also use LXC on a daily basis on my server and I've rebooted multiple times and have no issue whatsoever, not on my test server and not on my productive server (I use on both of the machines "/mnt/cache/lxc" as a path in the LXC settings) :

Have you yet updated the plugin to version 2022.07.12? A little bit of background information would be helpful… Which path have you choosen for LXC? Can you provide the Diagnostics?

Where? I thin you mean P8, P0 is the highest power state. Also, where is the script? I can‘t think of a reason why it shouldn‘t be the same on any version prior to 6.10.3 As said above without anything I can‘t help, the Diagnostics would be also helpful. BTW this is not an issue with this plugin and I think this would be better suited in the VM subforums since this is a VM related question.

Haven't got time to look into this, also don't know what 7DtD have to do with ArmA3. These are two different engines from what I know. I will fix this but I'm very busy at the moment in real life and this will take some time.

The container has a built in backup function and should be activated automatically. Please go to your Valheim directory and look if you got a "Backup" folder in it. A recent update from Valheim wiped all save files, but there is nothing I can do about, rather the developers from Valheim messed up a bit I think.

For sure, please give me some time since I‘m really busy currently in real life. I will report back when I know more.

Please try the following: Delete the container Delete the folder for vrising that lives in your appdata directory Pull a fresh copy from the CA App and leave everything at default Hopefully this should solve the issue If it doesn't solves the issue I think it's related to your CPU... Isn't this a Core2Quad? I think it's possible that it doesn't support some instructions which are needed for the game to run.

Please update the container and try it again, both 64bit and 32bit are now working on my machine. Attached both logs: x86.txt x64.txt But I would recommend to use the x86 versions because of known limitations of the x64 versions and Segfaulting on some machines.

That‘s not entirely true because there are workaround so that you can get Windows to work with LXC/LXD (I actually only know a few tutorials which involves LXD to create such a container) This should be also possible on Unraid in combination with QEMU. Also ARM containers should be theoretically possible in combination with QEMU and LXC on Unraid but I have to look a little bit more into that when I have more time since I think the necessary QEMU libraries are missing on Unraid, that‘s why I locked the LXC plugin to x86_64 only currently. Agreed.

From what I see you are not running the container on Unraid or am I wrong? What OS are you using and which version from the OS? Please don't do the mapping like this... Rather I would recommend that you use it like /home/rust/steamcmd and /home/rust/rust otherwise you can run into various other issues. Please also keep in mind that if you run more than this game server from me then you can also use one steamcmd directory for multiple containers and point them to the same steamcmd directory. How much RAM do you have on the machine that you are try to run RUST on? Keep in mind that RUST needs lot's of RAM to run, on my machine it consumes about 13GB of RAM when starting up for the first time without Oxide mod enabled (that is most likely the case on your machine at the stage where it crashes on your system, but I think you must have plenty of RAM since you are creating a server for 120 players) : (the screenshot is taken after it fully started) After a second start it uses about 7GB of RAM as you can see here (this is also with Oxide Mod enabled) : I've now tried it on my server and it works without a hitch. Maybe try to first run it with: --env 'OXIDE_MOD=false' \ to let it create the world first and then change it to true, at least that is what I've did on my server. Maybe Oxide has some issues there, I can for sure try to set it to true in the first place and see if this works to if you want me to do that.

I think this is more of an issue with Intel-GPU-TOP or the driver itself that is currently implemented in Unraid 6.10.3, so this question would be better suited in the Intel-GPU-TOP thread. But I have to say, I've compiled the latest Intel-GPU-TOP version about 2 weeks ago from the latest available Intel-GPU-Tools and there is not much I can do about that if nothing is displayed. Bleeding edge hardware on Linux is never a good idea since it takes (most of the times) some time so that the software/drivers are updated to support the hardware.

Please update the container first and then create a variable like that: You will be now able to change the release channel from the game now. Hope that helps.