Wuast94

I have Setup a VM with pass trough Nvidia GPU, normaly when i shutdown the vm the monitors turn off too. after updating unraid to 6.11 the VM shutt down and the Monitors stays on with the last seen screen. It seems that the GPU dont get shutdown correctly? Hope someone can help. here my xml: If u need more Information feel free to ask

i have similiar issue i have a VM where i passthrough a mouse and keyboard gpu soundcard, worked fine for month. today i added 2 more USB devices, wich work fine. but now my mouse stops working after some time. with the hotplug usb plugin i can detach and attach the mouse again and after a few minutes the mouse stops working again now i followed spaceinvader video to passthroug the whole usb controller, nothing changed. the only thing i can now detach and attach the usb physically instead of do it over the plugin. someone know whats the problem here? EDIT: Same for Keyboard, the other USB devices dont have this issue

Here a few more stats and infos, all the lsof tasks seems a bit of to me after stopping the docker service webui gets responsive again, but have a high CPU usage, every core about 10-30%, i pinned my cores so when i stop docker service unraid have 16/32 Cores/Threats alone My Log was at 100%, mainly nginx with a lot of worker connections are not enough lines another strange thing, i want to stop the array but the buttons are blinking (Mover and Stop Array) so some Array process is spawning again and again? after restart and starting all up again it looks good so far, will see if it break after some time

I had make a backup at the time of diag and becouse of the long loading times i had multiple instance open, it makes no diffrenze if i use one tab or more, my containers are up quite some time and even this makes no diffrence

Dont know if its a pre release thing but had this on stable too from time to time. Its present after restart too, my webui takes a few minutes to load, but it is loading and working. All containers and VM´s run perfekt, it seems like something is blocking the webui from loading, cant find anything and didnt change anything (plugins etc) Someone have an idea whats happening here? server-diagnostics-20220507-0830.zip

Is there a way to disable the docker services from unraid but keep docker enabled? I work with docker-compose and the unraid docker services is messing up my containers. I don't need the fancy webui and such things.

I recently have Trouble with my Unraid OS I cant create a new vm, when i hit save it loads foreever, i looked in the vm log but nothing i double checked all paths and leave all things default but nothing. Hope someone can figure out why ... Server Diag is attached server-diagnostics-20210725-1404.zip

ok i get snmp working now, but the only thing i see more is "UPS LOAD %" "NOMINAL POWER" and "UPS LOAD" are still missing .. and yes modbus is enabled but i only see modbus tcp in settings, i dont think that this is modbus per usb

i enabled modbus but when i set to ModBus (no matter if i use usb or ether) i get nothing

I have installed a APC Smart UPS from APC with a UPS Network Management Card 2. How can i get the data? when i use the USB Cable i dont get any Power readings, but it works for Battery % and static data as Serial number and such things now i want to get it up over network with SNMP, i select "Ether" as usb Cable and "SNMP" as UPS Type. i enter the IP adress dont get any information, i tried something like "192.168.178.5;apc;apc" too but no luck, anyone have more information how i can get this up and running ?

im stuck in a boot loop on 7daystodie. i created the server and seems to work fine, i then imported an existing save, changed the config (server name and so on) and started the server again. Connecting anonymously to Steam Public...Logged in OK Waiting for user info...OK Connecting anonymously to Steam Public...Logged in OK Waiting for user info...OK ---Update Server--- Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation -- type 'quit' to exit -- Loading Steam API...OK. Connecting anonymously to Steam Public...Logged in OK Waiting for user info...OK Success! App '294420' already up to date. ---Prepare Server--- ---SaveGameFolder location correct--- ---Savegame location found--- ---UserDataFolder location correct--- ---UserDataFolder location found--- chmod: changing permissions of '/serverdata/serverfiles/serverconfig.xml': Operation not permitted ---Server ready--- ---Start Server--- Found path: /serverdata/serverfiles/7DaysToDieServer.x86_64 ---Checking if UID: 99 matches user--- usermod: no changes ---Checking if GID: 100 matches user--- usermod: no changes ---Setting umask to 000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Starting...--- ---Update SteamCMD--- Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation -- type 'quit' to exit -- Loading Steam API...OK. Connecting anonymously to Steam Public...Logged in OK Connecting anonymously to Steam Public...Logged in OK Waiting for user info...OK ---Update Server--- Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation -- type 'quit' to exit -- Loading Steam API...OK. Connecting anonymously to Steam Public...Logged in OK Waiting for user info...OK Success! App '294420' already up to date. ---Prepare Server--- ---SaveGameFolder location correct--- ---Savegame location found--- ---UserDataFolder location correct--- ---UserDataFolder location found--- chmod: changing permissions of '/serverdata/serverfiles/serverconfig.xml': Operation not permitted ---Server ready--- ---Start Server--- Found path: /serverdata/serverfiles/7DaysToDieServer.x86_64 I fixed the permissions in a try before that wasnt the error so we can ignore this for now

