ich777

You got a XID119 error in your logs which you can learn more about here and the exact error is: Aug 19 17:41:50 UNRAIDH kernel: NVRM: _kgspLogXid119: ********************************* GSP Timeout ********************************** Aug 19 17:41:50 UNRAIDH kernel: NVRM: _kgspLogXid119: Note: Please also check logs above. Aug 19 17:41:50 UNRAIDH kernel: NVRM: GPU at PCI:0000:01:00: GPU-ae6c1872-fe75-40ba-a5fe-87ee034c69eb Aug 19 17:41:50 UNRAIDH kernel: NVRM: Xid (PCI:0000:01:00): 119, pid=1361, name=nv_open_q, Timeout after 6s of waiting for RPC response from GPU0 GSP! Expected function 103 (GSP_RM_ALLOC) (0x2080 0x4). Aug 19 17:41:50 UNRAIDH kernel: NVRM: GPU0 GSP RPC buffer contains function 103 (GSP_RM_ALLOC) and data 0x0000000000002080 0x0000000000000004. Aug 19 17:41:50 UNRAIDH kernel: NVRM: GPU0 RPC history (CPU -> GSP): Aug 19 17:41:50 UNRAIDH kernel: NVRM: entry function data0 data1 ts_start ts_end duration actively_polling Aug 19 17:41:50 UNRAIDH kernel: NVRM: 0 103 GSP_RM_ALLOC 0x0000000000002080 0x0000000000000004 0x00063cb8dae781bc 0x0000000000000000 y Aug 19 17:41:50 UNRAIDH kernel: NVRM: -1 103 GSP_RM_ALLOC 0x0000000000000080 0x0000000000000038 0x00063cb8dae780d8 0x00063cb8dae781b0 216us Aug 19 17:41:50 UNRAIDH kernel: NVRM: -2 103 GSP_RM_ALLOC 0x0000000000000000 0x0000000000000078 0x00063cb8dae78015 0x00063cb8dae780d5 192us Aug 19 17:41:50 UNRAIDH kernel: NVRM: -3 76 GSP_RM_CONTROL 0x0000000020800a9f 0x00000000000000b8 0x00063cb8dae77b90 0x00063cb8dae77fa1 1041us Aug 19 17:41:50 UNRAIDH kernel: NVRM: -4 76 GSP_RM_CONTROL 0x000000002080017e 0x0000000000000008 0x00063cb8dae77ad5 0x00063cb8dae77b4e 121us Aug 19 17:41:50 UNRAIDH kernel: NVRM: -5 76 GSP_RM_CONTROL 0x0000000020802a06 0x0000000000000004 0x00063cb8dae77971 0x00063cb8dae77aa7 310us Aug 19 17:41:50 UNRAIDH kernel: NVRM: -6 76 GSP_RM_CONTROL 0x0000000020802a0d 0x000000000000009c 0x00063cb8dae7763a 0x00063cb8dae7796e 820us Aug 19 17:41:50 UNRAIDH kernel: NVRM: -7 76 GSP_RM_CONTROL 0x0000000020802a06 0x0000000000000004 0x00063cb8dae774f8 0x00063cb8dae77635 317us Aug 19 17:41:50 UNRAIDH kernel: NVRM: GPU0 RPC event history (CPU <- GSP): Aug 19 17:41:50 UNRAIDH kernel: NVRM: entry function data0 data1 ts_start ts_end duration during_incomplete_rpc Aug 19 17:41:50 UNRAIDH kernel: NVRM: 0 4128 GSP_POST_NOCAT_RECORD 0x0000000000000002 0x0000000000000027 0x00063cb8dae3d496 0x00063cb8dae3d499 3us Aug 19 17:41:50 UNRAIDH kernel: NVRM: -1 4128 GSP_POST_NOCAT_RECORD 0x0000000000000005 0x00000000058abbd8 0x00063cb8dae3b0d6 0x00063cb8dae3b0d9 3us Aug 19 17:41:50 UNRAIDH kernel: NVRM: -2 4098 GSP_RUN_CPU_SEQUENCER 0x00000000000001ea 0x0000000000003fe2 0x00063cb8dae35c24 0x00063cb8dae35f59 821us Aug 19 17:41:50 UNRAIDH kernel: CPU: 2 UID: 0 PID: 1361 Comm: nv_open_q Tainted: P O 6.12.24-Unraid #1 Aug 19 17:41:50 UNRAIDH kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE Aug 19 17:41:50 UNRAIDH kernel: Hardware name: Supermicro C7Z97-MF/To be filled by O.E.M., BIOS 2.0 06/22/2015 Aug 19 17:41:50 UNRAIDH kernel: Call Trace: Aug 19 17:41:50 UNRAIDH kernel: <TASK> Aug 19 17:41:50 UNRAIDH kernel: dump_stack_lvl+0x47/0x70 Aug 19 17:41:50 UNRAIDH kernel: _kgspRpcRecvPoll+0x593/0x760 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? _issueRpcAndWait+0xd2/0x900 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? rpcRmApiAlloc_GSP+0x1c4/0x4f0 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? subdeviceConstruct_IMPL+0x1f9/0x2c0 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? subdeviceConstruct_IMPL+0x195/0x2c0 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? __nvoc_ctor_Subdevice+0x6c/0xa0 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? __nvoc_init__RmResource+0x38/0x60 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? __nvoc_objCreate_Subdevice+0x182/0x2d0 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? kmem_cache_debug_flags+0xc/0x20 Aug 19 17:41:50 UNRAIDH kernel: ? __nvoc_objCreateDynamic+0x4a/0x70 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? _portMemAllocNonPagedUntracked+0x2c/0x40 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? os_alloc_mem+0x70/0xc0 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? resservResourceFactory+0xc5/0x240 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? _tlsEntryAcquire+0x93/0xd0 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? _clientAllocResourceHelper+0x2aa/0x660 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? osGetCurrentThread+0x26/0x60 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? preempt_latency_start+0x2b/0x50 Aug 19 17:41:50 UNRAIDH kernel: ? serverAllocResourceUnderLock+0x33b/0xa10 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? kmem_cache_debug_flags+0xc/0x20 Aug 19 17:41:50 UNRAIDH kernel: ? rawspin_unlock_irqrestore+0x1f/0x40 Aug 19 17:41:50 UNRAIDH kernel: ? rmapiLockIsWriteOwner+0x21/0x40 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? rmclientValidateLocks_IMPL+0x2b/0x90 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? _serverLockClientWithLockInfo.constprop.0+0x106/0x260 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? serverAllocResource+0x2b4/0x5c0 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? rmapiAllocWithSecInfo+0x1f0/0x420 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? rmapiAllocWithHandle+0x3a/0x40 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? rmapiutilAllocClientAndDeviceHandles+0x155/0x2a0 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? rmapiutilAllocClientAndDeviceHandles+0x12c/0x2a0 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? rawspin_lock_irqsave+0x1f/0x30 Aug 19 17:41:50 UNRAIDH kernel: ? _kgraphicsInternalClientAlloc+0x14e/0x1d0 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? osGetCurrentThread+0x26/0x60 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? kgraphicsLoadStaticInfo_KERNEL+0x88/0xa50 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? os_acquire_spinlock+0xe/0x20 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? os_get_current_tick_hr+0x1f/0x80 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? kgraphicsStatePostLoad_IMPL+0x27/0xd0 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? gpuStateLoad_IMPL+0x396/0xe70 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? rawspin_unlock_irqrestore+0x1f/0x40 Aug 19 17:41:50 UNRAIDH kernel: ? preempt_latency_start+0x2b/0x50 Aug 19 17:41:50 UNRAIDH kernel: ? rawspin_lock_irqsave+0x1f/0x30 Aug 19 17:41:50 UNRAIDH kernel: ? portSyncSpinlockAcquire+0x18/0x30 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? gpumgrStateLoadGpu+0x23/0x110 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? rawspin_unlock_irqrestore+0x1f/0x40 Aug 19 17:41:50 UNRAIDH kernel: ? _tlsThreadEntryGet+0x82/0x90 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? tlsEntryGet+0x31/0x70 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? gpumgrStateLoadGpu+0x5b/0x110 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? RmInitAdapter+0x1337/0x1da0 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? _portMemAllocatorAlloc+0x2b/0xe0 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? preempt_latency_start+0x2b/0x50 Aug 19 17:41:50 UNRAIDH kernel: ? rawspin_lock_irqsave+0x1f/0x30 Aug 19 17:41:50 UNRAIDH kernel: ? rm_init_adapter+0xad/0xc0 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? nv_open_device+0x4e5/0x7d0 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? nvidia_open_deferred+0x33/0xd0 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? mainloop+0xf2/0x120 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? pfxmain_loop+0x10/0x10 [nvidia] Aug 19 17:41:50 UNRAIDH kernel: ? kthread+0xef/0x100 Aug 19 17:41:50 UNRAIDH kernel: ? __pfx_kthread+0x10/0x10 Aug 19 17:41:50 UNRAIDH kernel: ? ret_from_fork+0x24/0x40 Aug 19 17:41:50 UNRAIDH kernel: ? __pfx_kthread+0x10/0x10 Aug 19 17:41:50 UNRAIDH kernel: ? ret_from_fork_asm+0x1a/0x30 Aug 19 17:41:50 UNRAIDH kernel: </TASK> Aug 19 17:41:50 UNRAIDH kernel: NVRM: _kgspLogXid119: ******************************************************************************** Aug 19 17:41:50 UNRAIDH kernel: NVRM: _issueRpcAndWait: rpcRecvPoll timedout for fn 103! Aug 19 17:41:50 UNRAIDH kernel: NVRM: rpcRmApiAlloc_GSP: GspRmAlloc failed: hClient=0xc1e003cc; hParent=0xcaf00000; hObject=0xcaf00001; hClass=0x00002080; paramsSize=0x00000004; paramsStatus=0x00000000; status=0x00000065 Aug 19 17:41:56 UNRAIDH kernel: NVRM: Xid (PCI:0000:01:00): 119, pid=1361, name=nv_open_q, Timeout after 6s of waiting for RPC response from GPU0 GSP! Expected function 76 (GSP_RM_CONTROL) (0x20800a1f 0xb8). Aug 19 17:41:56 UNRAIDH kernel: NVRM: _issueRpcAndWait: rpcRecvPoll timedout for fn 76! Aug 19 17:41:56 UNRAIDH kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Call timed out [NV_ERR_TIMEOUT] (0x00000065) returned from pRmApi->Control(pRmApi, hClient, hSubdevice, NV2080_CTRL_CMD_INTERNAL_STATIC_KGR_GET_CAPS, pParams, sizeof(pParams->caps)) @ kernel_graphics.c:1174 Aug 19 17:41:57 UNRAIDH kernel: NVRM: GspMsgQueueSendCommand: buffer is full (waiting for 1 free elements, got 0) Aug 19 17:41:57 UNRAIDH kernel: NVRM: _kgspRpcSendMessage: GspMsgQueueSendCommand failed on GPU0: 0x3 Aug 19 17:41:57 UNRAIDH kernel: NVRM: _issueRpcAndWait: rpcSendMessage failed with status 0x00000003 for fn 10! Aug 19 17:41:57 UNRAIDH kernel: NVRM: rpcRmApiFree_GSP: GspRmFree failed: hClient=0xc1e003cc; hObject=0xcaf00001; paramsStatus=0x00000000; status=0x0000ffff Aug 19 17:41:58 UNRAIDH kernel: NVRM: Rate limiting GSP RPC error prints for GPU at PCI:0000:01:00 (printing 1 of every 30). The GPU likely needs to be reset. Aug 19 17:41:58 UNRAIDH kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Call timed out [NV_ERR_TIMEOUT] (0x00000065) returned from kgraphicsLoadStaticInfo(pGpu, pKernelGraphics, KMIGMGR_SWIZZID_INVALID) @ kernel_graphics.c:448 Aug 19 17:41:58 UNRAIDH kernel: NVRM: RmInitNvDevice: *** Cannot load state into the device Aug 19 17:41:58 UNRAIDH kernel: NVRM: RmInitAdapter: RmInitNvDevice failed, bailing out of RmInitAdapter Aug 19 17:42:01 UNRAIDH kernel: NVRM: nvAssertFailedNoLog: Assertion failed: (status NV_OK) || (status NV_ERR_GPU_IN_FULLCHIP_RESET) @ fecs_event_list.c:1596 Aug 19 17:42:02 UNRAIDH kernel: NVRM: nvAssertFailedNoLog: Assertion failed: (status NV_OK) || (status NV_ERR_GPU_IN_FULLCHIP_RESET) @ rs_client.c:844 Aug 19 17:42:02 UNRAIDH kernel: NVRM: nvAssertFailedNoLog: Assertion failed: (status NV_OK) || (status NV_ERR_GPU_IN_FULLCHIP_RESET) @ rs_server.c:259 Aug 19 17:42:02 UNRAIDH kernel: NVRM: nvAssertFailedNoLog: Assertion failed: rmStatus == NV_OK @ kern_disp.c:298 Aug 19 17:42:04 UNRAIDH kernel: NVRM: nvAssertFailedNoLog: Assertion failed: listCount(&pKernelBus->virtualBar2[gfid].usedMapList) == 0 @ kern_bus_vbar2.c:346 Aug 19 17:42:09 UNRAIDH kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Failure: Generic Error [NV_ERR_GENERIC] (0x0000FFFF) returned from pRmApi->Control(pRmApi, pGpu->hInternalClient, pGpu->hInternalSubdevice, NV2080_CTRL_CMD_INTERNAL_INIT_USER_SHARED_DATA, &params, sizeof(params)) @ gpu_user_shared_data.c:213 Aug 19 17:42:10 UNRAIDH kernel: NVRM: nvAssertFailedNoLog: Assertion failed: rmStatus == NV_OK @ osinit.c:2265 Aug 19 17:42:10 UNRAIDH kernel: NVRM: nvAssertFailedNoLog: Assertion failed: listCount(&pKernelBus->virtualBar2[gfid].usedMapList) == 0 @ kern_bus_vbar2.c:346 Aug 19 17:42:10 UNRAIDH kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x25:0x65:1203) Aug 19 17:42:10 UNRAIDH kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 It seems that your GSP times out which most of the times means some hardware incompatibility issue and may actually be a driver incompatibility issues. I can't do much about that, you can try to report that on the Nvidia Developer forums over here. However I'm not 100% sure if the folkos over there can help.

