HuiBuh

So I downgraded, and the server is not crashing, but the parity calculations is stuck (had this before with the newest version of Unraid) It also seems like Unraid has some wrong CPU utilization information. The syslog is a bit more interesting though... * and I cannot turn it of (neither using the UI, nor the terminal) syslog-old-unraid

I just checked, and I already have the c-states disabled. I however, just found an old syslog. I think the only "interesting" logs will be on the 22nd of December, as the server crashed on that day. Afterward, I tried to have it on as little as possible, to reduce the crashes (However there should be about one to two somewhere buried in the logs). Just now, it crashed 2 minutes after starting the array, however the syslog has basically nothing in it.... syslog-2

Here you go. Thanks for taking the time! hades-diagnostics-20240208-1456.zip syslog

I had some problems with Unraid after upgrading to the latest version and tried to roll back; however, this would also not work. So I decided to run some stress tests using stress-ng on an Ubuntu live USB for about two days and nothing came up. So to make sure that it is not the fault of some weird Unraid configuration, I decided to start fresh using a new USB and a clean Unraid install. Now after I started to rebuild parity the server did not crash (yet), but Parity seems to be stuck, as I am unable to cancel or pause it. In addition to that, it seems to be stuck, displaying the same parity speed. There are some error messages in the syslog; however, I could not find what they actually mean. I doubt that there are memory problems, as I am running ECC ram. I just tried to collect statistics, but it is stuck and will not do anything now. I cannot ssh into it, the WebUI cannot be accessed, ... So the only thing I have for now is the following error... Feb 8 03:30:12 Hades kernel: CPU: 12 PID: 4570 Comm: unraidd0 Tainted: P D O 6.1.64-Unraid #1 This appeared more often in the syslog