ich777

I see that the plugin only tries to connect to one target? Do you have 2 different machines at home that you are trying to connect or the targets on the same machine? I see only one IQN with one Target in the log: iqn.2000-01.com.synology:Pegasus.Target-1.c85bc750ef What does the plugin page tell you which connections are established? One or two? If you don't use the targets in the Array or Cache you have to mount them through Unassigned Devices, otherwise you can't mount them properly.

Please use the directory /luckybackup/.ssh/ for your id_rsa.

But what's the benefit if you do so? Installing a driver for a non "installed" card?

I really don't recommend doing it that way because these firmware files are not tested with TBS-OS drivers and can cause actually crashes from what I found from my research, it only is working because TBS also offers a card with a similar tuner but not quite the same. Please be really careful with such things!

Yes, this would be my second recommendation. I personally use DigitalDevices cards and had not a single issue, TBS Cards are not that expensive with the benefit of having a dual tuner or even more and they are reliable too, my third recommendation would be something like a DVB Sky card that I use in my Test server (if you can find one, they are really hard to get these days).

You know that since Unraid 6.10.0-rc2 TPM is supported and emulated? You can also change your existing VM to use the built in TPM function in Unraid (as long as you are using as BIOS type OVMF): Click Exactly, you can use the GPU only in a VM (Guest) or on Unraid (Host). I would recommend that you are bind the card to VFIO in your System Devices page, reboot and try it again. If you have any further questions I would recommend that you post in the VM subforums since these are VM related questions.

You know that since Unraid 6.10.0-rc2 TPM is now available in Unraid and you can Windows 11 as usual. You even can change your VM to use the emulated TPM as long as you are using OVMF as BIOS type without any scripts,...: Click

Now I remember this device, it is not guaranteed that it works on Linux even if the description says it's supported because newer devices use a slightly different Chipset that is not fully supported. See this post from another user:

And with TBs OS it‘s detected? What happens when you do: ls -la /dev/dvb from a Unraid terminal? In general I don‘t recommend using USB tuners because they are often really unreliable.

May I ask why you are using the TBS package? This isn‘t a TBS Card… The TBS package also doesn‘t have the firmware files included, please use the LibreELEC package instead, reboot and post the Diagnostics again after reboot.

Don‘t use RDP, ise Parsec or VNC instead.

Please send me your logs after all this happened. Have you turned on Auto Mount in the Unassigned Devices plugin for this devices?

You have Windows 11 installed on 6.9.2? Do you have a modified version from Windows without TPM? TPM support was first built into Unraid with 6.10.0-RC2 Do you want to use the card in a VM? If yes I would strongly recommend that you bind it to VFIO. The driver from Unraid has nothing to do with Windows, keep in mind that no driver should be loaded on the Host when you try to use the card in a Guest system. Also if you want to use the card mainly in a VM this questions would be better suited in the VM subforums.

What driver package are you using and on what Unraid version are you? Can you please post your Diagnostics?