Ok i finally found the issue... a module https://github.com/NolanKingdon/MMM-DailyPokemon is crashing since MM2 V2.13

@ich777 Here is the log, its repeating and sure you want a screenshot? Its just a black screen... Log.txt

My Magic Mirror goes black a few days ago .. after a while of tweaking i checked that there is no problem with my hardware .. my server just serves a black screen. I didnt changed anything and it was working before .. checkt the logs and no problems there .. but i just get a black screen when browsing to the url

I have some problems with the Onlyoffice container, i run it first stock from template and was getting MySQL errors, i then changed to an external mariadb instance and this error is gone. But now i getting errors related to elasticsearch, i would use an external there too but there are no variables for that. more infos are here https://github.com/ONLYOFFICE/Docker-CommunityServer/issues/100 , i created a github issue becouse i think its more related to the docker image than this thread but i hope that someone has the same proble or have a fix for that

i have two tails open, one on my pc and one that is piping it into a txt file on cache drive to see if there is anything usefull on crash i dont change anything the last month at the system, i also dont installed any plugins or anything else

bios is up to date but i will check the setting but why was my system running for month´s and is now stucking daily since 3 days ? EDIT: Ram speeds are good, no over clock at all. CPU is stock too

My Unraid server is Shutting down randomly, first i think it was the SSD, checked and reformated the whole SSD without errors, Then i run a Memtest, with no errors at all. SMART is okk too. The server runs for serveral houres and then it goes offline. the logs are a bit wired, this is an example, the logs are full with this: Apr 29 13:28:32 Server kernel: vethd123a7d: renamed from eth0 Apr 29 13:28:32 Server kernel: docker0: port 32(vethe08ef94) entered disabled state Apr 29 13:28:32 Server kernel: docker0: port 32(vethe08ef94) entered disabled state Apr 29 13:28:32 Server kernel: device vethe08ef94 left promiscuous mode Apr 29 13:28:32 Server kernel: docker0: port 32(vethe08ef94) entered disabled state Apr 29 13:29:05 Server kernel: docker0: port 32(vethfb022db) entered blocking state Apr 29 13:29:05 Server kernel: docker0: port 32(vethfb022db) entered disabled state Apr 29 13:29:05 Server kernel: device vethfb022db entered promiscuous mode Apr 29 13:29:05 Server kernel: IPv6: ADDRCONF(NETDEV_UP): vethfb022db: link is not ready Apr 29 13:29:06 Server kernel: eth0: renamed from veth5eba356 Apr 29 13:29:06 Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethfb022db: link becomes ready Apr 29 13:29:06 Server kernel: docker0: port 32(vethfb022db) entered blocking state Apr 29 13:29:06 Server kernel: docker0: port 32(vethfb022db) entered forwarding state Apr 29 13:29:32 Server kernel: docker0: port 34(veth3c88d1b) entered blocking state Apr 29 13:29:32 Server kernel: docker0: port 34(veth3c88d1b) entered disabled state Apr 29 13:29:32 Server kernel: device veth3c88d1b entered promiscuous mode Apr 29 13:29:32 Server kernel: IPv6: ADDRCONF(NETDEV_UP): veth3c88d1b: link is not ready Apr 29 13:29:32 Server kernel: docker0: port 34(veth3c88d1b) entered blocking state Apr 29 13:29:32 Server kernel: docker0: port 34(veth3c88d1b) entered forwarding state Apr 29 13:29:32 Server kernel: docker0: port 34(veth3c88d1b) entered disabled state Apr 29 13:29:32 Server kernel: eth0: renamed from veth3e71acd Apr 29 13:29:32 Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth3c88d1b: link becomes ready Apr 29 13:29:32 Server kernel: docker0: port 34(veth3c88d1b) entered blocking state Apr 29 13:29:32 Server kernel: docker0: port 34(veth3c88d1b) entered forwarding state Apr 29 13:29:32 Server kernel: veth3e71acd: renamed from eth0 Apr 29 13:29:32 Server kernel: docker0: port 34(veth3c88d1b) entered disabled state Apr 29 13:29:32 Server kernel: docker0: port 34(veth3c88d1b) entered disabled state Apr 29 13:29:32 Server kernel: device veth3c88d1b left promiscuous mode Apr 29 13:29:32 Server kernel: docker0: port 34(veth3c88d1b) entered disabled state Apr 29 13:29:40 Server kernel: veth5eba356: renamed from eth0 Apr 29 13:29:40 Server kernel: docker0: port 32(vethfb022db) entered disabled state Apr 29 13:29:40 Server kernel: docker0: port 32(vethfb022db) entered disabled state Apr 29 13:29:40 Server kernel: device vethfb022db left promiscuous mode Apr 29 13:29:40 Server kernel: docker0: port 32(vethfb022db) entered disabled state Apr 29 13:30:32 Server kernel: docker0: port 32(vethda94d6d) entered blocking state Apr 29 13:30:32 Server kernel: docker0: port 32(vethda94d6d) entered disabled state Apr 29 13:30:32 Server kernel: device vethda94d6d entered promiscuous mode Apr 29 13:30:32 Server kernel: IPv6: ADDRCONF(NETDEV_UP): vethda94d6d: link is not ready Apr 29 13:30:32 Server kernel: docker0: port 32(vethda94d6d) entered blocking state Apr 29 13:30:32 Server kernel: docker0: port 32(vethda94d6d) entered forwarding state Apr 29 13:30:32 Server kernel: docker0: port 32(vethda94d6d) entered disabled state Apr 29 13:30:33 Server kernel: eth0: renamed from vethbfaccc9 Apr 29 13:30:33 Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethda94d6d: link becomes ready Apr 29 13:30:33 Server kernel: docker0: port 32(vethda94d6d) entered blocking state Apr 29 13:30:33 Server kernel: docker0: port 32(vethda94d6d) entered forwarding state Apr 29 13:30:33 Server kernel: vethbfaccc9: renamed from eth0 Apr 29 13:30:33 Server kernel: docker0: port 32(vethda94d6d) entered disabled state Apr 29 13:30:33 Server kernel: docker0: port 32(vethda94d6d) entered disabled state Apr 29 13:30:33 Server kernel: device vethda94d6d left promiscuous mode Apr 29 13:30:33 Server kernel: docker0: port 32(vethda94d6d) entered disabled state Apr 29 13:31:33 Server kernel: docker0: port 32(veth7c1c504) entered blocking state Apr 29 13:31:33 Server kernel: docker0: port 32(veth7c1c504) entered disabled state Apr 29 13:31:33 Server kernel: device veth7c1c504 entered promiscuous mode Apr 29 13:31:33 Server kernel: IPv6: ADDRCONF(NETDEV_UP): veth7c1c504: link is not ready Apr 29 13:31:33 Server kernel: docker0: port 32(veth7c1c504) entered blocking state Apr 29 13:31:33 Server kernel: docker0: port 32(veth7c1c504) entered forwarding state Apr 29 13:31:33 Server kernel: docker0: port 32(veth7c1c504) entered disabled state Apr 29 13:31:33 Server kernel: eth0: renamed from veth6728934 Apr 29 13:31:33 Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7c1c504: link becomes ready Apr 29 13:31:33 Server kernel: docker0: port 32(veth7c1c504) entered blocking state Apr 29 13:31:33 Server kernel: docker0: port 32(veth7c1c504) entered forwarding state Apr 29 13:31:33 Server kernel: veth6728934: renamed from eth0 Apr 29 13:31:33 Server kernel: docker0: port 32(veth7c1c504) entered disabled state Apr 29 13:31:33 Server kernel: docker0: port 32(veth7c1c504) entered disabled state Apr 29 13:31:33 Server kernel: device veth7c1c504 left promiscuous mode Apr 29 13:31:33 Server kernel: docker0: port 32(veth7c1c504) entered disabled state Diag: server-diagnostics-20200429-1337.zip

