ich777

You have a macvlan trace in your syslog: Dec 12 22:17:53 MojoRyzen kernel: ------------[ cut here ]------------ Dec 12 22:17:53 MojoRyzen kernel: NETDEV WATCHDOG: eth0 (r8152): transmit queue 0 timed out Dec 12 22:17:53 MojoRyzen kernel: WARNING: CPU: 20 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x14e/0x1c0 Dec 12 22:17:53 MojoRyzen kernel: Modules linked in: xt_connmark xt_comment iptable_raw wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha xt_mark tcp_diag udp_diag inet_diag veth macvlan xt_nat nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 vhost_net tun vhost vhost_iotlb tap nvidia_uvm(PO) xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls r8152(O) igb i2c_algo_bit nvidia_drm(PO) nvidia_modeset(PO) edac_mce_amd edac_core intel_rapl_msr intel_rapl_common iosf_mbi kvm_amd nvidia(PO) kvm crct10dif_pclmul crc32_pclmul crc32c_intel video Dec 12 22:17:53 MojoRyzen kernel: ghash_clmulni_intel sha512_ssse3 sha256_ssse3 btusb sha1_ssse3 drm_kms_helper btrtl aesni_intel btbcm btintel input_leds crypto_simd wmi_bmof mxm_wmi cryptd drm bluetooth mpt3sas rapl nvme backlight syscopyarea k10temp raid_class hid_apple sysfillrect ahci sysimgblt ccp i2c_piix4 ecdh_generic scsi_transport_sas fb_sys_fops nvme_core ecc led_class libahci i2c_core tpm_crb tpm_tis tpm_tis_core tpm wmi button acpi_cpufreq unix [last unloaded: r8152(O)] Dec 12 22:17:53 MojoRyzen kernel: CPU: 20 PID: 0 Comm: swapper/20 Tainted: P O 6.1.64-Unraid #1 Dec 12 22:17:53 MojoRyzen kernel: Hardware name: To Be Filled By O.E.M. X570 Taichi/X570 Taichi, BIOS P5.00 10/19/2022 Dec 12 22:17:53 MojoRyzen kernel: RIP: 0010:dev_watchdog+0x14e/0x1c0 Dec 12 22:17:53 MojoRyzen kernel: Code: a4 c5 00 00 75 26 48 89 ef c6 05 a8 a4 c5 00 01 e8 59 23 fc ff 44 89 f1 48 89 ee 48 c7 c7 58 80 15 82 48 89 c2 e8 ab 73 93 ff <0f> 0b 48 89 ef e8 32 fb ff ff 48 8b 83 88 fc ff ff 48 89 ef 44 89 Dec 12 22:17:53 MojoRyzen kernel: RSP: 0018:ffffc90000670ea8 EFLAGS: 00010282 Dec 12 22:17:53 MojoRyzen kernel: RAX: 0000000000000000 RBX: ffff888106075448 RCX: 0000000000000003 Dec 12 22:17:53 MojoRyzen kernel: RDX: 0000000000000104 RSI: 0000000000000003 RDI: 00000000ffffffff Dec 12 22:17:53 MojoRyzen kernel: RBP: ffff888106075000 R08: 0000000000000000 R09: ffffffff829513f0 Dec 12 22:17:53 MojoRyzen kernel: R10: 00003fffffffffff R11: 2074696d736e6172 R12: 0000000000000000 Dec 12 22:17:53 MojoRyzen kernel: R13: ffff88810607539c R14: 0000000000000000 R15: 0000000000000001 Dec 12 22:17:53 MojoRyzen kernel: FS: 0000000000000000(0000) GS:ffff888ffed00000(0000) knlGS:0000000000000000 Dec 12 22:17:53 MojoRyzen kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 12 22:17:53 MojoRyzen kernel: CR2: 0000000000452b98 CR3: 0000000103894000 CR4: 0000000000350ee0 Dec 12 22:17:53 MojoRyzen kernel: Call Trace: Dec 12 22:17:53 MojoRyzen kernel: <IRQ> Dec 12 22:17:53 MojoRyzen kernel: ? __warn+0xab/0x122 Dec 12 22:17:53 MojoRyzen kernel: ? report_bug+0x109/0x17e Dec 12 22:17:53 MojoRyzen kernel: ? dev_watchdog+0x14e/0x1c0 Dec 12 22:17:53 MojoRyzen kernel: ? handle_bug+0x41/0x6f Dec 12 22:17:53 MojoRyzen kernel: ? exc_invalid_op+0x13/0x60 Dec 12 22:17:53 MojoRyzen kernel: ? asm_exc_invalid_op+0x16/0x20 Dec 12 22:17:53 MojoRyzen kernel: ? dev_watchdog+0x14e/0x1c0 ### [PREVIOUS LINE REPEATED 1 TIMES] ### Dec 12 22:17:53 MojoRyzen kernel: ? psched_ppscfg_precompute+0x57/0x57 ### [PREVIOUS LINE REPEATED 1 TIMES] ### Dec 12 22:17:53 MojoRyzen kernel: call_timer_fn+0x6f/0x10d Dec 12 22:17:53 MojoRyzen kernel: __run_timers+0x144/0x184 Dec 12 22:17:53 MojoRyzen kernel: ? tick_init_jiffy_update+0x7c/0x7c Dec 12 22:17:53 MojoRyzen kernel: ? update_process_times+0x7a/0x81 Dec 12 22:17:53 MojoRyzen kernel: ? tick_sched_timer+0x43/0x71 Dec 12 22:17:53 MojoRyzen kernel: ? __hrtimer_next_event_base+0x27/0x81 Dec 12 22:17:53 MojoRyzen kernel: run_timer_softirq+0x2b/0x43 Dec 12 22:17:53 MojoRyzen kernel: __do_softirq+0x129/0x288 Dec 12 22:17:53 MojoRyzen kernel: __irq_exit_rcu+0x5e/0xb8 Dec 12 22:17:53 MojoRyzen kernel: sysvec_apic_timer_interrupt+0x85/0xa6 Dec 12 22:17:53 MojoRyzen kernel: </IRQ> Dec 12 22:17:53 MojoRyzen kernel: <TASK> Dec 12 22:17:53 MojoRyzen kernel: asm_sysvec_apic_timer_interrupt+0x16/0x20 Dec 12 22:17:53 MojoRyzen kernel: RIP: 0010:cpuidle_enter_state+0x11d/0x202 Dec 12 22:17:53 MojoRyzen kernel: Code: 2b ff 9f ff 45 84 ff 74 1b 9c 58 0f 1f 40 00 0f ba e0 09 73 08 0f 0b fa 0f 1f 44 00 00 31 ff e8 a3 c0 a4 ff fb 0f 1f 44 00 00 <45> 85 e4 0f 88 ba 00 00 00 48 8b 04 24 49 63 cc 48 6b d1 68 49 29 Dec 12 22:17:53 MojoRyzen kernel: RSP: 0018:ffffc900001f7e98 EFLAGS: 00000246 Dec 12 22:17:53 MojoRyzen kernel: RAX: ffff888ffed00000 RBX: ffff888109157000 RCX: 0000000000000000 Dec 12 22:17:53 MojoRyzen kernel: RDX: 000009412b09c6cd RSI: ffffffff820d7e01 RDI: ffffffff820d830a Dec 12 22:17:53 MojoRyzen kernel: RBP: 0000000000000001 R08: 0000000000000002 R09: 0000000000000002 Dec 12 22:17:53 MojoRyzen kernel: R10: 0000000000000020 R11: 000000000000afc8 R12: 0000000000000001 Dec 12 22:17:53 MojoRyzen kernel: R13: ffffffff823237a0 R14: 000009412b09c6cd R15: 0000000000000000 Dec 12 22:17:53 MojoRyzen kernel: ? cpuidle_enter_state+0xf7/0x202 Dec 12 22:17:53 MojoRyzen kernel: cpuidle_enter+0x2a/0x38 Dec 12 22:17:53 MojoRyzen kernel: do_idle+0x18d/0x1fb Dec 12 22:17:53 MojoRyzen kernel: cpu_startup_entry+0x2a/0x2c Dec 12 22:17:53 MojoRyzen kernel: start_secondary+0x101/0x101 Dec 12 22:17:53 MojoRyzen kernel: secondary_startup_64_no_verify+0xce/0xdb Dec 12 22:17:53 MojoRyzen kernel: </TASK> Dec 12 22:17:53 MojoRyzen kernel: ---[ end trace 0000000000000000 ]--- If you are using macvlan in your Docker settings please disable the Bridge in your Network settings, if you need the Bridge then please change to ipvlan in your Docker settings.

