Hello!

I am not sure since when, but for some weeks now, my Unraid server every couple of days freezes, the Web UI is not accessible, nor is any of the apps that I run there, is like the server is dead but the computer still runs.

When that happens I have to brute force shutdown the server and turn it on again.

 

From other topics here in the forum I saw that the issue could be solved by setting the docker to ipvlan, but my server was already with that setting, so it is something else.

 

Also I enabled the syslogs as I saw was requested in other topics and I will attach here the log. My server freezed on the 10th of October, but I do not see nothing in the logs strange (I have my discs full except the nvme cache, so some warnings there in the log).

 

I thought maybe it is a bad USB so I have ordered a new Samsung one today, the one suggested in this video https://www.youtube.com/watch?v=jjkaidlZmgs

Could someone take a look and help me? I need to have the server reliable again.

 

Best Regards,

Pedro

syslog

Check that this has been taken care of:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

 

Thank you very much! Never thought of that!
Will try it, if the server holds for a week I will set as solution.
Just do not understand why the server in the past worked months at a time, and now fails with me not having changed the bios settings

Tryed the "typical current idle" solution and it hold up until today, but today it frooze, will now try the "completely disabling C-States"

Just to give feedback, after "completely disabling C-States" my UnRaid server is working non-stop for 28 days! I guess it is solved

Hello,

I am back.... So shortly after my last message the server frooze again. And ever since it still frezes frequently, some times 10 days apart, sometimes 5 days, sometimes 15 days.

Since we solved the C-States, I am unable to find a reason.

Do you think it may be do to low disk space? I will attach photo of my disks. And the latest pre-frezzee logs

syslog-previous

1 hour ago, TZodiacK said:

Do you think it may be do to low disk space?

Very unlikely, unfortunately there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker/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.