What path did you set? The path to the serverfiles inside the container is always: /serverdata/serverfiles/

Please check your paths inside the template. If you've set /mnt/cache/appdat/... then you have to ensure that your appdata share stays on the cache and is not moved to another pool <- that's probably the reason. Check your Share settings for your appdata share and make sure the mover takes no action.

Can you please: Update your BIOS to the latest version Enable Above 4G Decoding in the BIOS Enable Resizable BAR Support Make sure to boot with UEFI and not in Legacy Mode

Exactly, uinput is integrated a long time now into Unraid itself, so to speak, no need for a install anymore.

No, this is not possible. If you remove them from the Docker template the default values from the Dockerfile are read. May I ask with what values do you have an issue, the container exists a very long time now and nobody until yet reported an issue. Is it that bad when you have to use the Docker template for these few values instead the server.cfg?

I'm not 100% sure how you did that but nouveau is enabled. 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GB206 [GeForce RTX 5060 Ti] [10de:2d04] (rev a1) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:5351] Kernel driver in use: nvidia Kernel modules: nouveau, nvidia_drm, nvidia 01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:22eb] (rev a1) Subsystem: NVIDIA Corporation Device [10de:0000] And your GPU fell from the BUS: Aug 15 09:24:51 nas kernel: NVRM: Xid (PCI:0000:01:00): 79, GPU has fallen off the bus. You also have a lot of entries in your syslog from Nvidia, was the card working before or did you just put it in your system. When the card falls from the bus this can have multiple reasons, please don't use a PCIe riser if you have one installed, try another slot, try to lower the PCIe Gen to 4 or even down to 3 speed, make sure your BIOS is up to date.

