Hey,
I've been 2 lockouts/freezes since I upgraded to 6.12.10 (might be unrelated but who knows).
I tried accessing the server through SSH but it seems to be completely locked out.
Only thing that helps is a cold shutdown through power button. 
When I try to reboot it just opens bios. I have to unplug the USB and let Windows repair it. After plugging it back in it works again.
Not sure if a USB could cause that lockout/freeze.

I managed to get the syslog and the diagnostics.
The freeze should have happened before 14:26 (where I booted it up again).

 

I do have macvlan activated since I own a Fritzbox but I followed the workaround here: 6.12.4 Changelog

Can someone identify the issue?

syslog-127.0.0.1.log homeserver-diagnostics-20240519-1434.zip

Edited May 19, 20242 yr by Ikeasofa

Unfortunately there's nothing relevant logged, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

Ah too bad. Could a bad RAM or a BIOS setting cause this? I change some settings that enables ASPM and some other stuff for powertop. I wonder if that could cause something.

1 hour ago, Ikeasofa said:

Could a bad RAM or a BIOS setting cause this?

It can.

I haven't changed any BIOS settings since months hmm.... The RAM was also brand new. Can you memtest them in unraid somehow?

7 minutes ago, Ikeasofa said:

Can you memtest them in unraid somehow

There is a memtest option on the Unraid boot menu.    However if you boot in UEFI mode you should download the latest version from memtest86.com as that also works in UEFI mode. but it would not do any harm to also use it if booting in legacy mode.

What does the legacy mode do? Is it the same as the safe mode?

1 hour ago, Ikeasofa said:

What does the legacy mode do? Is it the same as the safe mode?

No.  That is the none-UEFI boot mode that older machines use.

Current memtest included with Unraid also supports UEFI boot.

I've got some information that there is a bug on Browsers that have some kind of energy saving option for tabs. The bug causes the system to freeze. Is this known? I have been using Microsoft Edge all the time. Just giving some ideas for my problem 😅

That should not make the server crash, but it could possibly make the webGUI stop working, though you should still have CLI access.

could be that my issue is connected to this here. See:

 

I just had 2 people in discord with a freeze/lockout. What is going on lately? 

Just want to add to this topic as it keeps happening to me as well. I've had to to do several hard reboots lately which is making the whole system unreliable.

These are other similar reports on the same topic:

 

 

 

Enable the syslog server and post that after a crash.

also guys monitor CPU load average in top and if processes get stuck with:
 

unraid CLI:

while [ 1 -eq 1 ]; do ps -ax | awk '{ print $1,"---", $3 }' | grep D | grep -v PID && sleep 2 && clear; done

to monitor waiting processes

PROCESS STATE CODES D uninterruptible sleep (usually IO)

if lines appear and do not disappear, these processes build up and bring the system down, at least in my case. And with knowing which processes you can tell what docker is the reason - if it is a docker and if it is processes with status D.

@JorgeB - attached you have the syslog as I just had a freeze.

 

 

@gloeckle When it comes to CPU load average what I did a few days ago is to restrict partially access of docker containers to CPU cores, always keep 2 cores and 2 threads open. Obviously it didn't help. I will try what you suggested.

 

Edited June 8, 20242 yr by Thomas Edain

11 hours ago, Thomas Edain said:

attached you have the syslog as I just had a freeze.

Unfortunately there's nothing relevant logged, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.