never checked that i assume that this way all configs path ports etc settings are as they were before ? and thanks for that tipp

Is there a way that all my docker Containers that are curently shown in docker tab are addet automaticly after recreating the docker image file ? I have more then 30 Containers running and to add them one by another needs time and is not the best i can think of. at least it would be nice to have a multi selection for adding containers back. that way i can select all containers i want to recreate after recreating the docker image file.

ok I changed the disk and now it seems to be fine again

and here is the anonymized server diagnostics after booting and before try to bring the array online. server-diagnostics-20191219-0410.zip EDIT: meanwhile I get error on disk 4 but this wasn't before and now when I start the array (hitting the checkbox that I want to start the array without disk 4) it starts without problems. so was the diening disk the issue ?

My unraid server stops running after an online time about a few days. I didn't do anything with the server at this moment. unraid crashes and boots up, after I enter the encryption key and hitting start the server crashes again. so I did tail the log "tail -f /var/log/syslog" it runs to the point where the docker container boots up: Dec 19 04:00:09 Server kernel: docker0: port 19(vetha153c45) entered blocking state Dec 19 04:00:09 Server kernel: docker0: port 19(vetha153c45) entered disabled state Dec 19 04:00:09 Server kernel: device vetha153c45 entered promiscuous mode Dec 19 04:00:09 Server kernel: IPv6: ADDRCONF(NETDEV_UP): vetha153c45: link is not ready Dec 19 04:00:09 Server kernel: docker0: port 19(vetha153c45) entered blocking state Dec 19 04:00:09 Server kernel: docker0: port 19(vetha153c45) entered forwarding state Dec 19 04:00:09 Server kernel: docker0: port 19(vetha153c45) entered disabled state Dec 19 04:00:10 Server kernel: eth0: renamed from veth3e07bc1 Dec 19 04:00:10 Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth352a4a0: link becomes ready Dec 19 04:00:10 Server kernel: docker0: port 16(veth352a4a0) entered blocking state Dec 19 04:00:10 Server kernel: docker0: port 16(veth352a4a0) entered forwarding state Dec 19 04:00:11 Server kernel: docker0: port 20(vethce2356b) entered blocking state Dec 19 04:00:11 Server kernel: docker0: port 20(vethce2356b) entered disabled state Dec 19 04:00:11 Server kernel: device vethce2356b entered promiscuous mode Dec 19 04:00:11 Server kernel: IPv6: ADDRCONF(NETDEV_UP): vethce2356b: link is not ready Dec 19 04:00:11 Server kernel: docker0: port 20(vethce2356b) entered blocking state Dec 19 04:00:11 Server kernel: docker0: port 20(vethce2356b) entered forwarding state Dec 19 04:00:11 Server kernel: docker0: port 20(vethce2356b) entered disabled state Dec 19 04:00:11 Server kernel: eth0: renamed from veth5b5b5ea Dec 19 04:00:11 Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe941427: link becomes ready Dec 19 04:00:11 Server kernel: docker0: port 17(vethe941427) entered blocking state Dec 19 04:00:11 Server kernel: docker0: port 17(vethe941427) entered forwarding state Dec 19 04:00:13 Server kernel: docker0: port 21(vethf34c5ce) entered blocking state Dec 19 04:00:13 Server kernel: docker0: port 21(vethf34c5ce) entered disabled state Dec 19 04:00:13 Server kernel: device vethf34c5ce entered promiscuous mode Dec 19 04:00:13 Server kernel: IPv6: ADDRCONF(NETDEV_UP): vethf34c5ce: link is not ready Dec 19 04:00:13 Server kernel: docker0: port 21(vethf34c5ce) entered blocking state Dec 19 04:00:13 Server kernel: docker0: port 21(vethf34c5ce) entered forwarding state Dec 19 04:00:13 Server kernel: docker0: port 21(vethf34c5ce) entered disabled state Dec 19 04:00:13 Server kernel: eth0: renamed from veth0662c75 Dec 19 04:00:13 Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth83fcb3f: link becomes ready Dec 19 04:00:13 Server kernel: docker0: port 18(veth83fcb3f) entered blocking state Dec 19 04:00:13 Server kernel: docker0: port 18(veth83fcb3f) entered forwarding state and there it stops. i think its between the docker containers starting.. I have more containers booting up at start as I can count in this log file. is there any docker log I can look at or anything else where I can find this problem ?

Unable to determine the device handle for GPU 0000:04:00.0: Unknown Error when i run nvidia-smi i get the error above. in plugin settings i get my gpu and UUID so all seems good. i running the 6.8.0 RC5 image.

I restarted Unraid today and my GPU is not detected anymore. before it works just fine as my transcoder card for plex. IOMMU is enabled and i didnt change anything. I looked in the log files but didn´t see anything thats wrong