Have you forwarded all the ports form the template with the according protocol in your router too?

May I ask why not run it in LXC on Unraid?

Yes, please make sure that your plugin is also up to date!

Only English over here. Why? Only enter your Steam credentials when the Steam Username and Password are not hidden away at "Show more..." and are marked with a red asterisk (*) !!! NEVER DISABLE THE STEAM GUARD ON YOUR PERSONAL ACCOUNT !!! The only thing in this screenshot that is wrong is that you've entered your Steam credentials. Also please read the description from the container, the first start can take a very long time depending on your Internet connection since the container needs to download the game files! To solve this issue, do the following: Remove the container Remove the directory that was created for Wreckfest in your appdata directory Pull a fresh copy from Wreckfest from the CA App and leave all settings untouched (except if you need to change the paths) Wait for the download to finish, this means that the log window will not change in a while but it will eventually display the progress and start the dedicated server

Vermutlich hat es schon vorher auch funktioniert, vermutlich war eine kleinigkeit falsch eingestellt. Ja, es funktioniert. Vermutlich war es nicht das skript aber sonst schmeiß einfach das in dein go file ganz am Schluss rein (/boot/config/go) : nvidia-persistenced Kannst auch mit einem User Script machen, nach dem initialen boot, einmal genügt wenn Unraid hochgefahren wird.

I'm not super convinced that this is necessary since the NIC temperature is usually consistent on Mellanox cards and I have no plans currently to implement that.

I think the bar that you see that says N/A is the Power Draw, is that also disabled?

