October 31, 20205 yr Hi! Recently my unraid machine have started become unresponsive after approximately 3 days after reboot. As you can see in the attached image the kworker events_power_efficient consumes all the cpu and there are several other kworker kblocked processes filling up the rest of the top consuming processes. The web GUI is unresponsive so I don't know how to save the System Diagnostics. Worth noting is that the machine has been running non-stop perfectly for four months before this started happening earlier this week.
October 31, 20205 yr Community Expert Try getting the diags on the console by typing "diagnostics", also make sure to see if it still happens if you boot in safe mode.
October 31, 20205 yr Author I had to reboot the machine because now even the console where unresponsive. After reboot I manage to collect the diagnostics. tower-diagnostics-20201031-1233.zip Edit: Note that I did not start the array when the collected this diagnostics file. It just occurred to me that it might be required. Should I collect another diagnostics file or is the one above enough? Edited October 31, 20205 yr by sywor
October 31, 20205 yr Community Expert Diags after rebooting won't be much help, also don't forget to try safe mode.
October 31, 20205 yr Author Booted into safe mode, started the array and let it run for an hour. So far everything seams normal as far as I can see. tower-diagnostics-20201031-1353.zip
November 3, 20205 yr Author Bumping my own thread. The problem is still there even in safe mode. And since the kworker consumes all the CPU the diagnostics never completes, even when I run it from the console.
November 4, 20205 yr Community Expert On 10/31/2020 at 12:55 PM, sywor said: So far everything seams normal as far as I can see. No need to bump, you said everything was normal in safe mode, and the diags are consistent with that, if it isn't please post diags showing that.
November 4, 20205 yr Author 9 hours ago, JorgeB said: No need to bump, you said everything was normal in safe mode, and the diags are consistent with that, if it isn't please post diags showing that. No that's not what I wrote. I cannot export diagnostics when it happens since it is by then it is already too late to do anything. Anyways. I have now turned on syslog persistence to flash. hoppfull at least the syslog should be saved when it happens again. Edited November 4, 20205 yr by sywor
November 4, 20205 yr Community Expert 20 minutes ago, sywor said: No that's not what I wrote. I cannot export diagnostics when it happens since it is by then it is already too late to do anything. Anyways. That's why I said no need to say you're bumping the thread, just report that. 21 minutes ago, sywor said: I have now turned on syslog persistence to flash. hoppfull at least the syslog should be saved when it happens again. That's worth a try, hopefully it will catch something.
November 21, 20205 yr Author The fault is back, this time the machine stayed up for 10 days. And the syslog is full of something suspicious I cannot decipher. It starts at 02:07:13 this morning (Nov 21) on row 358. Is my CPU broken? syslog
November 21, 20205 yr Community Expert Those errors are like related, but can't say what's causing them, you thing you can try is the latest beta, newer kernel works better with Ryzen.
Archived
This topic is now archived and is closed to further replies.