I think the amdgpu driver that is included with 6.9.2 is not fully compatible with your card: Mar 15 12:52:10 Unraid kernel: [drm:amdgpu_pci_remove [amdgpu]] *ERROR* Hotplug removal is not supported Mar 15 12:52:10 Unraid kernel: amdgpu 0000:11:00.0: amdgpu: amdgpu: finishing device. Mar 15 12:52:10 Unraid kernel: [drm] free PSP TMR buffer Mar 15 12:52:10 Unraid kernel: general protection fault, probably for non-canonical address 0x15ff006e69622e: 0000 [#1] SMP NOPTI Mar 15 12:52:10 Unraid kernel: CPU: 15 PID: 12870 Comm: daemon-init Not tainted 5.10.28-Unraid #1 Mar 15 12:52:10 Unraid kernel: Hardware name: System manufacturer System Product Name/ROG STRIX X570-F GAMING, BIOS 3604 04/14/2021 Mar 15 12:52:10 Unraid kernel: RIP: 0010:do_raw_spin_lock+0x7/0x12 Mar 15 12:52:10 Unraid kernel: Code: c3 b8 00 fe ff ff f0 0f c1 07 c3 31 c0 48 81 ff 68 d3 6b 81 72 0c 31 c0 48 81 ff 10 d5 6b 81 0f 92 c0 c3 31 c0 ba 01 00 00 00 <f0> 0f b1 17 74 04 89 c6 eb bb c3 8b 07 45 31 c0 85 c0 75 11 ba 01 Mar 15 12:52:10 Unraid kernel: RSP: 0018:ffffc90000d1bd08 EFLAGS: 00010246 Mar 15 12:52:10 Unraid kernel: RAX: 0000000000000000 RBX: ffff88813d000000 RCX: 0000000080800079 Mar 15 12:52:10 Unraid kernel: RDX: 0000000000000001 RSI: 0000000000210d00 RDI: 0015ff006e69622e Mar 15 12:52:10 Unraid kernel: RBP: ffff88810213c640 R08: 0000000000000001 R09: ffffffffa04287ce Mar 15 12:52:10 Unraid kernel: R10: ffffea0004d43f00 R11: ffff88810213c620 R12: 0015ff006e69622e Mar 15 12:52:10 Unraid kernel: R13: ffff88813d016d28 R14: 000000000000000c R15: ffff888166f39210 Mar 15 12:52:10 Unraid kernel: FS: 000014a602632700(0000) GS:ffff888feebc0000(0000) knlGS:0000000000000000 Mar 15 12:52:10 Unraid kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 15 12:52:10 Unraid kernel: CR2: 0000153c1c73c000 CR3: 000000016c886000 CR4: 0000000000750ee0 Mar 15 12:52:10 Unraid kernel: PKRU: 55555554 Mar 15 12:52:10 Unraid kernel: Call Trace: Mar 15 12:52:10 Unraid kernel: free_fw_priv+0x12/0x91 Mar 15 12:52:10 Unraid kernel: release_firmware+0x49/0x4b Mar 15 12:52:10 Unraid kernel: psp_sw_fini+0x6e/0x9c [amdgpu] Mar 15 12:52:10 Unraid kernel: amdgpu_device_fini+0x285/0x43c [amdgpu] Mar 15 12:52:10 Unraid kernel: amdgpu_pci_remove+0x31/0x47 [amdgpu] Mar 15 12:52:10 Unraid kernel: pci_device_remove+0x36/0x8e Mar 15 12:52:10 Unraid kernel: device_release_driver_internal+0xed/0x194 Mar 15 12:52:10 Unraid kernel: unbind_store+0x51/0x6f Mar 15 12:52:10 Unraid kernel: kernfs_fop_write_iter+0x10f/0x152 Mar 15 12:52:10 Unraid kernel: new_sync_write+0x7a/0xb2 Mar 15 12:52:10 Unraid kernel: vfs_write+0xd7/0x121 Mar 15 12:52:10 Unraid kernel: ksys_write+0x71/0xba Mar 15 12:52:10 Unraid kernel: do_syscall_64+0x5d/0x6a Mar 15 12:52:10 Unraid kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Mar 15 12:52:10 Unraid kernel: RIP: 0033:0x14a609f6848f Mar 15 12:52:10 Unraid kernel: Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 49 fd ff ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2d 44 89 c7 48 89 44 24 08 e8 7c fd ff ff 48 Mar 15 12:52:10 Unraid kernel: RSP: 002b:000014a602631590 EFLAGS: 00000293 ORIG_RAX: 0000000000000001 Mar 15 12:52:10 Unraid kernel: RAX: ffffffffffffffda RBX: 000000000000000c RCX: 000014a609f6848f Mar 15 12:52:10 Unraid kernel: RDX: 000000000000000c RSI: 000014a5c005fe20 RDI: 000000000000001b Mar 15 12:52:10 Unraid kernel: RBP: 000014a5c005fe20 R08: 0000000000000000 R09: 0000000000000000 Mar 15 12:52:10 Unraid kernel: R10: 0000000000000000 R11: 0000000000000293 R12: 000000000000001b Mar 15 12:52:10 Unraid kernel: R13: 000000000000001b R14: 0000000000000000 R15: 000014a5c011fd00 Mar 15 12:52:10 Unraid kernel: Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle nf_tables vhost_net tun vhost vhost_iotlb tap veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod amdgpu gpu_sched drm_kms_helper ttm drm backlight agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops nct6775 hwmon_vid wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libblake2s blake2s_x86_64 libblake2s_generic libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables bonding edac_mce_amd kvm_amd kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel igb aesni_intel crypto_simd wmi_bmof i2c_piix4 cryptd ahci i2c_algo_bit mxm_wmi i2c_core libahci glue_helper ch341 usbserial cdc_acm ccp rapl k10temp wmi button acpi_cpufreq nvme nvme_core Mar 15 12:52:10 Unraid kernel: ---[ end trace 6a4dd67cf38c3cbb ]--- Mar 15 12:52:10 Unraid kernel: RIP: 0010:do_raw_spin_lock+0x7/0x12 Mar 15 12:52:10 Unraid kernel: Code: c3 b8 00 fe ff ff f0 0f c1 07 c3 31 c0 48 81 ff 68 d3 6b 81 72 0c 31 c0 48 81 ff 10 d5 6b 81 0f 92 c0 c3 31 c0 ba 01 00 00 00 <f0> 0f b1 17 74 04 89 c6 eb bb c3 8b 07 45 31 c0 85 c0 75 11 ba 01 Mar 15 12:52:10 Unraid kernel: RSP: 0018:ffffc90000d1bd08 EFLAGS: 00010246 Mar 15 12:52:10 Unraid kernel: RAX: 0000000000000000 RBX: ffff88813d000000 RCX: 0000000080800079 Mar 15 12:52:10 Unraid kernel: RDX: 0000000000000001 RSI: 0000000000210d00 RDI: 0015ff006e69622e Mar 15 12:52:10 Unraid kernel: RBP: ffff88810213c640 R08: 0000000000000001 R09: ffffffffa04287ce Mar 15 12:52:10 Unraid kernel: R10: ffffea0004d43f00 R11: ffff88810213c620 R12: 0015ff006e69622e Mar 15 12:52:10 Unraid kernel: R13: ffff88813d016d28 R14: 000000000000000c R15: ffff888166f39210 Mar 15 12:52:10 Unraid kernel: FS: 000014a602632700(0000) GS:ffff888feebc0000(0000) knlGS:0000000000000000 Mar 15 12:52:10 Unraid kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 15 12:52:10 Unraid kernel: CR2: 0000153c1c73c000 CR3: 000000016c886000 CR4: 0000000000750ee0 Mar 15 12:52:10 Unraid kernel: PKRU: 55555554 The driver was basically loaded but after a while you got a module error and it got unloaded. You can try a RC version from Unraid but no guarantee that it works...

What does not work? If you change the value? Male sure that validiation in the template is turned off and also that you stop the container, edit the file and them start it again. What have you changed exactly? Have you also tested if more than 4 people can connect? Maybe it‘s simply displayed wrong because the game is not designed to have more than 4 players connected. No, because then someone else wants me to add an option for another game setting in the template and so on. That is not how a setting in a settings file should be changed, that‘s always up to the user.

@Helzminion it is really strange to me since you are running this on 11th gen and it doesn‘t work and on my 10th gen it works just flawlessly… From your Diagnostics I saw that you are booting with UEFI, can you try to boot with Legacy (CSM)? I don‘t think that this will make any difference at all but I really don‘t get it why it won‘t work for you…

See here: Click You find the file in your satisfactory folder that is located in your appdata directory. But keep in mind that this can have various downsides (high system resource usage, crashes from the dedicated server, high latency,...) since the dedicated server is still in beta and considered experimental.

Do you get the X error every time? X connection to :99 broken (explicit kill or server shutdown). Can you maybe post a log when running the container on a BTRFS drive? As you can see from my log above I have many warnings from WINE in my log too but the server is running fine. Can you please point me to the threads where people have issues with this exact same error?

You can always remove that folder from the console pretty quick, in your case the command would be: rm -rf /mnt/docker_cache/appdata/conanexiles (but be very careful with that command since it deletes folders and if used wrong you could delete more than just one folder...) Please keep me updated if it is working after you've did this, sorry for that many tries, but it's really strange that it won't work on your system...

Can you post a screenshot from the entire template for ConanExiles? I would strongly recommend that you not just point the existing template to the new drive, I would recommend that you really start over, delete everything related to the ConanExiles container and pull a fresh copy from the CA App. TBH, I think I never saw this error, seems like it doesn't start the xvfb server but I actually can't tell why that happnes on your system. Have you changed anything else to the container, maybe mounted another directory or do you change anything in terms of the /tmp path inside the container? Do you use a docker.img or do you use the path? Maybe it's related because the Docker images are on a XFS filesystem, but that's only another guess, as said above, I've tried it this morning and it works flawlessly.

Not related but the first thing that I've noticed in the go file: modprobe i915 chmod -R 777 /dev/dri and you also have the Intel GPU TOP plugin installed. Please remove those two lines from the go file because the Intel GPU TOP plugin handles everything for you. From what I see you are using a XFS formatted drive for the Docker Cache or am I wrong? Please check first if the path in the template points to that Cache driver. A thing that I've discovered recently is that maybe XFS is maybe the issue, do you have a spare disk lying around that you can mount in UnassignedDevcies, format it with BTRFS and try to install the game (at least the game files there)? I remember reading somewhere that some games have issues with XFS, but this was already a while back.

I've never experienced such a thing, do you have a Cache drive installed, if yes to what is the appdata share set in terms of Use Cache set in your Share settings? Can you post the full log output in a text file maybe? I've now tried a fresh install and it works right OOB: CSGO.log and I also can browse it in the Steam Sever browser: Maybe try to start over, delete the container, delete the csgo folder in your appdata directory and pull a fresh copy from the CA App.

I really don't know what's causing this on your setup... I've now tried it on my server and it works flawlessly, here is the log after the first installation: ConanExiles.log and I also can browse it in the Steam Server Browser: Can you maybe share your Diagnostics, but I can't tell for sure if I can help you after you've shared them.

The dedicated server is only available for Windows from what I see and I‘m not to sure if this game will even run on Linux through WINE. I also have stopped to create game servers for games that I‘ve personally don‘t own because giving support for those containers is a nightmare.