Post your Diagnostics, as pointed out in the first post since they are required to troubleshoot hardware issues

Usually not, Fix Common Problems won‘t change permissions on files/folders, correct @Squid Sorry for that but usually it should just work if you don‘t change permissions. I really can‘t tell what happened there, sorry.

Nope, that doesn‘t mean that the permissions are correct. I assume something changed the permissions in the folder or even something got deleted somehow and that‘s why the container is not working anymore. LXC works a bit different than Docker for example, each container has it’s own rootfs and when you change permission the containers won‘t start anymore meaning that they are bricked. There should be a big red warning on the settings page to never run the Unraid function „Fix Permission“ on the LXC share sonce this basically would break all containers.

Is this the full output from lxc-start -F <CONTAINERNAME> (please don't forget to include the -F) Did you by any chance change your docker network from macvlan to ipvlan or did you change any bridge network on Unraid itself to use eth0 instead of br0? The above is also not default. Did you possible issue new permissions on the LXC container directory? Usually the containers will still work but the error message that you've posted is not much.

Sorry, you have a lot custom things in your AMP configuration file, remove all of that and see if it then works. May I ask why are you passing through the Nvidia driver through to the container, also your method seems rather complicated and I assume this is the issue why it's not working, your installed Nvidia driver version: 570.86.16 you pass through files from driver: 565.77 You always can check from the command line what went wrong with: lxc-start -F CONTAINERNAME

GVT-g is only supported up to Intel 10th gen CPUs but you question has nothing to do with GVT-g. It would be also be better to ask that in the appropriate support thread from @binhex since this seems like it's related to Emby and not GVT-g. This also doesn't require a dedicated plugin, you just need to pass through the device /dev/dri but that is something you should ask in the support thread (you can get there by clicking the container icon on the Docker page within Unraid and click Support).

Only Intel Core Series and Xeon Series CPUs are supported for GVT-g, Pentium and Atom Series CPUs are not supported (like mentioned in the first post).

I would recommend that you upgrade to 7.1.4 to begin with, never mind I just read that you are already on 7.1.4. I think that won't change much but it shouldn't hurt to enable GuC and HuC Since we are dealing with Docker that won't do much I think since these are primarily for VMs. This is not a troubleshooting step since you give the container full access to the host and this is basically bad, Privileged should not be turned on whatsoever except you want to make everything insecure. :) If your've already have a Device mapping in the template that won't do much, which I assume you had because otherwise that wouldn't work, what basically means this is redundant and not necessary. I'm not too familiar with Firgate but you shouldn't have to do that and I'm also not sure if Firgate mounts anything in /dev/shm. Can't say anything to that because I'm not running Frigate. I don't think so because OpenVINO should work no matter what, except if you completely overload it or we are dealing with a hardware failure, or it could even be the case that the your iGPU doesn't fully support the OpenVINO implementation from Frigate <- but I don't think that's the issue. However it always depends on the implementation from Frigate how OpenVINO is used and you might need to pass through /dev/usb to your container, so to speaking a Device with the mapping: /dev/bus/usb:/dev/bus/usb

Yes.

I assume you've set the docker container up using the command line with docker run, that's why you are seeing 3rd part.

Please update the container itself, the issue with BepInEx is now fixed, if you did any workarounds delete the version file for BepInEx which is located in the main directory from the container (usually named BepInEx-<VERSION>) in the first place and then update the container.

Are you talking about ValheimPlus or BepInEx? I try to look into this but I'm nut sure when I have time for a fix.

Yes: https://github.com/ich777/docker-minecraft-basic-server/blob/master/scripts/start-server.sh#L86 https://github.com/ich777/docker-minecraft-basic-server/blob/master/scripts/start-server.sh#L73 https://github.com/ich777/docker-minecraft-basic-server/blob/master/scripts/start-server.sh#L60 https://github.com/ich777/docker-minecraft-basic-server/blob/master/scripts/start-server.sh#L47 https://github.com/ich777/docker-minecraft-basic-server/blob/master/scripts/start-server.sh#L34 https://github.com/ich777/docker-minecraft-basic-server/blob/master/scripts/start-server.sh#L25

Okay wegn that all also doesn‘t work then something else is wrong. Are you sure that the container has access to GitHub and you are not blocking any traffic? Male sure to disable all AdBlockers if you have any on your network. Do you also have Unifi gear on your network? Sometimes IDS/IPS is a bit to strict on those devices and restrict access for containers to some sites.

Please try to remove the runtime folder from your minecraft directory alongside with any jar zip/tar file in the main directory from minecraft. Of course stop the container before doing any of that and then start the container.

Sure, just set RUNTIME_NAME to jre21 which you can find in Show more ... in the template.

I don‘t understand what you mean with that? The open source driver is compiled once when a new Unraid version is released. Again, this is most of the times a hardware incompatibility issue. Did you yet try to upgrade to Unraid 7.2.0 beta siereis and look if the open source driver is working there?

If your hardware ID is listed here then yes: GitHubGitHub - NVIDIA/open-gpu-kernel-modules: NVIDIA Linux ope...NVIDIA Linux open GPU kernel module source. Contribute to NVIDIA/open-gpu-kernel-modules development by creating an account on GitHub.