rug

I had that enabled and I do have the syslog file of the day of the recent freeze but I don't know what to look for and if it's safe to share on the forum. By the way a change I applied to the system recently was to set the Power Mode to power saving, previously on Best performance). Maybe that re enabled low c-states?

After a year it happened again, server unresponsive: can't SSH into it Web GUI not loading (times out) Disks i/o led blinking and fans spinning like if it was doing something Had to force shutdown the server but this time I do have the syslog file, what should I look for to troubleshoot the issue? Can I post it on the forum or does it contain sensitive information? I also did change c-state settings last year as recommended in the above mentioned thread, but is there anything I can check to be sure whether the issue is still related to c-states or something else? I wouldn't mind re-enabling the c-states for power saving, at the time I changed the setting "blindly" without a confirmation that this was actually my issue. AMD Ryzen 5700G. The server is headless so I am also thinking to buy a kvm to remotely access the screen and try to reboot it from the shell as if I was with screen and keyboard attached to the server (assuming at least that works).

The first post instructs on how to install powertop but I noticed it references Unraid version 6.11.0, can I still install powertop on v7.2.3 the same way?

Is the script still relevant / still works / applies for Unraid 7.x? I stumbled upon here while browsing the meaning of the various disk settings.

Hi, just installed the plugin to troubleshoot some disks that are always spinning, the plugin Drive Standby Monitor reports some disks around 0.55% (basically on h24) 😢 The plugin seems to work fine and indeed I can see a lot of files being accessed on those disks confirming the data from the other plugin, however the process being reported is always PID 1881561 process path /usr/libexec/unraid/shfs While some paths are immediately recognizable to me because they are exclusive for certain containers, other files remains a mystery. Is there any margin of improvement on the subject or is an Unraid limitation to expose the real process/container accessing a file? I have my suspects on some other containers. For now, the only strategy I can think of is to try to stop them all and turning them on one by one while observing in real time the File Activity plugin.

I am not ready to migrate to ZFS and likely never will so the subject is very important to me and I just stumbled upon this plugin. So far I have been using File Integrity plugin, but I am no expert on the mechanics involved. Genuine question, would you recommend your solution and if so why? Is it faster or more resilient or other?

Best plugin I have ever used to manage fan speeds. Easy to use and well thought 🙂

Thanks, I will try to address this first.

In the last week my server has become unresponsive two times at the point that SSH connection through Putty wasn't responding, WebUI wasn't loading (Connection timeout), Glances webui was in timeout too, no other Docker service was responding. The only thing that gave me a heartbeat was a ping to which the server did respond. The server did not have any recent modification, last thing was the setup of Immich a month ago. Given the situation the only action I could perform was a forced shutdown 😖, upon rebooting the server resumed functionalities as normal. I have Glances installed which I used in the pas to explore hungry processes, however, it's a live tool and doesn't retain historical data. To troubleshoot the issue, I am trying to deactivate everything and activate things one by one, but I surely feel like I need something to retain historical data in case a new disaster occurs. What (how) can I setup to ensure Unraid logs, system metrics, disks metrics, processes, docker containers system usage etc are logged and retained across reboots\forced shutdowns? For what's worth I have another machine where I could send data (or pull it from Unraid). --- After disabling all the containers dockerd is still consuming a huge amount of CPU. I'm investigating if there is something corrupted with docker maybe, but I'm really going blindly into the unknown. Executing from SSH `/etc/rc.d/rc.docker stop` frees up 100% of the CPU. But basically I am unable to restart it because if I execute `/etc/rc.d/rc.docker start` the dockerd process spikes again to 300% CPU usage with 0 containers running (I disabled the autostart on all of them). Edit: - Attached diagnostics zip tower-diagnostics-20250121-1103.zip

Tried but with no success. Oddly enough if I open the web gui with another browser it works fine so I guess something is specifically wrong with Firefox 129.0b8

I didn't see any anomaly in the processes running on the server. Today I logged in the WEB UI for some maintenance and noticed some odd things: The dashboard correctly shows docker containers, I even stopped one and the UI updated the icon All the other infos are missing: CPU, FAN etc are blanks The main tab shows no disks The log doesn't load The diagnostic tab keeps loading indefinitely, so I can't download a diagnostic zip The Glances docker container (which is running OK) does show correctly the server infos Every docker container is performing normally and services are up and running I've attached some screenshots. I'm considering rebooting, but I'm leaving for a week, and I'd rather have my services running instead of risking a reboot that could lead to more troubles. I can SSH into the server to perform manual operations if needed, but right now I don't know what should I do.

Following, having the same issue and this is the only thread on the topic.

The VBIOS listed in the first post link indeed reports UEFI NO but the GPU works fine without VBIOS specified after the SeaBios change. I mean it works as far as getting an output on the HDMI output to see the VM on my TV.

Recreating the VM wigh SeaBios allowed me to boot with the GPU passed through, thanks.

I haven't but now that I tried, SeaBios does show up in the webui menu but I can't select it.