terox

Fixed. Not a bug, but the "CPU pinning" panel could induce into confusions for "non-sys guys". By parts: The solution: My CPU has 12 cores (6/6). I had isolate the CPU with id 0 and 6. My VM has pinned the rest of cores (1,2,3,5,7...). This configuration is completely wrong. The isolated CPUs "are out" of the task scheduler. By this misunderstood configuration I was achiving a crash may be because teorically non-isolated CPUs was using for VM (and containers). After a change of pinned CPUs from 0,6 to 1-5,7-11 and pin the same isolated cores to VM, the issue was fixed. I reserved the CPU 0,6 for dockers and Unraid processes. Why I think that CPU Pinning induce to confusions: There is nothing that visual in the panel that alert you that you have (or could you have) a potential issue of performance or configuration. To know some of this problems, you need to install a "Fix common Problems" to have some clue. I think that It should be integrated into the panel. Thank you for help and clues.

I created a new entry in boot without isolcpus... and it worked as expected. I will try in next days to understand why: It's a configuration question of pinned cpus? What are the implications of isolcpus? Why its related with the sleep mode? Maybe it's a bug? If someone have some clue, could be very helpful. Thank you for all of you help

Could be interesting what changes are enabled in "unraidsafemode". I checked kernel loaded modules and are the same in safe and normal mode. Is something loaded in normal mode that is not present in safe. Could be the isolcpus? Is the only parameter not present in the normal boot. But I don't understand what is the effect.

I uninstalled all plugins, and same thing. Something more are changing… there are some official documentation?

Thank for the annotation. I keep investigating because in safe mode, with the array mounted and all dockers working as normal and other services like SMB, it works like a charm. What things change in safe mode? What things (separately of plugins) change?

Bad new from my side. I enabled the i915 driver for my Intel integrated GPU and then rebooted the server. After force the S3 sleep with the plugins, nothing new happen: crashed. I also tried installing the NVIDIA drivers, and the same. I keep investigating. I need read the logs after crash, but I don’t know how because they are cleaned or lost.

That sounds promising. I will be able to try in two days. You have the same experiences that other people with the “g” param. One question, are you using a router with WoW, sending magic packets to the public IP on the WireGuard port? I read that router must be compatible. I will feedback you with the results in a few days Thank you

Very promising! I am now out of home for work for two days, but I will try and I will post the results. In my case, I had set the "g" setting manually each time because the plugin S3 of Dynamic didn't work. Nothing important if I can patch it from user scripts of from a PR in GitHub repository :). @media-fortdo you have some VM with a PCI video card connected by passtrough? In that case where are your video output, in video card on in the integrated igpu output? @Squidshould install video drivers for igpu, although I am use (or passtrought to VM the PCI card, NVIDIA in my case)? Thanks!

Maybe, but I think that is important. I usually run my server 24/7 but some months ago I don't need processes running all the time. Also the electricity bills in Spain are touching the sky. We are in a serious trouble. I am searching solutions. I am sure, that there are some solution or explanation.

When the computer is "sleeping" after some time of inactivity, and the signal of the WOL appears I can't access to computer. It doesn't respond. Sorry by the soft explanation. I mean that I can see the "syslog" on screen monitor whem server boots, but not when it is wake up from LAN. I can't write anything before and after. I haven't a terminal, only logs (maybe I am wrong here). The key: after WOL action, I can't see anything in screen monitor. I have two VM and a NVIDIA graphic card atteched to both. I normally use only one VM at same time, because it is impossible use both. When I force the sleep state, both VM are powered off. Only dockers are running. The iGPU is not used in any VM, but I don't know what you mean from passing passthrough or isoloted. Maybe the issue could come from there? What do you want to try? I tried some hours ago with VM service disabled. But same results. Maybe is the iGPU, but... why when it is restored from a S* state? Thanks

Another detail: when the server wake up, the previous string with white and black text logs don't appear. Also the hard drive LED is off. It is completly crashed.

Hello @Squid Here are the diagnostics with unraid 6.10-rc2 (The behaviour is the same that in 6.9.2) Thank you terox.node-diagnostics-20220128-2318.zip

Hello! I have an stable 6.9.2 unraid server with a minimal configuration. I installed the S3 plugin from Dynamix to sleep the system during the inactivity. The server go to sleep sucessfully and responds also sucessfully to WOL signal. The problem comes when the system wake up. It is unreachable because is crashed. I don't know why. I don't know where collect log to for diagnosticate the issues. Whe it occurs I can't access via website and SSH. By other hand, if I run in a safe mode (without plugins) it runs and wakeup succesfully. I don't understand why because the only plugin that i have installed is the S3. I tried also in a normal mode without docker, VM... and other configurations. I don't understand why in safe mode it works and I can reach the server via SSH and with the browser. It is really annoying. I don't know how I can read the syslog after the "wake up" to read the error and why all is falling. I need help to send more information in that way. Any solution, link to post are welcome (I searched a lot, but no real solutions)... but I read that there are a lot of people with simular issues (not responding, crash...) I hope that together find a solution Thank you so much