I did not know how to describe this problem other wise than that it are random dropouts. So here goes;

 

My system has been running fine for some time now, I guess for about 1,5 years. I have ugraded the processor from a G4560 to a i5-7500 a couple of months ago but all fine.

 

The last 1,5/2 weeks I notice sites couldn't be loaded on my phone and computer. I have an Adguard container running and the DNS server of my phone and computer is set to it. When I can't reach a website I wait a few seconds, hit reload and all good. I have looked into the logs of the container and see there are timeouts. I tried reinstalling the container, using another image and switchting to adguard unbound but still the same behavior. I tried switching to PiHole but also the same behavior there.

 

I have Beszel running in a container and view the graphs today. I noticed there are random drops on the server. See attachd images.

When this happens I also can't reach my drive in Windows Explorer. I have looked in the log but nothing there, well at least nothing I can see. For example; I saw in Beszel I had an outage this morning around 09.30, I looking in the Unraid Log but no new entry after 09.00 (there are new entries now). So I do not really know how to trouble shoot this or what can be the cause.

 

Just to be clear. The system does not crash or shutdown. It keeps running. 

 

My system;

CPU: Intel i5-7500
Ram: 24GB ram
Mainbord: MSI H110I Pro
Nvme: Lexar NM790
Power: Mini-box picoPSU PicoPSU-160-XT

Edited February 7, 20251 yr by DutchTee86

Enable the syslog server and post that after a crash, together with fresh diagnostics.

Here is the syslog and diagnostics. According to beszel last outage on 14.14

syslog-1738737843 diagnostics-20250207-1422.zip

Edited February 7, 20251 yr by DutchTee86

Unfortunately, there's nothing relevant logged, this can also be a hardware issue, 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, including the individual docker containers. 

 

Additionally, look in the BIOS for a "Global C-States" or similar setting and disable that to retest, it's been known to be a problem with some boards, with both Intel and AMD CPUs.

Hi @JorgeB, 

 

Thank you for looking into it. Just to be clear the system does not crash. It keeps running. 

It means basically the same, replace crash with inaccessible.