Mach eine Container Konsole (nicht die Unraid Konsole selbst) auf und dann gib das ein: nvidia-smi Was kommt dann -> Screenshot? Was ist das im syslog: Dec 11 14:15:17 RMSAGNAS01 kernel: NVRM: Persistence mode is deprecated and will be removed in a future release. Please use nvidia-persistenced instead. (Bitte mach das User script weg, das ist outdated! Du solltest nvidia-persistenced verwenden). Hast du mal screenshots von deinem Container template mit der Advanced View an geschaltet? Hast du denn auch einen Claim erstellt und dann im Template eingefügt? Schalte bitte im BIOS deine C-States aus da du einen Ryzen CPU der 2ten generation verwendest, stell auch sich das du Resizable BAR Support und Above 4G Decoding oder Large Address Support bei den PCI Geräten im BIOS aktivierst.

I think you are using a really old template from my container correct? You don't need to copy over anything and by default my container is using this version from Valheim+ I'm running it on my server and it is working as it should: Are you also sure that the container itself is up to date? By default it uses this repository.

Then this is most certainly the cause of the issue. Glad to hear that it's solved.

Issue this command from a Unraid terminal and restart the container afterwards and see if that helps: echo 265000 > /proc/sys/vm/max_map_count (this command is not persistent and you have to reissue it every time you reboot) It would be also nice to know if you are using mods or not, you are the first user that reported a OOM error for Conan Exiles.

It looks like both of you are using the old plugin, since the plugin date from my fork is: 2023.11.22 and not 2023.04.06 Please look at the first recommended post in this thread on top, uninstall the old plugin and install my fork since @zhtengw seems like to be not active anymore and that's why I forked the plugin (I explained this in the recommended post).

Not yet, I will post a update when I know more. As a workaround add this variable to the container, this fixes the start issue on my machine: Config Type: Variable Key: FORCE_X86 Value: true

What does the log say? Stop the container, open the Logs from the container and post a screenshot or a textfile with the contents from the log. The container is running and not restarting correct?

...der ist schon lange nicht mehr aktuell... Bitte auf den offiziellen Container umsteigen, der Unterstützt das jetzt auch. https://hub.docker.com/r/jellyfin/jellyfin

Yes, why not? This update should be a solution so that the plugin is workig again for all users. I just waited for your confirmation since your posts where a bit confusing.

I've pushed an update to the plugin so that it blacklist all cdc drivers.

I think you mean cdc_mbim? Can you remove that? From what version? From the Diagnostics I see 6.12.4? Where does it say that? Did you type in a command? Please execute this command once and reboot and make sure the plugin is installed and see if that fixes the error: echo "blacklist r8153_ecm" > /boot/config/modprobe.d/r8153_ecm.conf (leave the other three files in place)

I've gone through the source and your specific Vendor/Device ID is supported by the RTL8152 plugin but it failed to install as you can see here: Dec 9 15:24:59 Tower root: -----------------------Downloading RTL8152 package!------------------------- Dec 9 15:24:59 Tower root: --------This could take some time, please don't close this window!---------- Dec 9 15:24:59 Tower root: Dec 9 15:24:59 Tower root: -----------------------Can't download RTL8152 package----------------------- Dec 9 15:24:59 Tower root: plugin: run failed: '/bin/bash' returned 1 Are you sure that the plugin is correctly installed? Please check if the plugin is in the "Plugin Error" tab on the Plugin page, uninstall it and try to reinstall it while your Intel NIC is connected and make sure that the plugin actually says that it is installed and the Done button appeared in the plugin installation popup. Make sure you have the cdc_ether.conf still in place and after that reboot your server and please pull new Diagnostics and post them here if the NIC doesn't work after that.

Yes, that what I was saying above, you can‘t blacklist the built in driver when you uninstall the plugin becuase that means that you would have no available driver to use. About what blacklist are you talking exactly? When the driver is not installed there should be no blacklist file in place. Just for clarification, have you copy pasted my command from above in a Terminal from Unraid and after that rebooted with the driver plugin from @jinlife already installed? After installing the plugin you manually have to copy/paste the command from above and reboot.

Sorry haven‘t got time yet to reply. I see it, anyways, glad that it‘s solved!

Please try reinstalling it and specify a new token. Are you able to issue nvidia-smi in the container?

It seems that in your case another driver is used, can you please try to do the following with the plugin installed: echo "blacklist cdc_ether" > /boot/config/modprobe.d/cdc_ether.conf It seems like that your NIC is using another driver. However as @JorgeB said it might be possible that you even don't need the R8152 anymore. Can you please also test what removing the R8152 does after a reboot and if everything is working as expected (of course you have to remove the file /boot/config/modprobe.d/cdc_ether.conf first <- otherwise you won't have network!)?

Sure, simply create a port mapping to somewhere on the Array (or a share that is located to move the files from the Cache to the Array): (make sure that you stop the container, move the old folder "Backup" that already exists in your Valheim directory to somewhere else and it will work as intended) SteamCMD is a shared directory which my game server containers use that only exists one time on your server to download the game files, ServerFiles are the location where the necessary dedicated server files are download to.