I have been burdened with this issue for a while now the systems seems to randomly lock up requiring a hard reset.   I have updated BIO/BMC to the latest release, ran a memtest which is fine.  I am attaching a syslog which was captured before the system went down according to my monitor and it includes when I got around to hard resetting and downloading the log.  If someone could point me in the right direction that would be awesome. 

 

The monitor reports the system going down August 12, 1:18AM 

 

Motherboard - ASRockRack E3C252D4U

CPU - i5-10400

 

 

Syslog Before failure.txt

Nothing much to see, NIC was reset one day before the crash then the log only has the same repeating spam:

 

Aug 12 01:21:41 SikonUnraid kernel: igb 0000:0a:00.0 eth0: Reset adapter
Aug 12 01:21:41 SikonUnraid kernel: igb 0000:0a:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Aug 12 01:21:51 SikonUnraid key.dns_resolver: TANK.SIKONNET.COM: No address associated with name
Aug 12 01:22:06 SikonUnraid key.dns_resolver: TANK.SIKONNET.COM: No address associated with name
Aug 12 01:22:20 SikonUnraid key.dns_resolver: TANK.SIKONNET.COM: No address associated with name

 

Any idea what TANK.SIKONNET.COM is?

 

tank.sikonnet.com is a truenas system that is mounted on unraid. VM and docker backups are sent to this device 

 

 

Then it suggests the LAN never totally recovered after the NIC hang.

So the server locked up today again requiring a hard reset, I looked at the syslog and there was nothing there so I looked in the IPMI log and I do see the below.

I don't know how to figure out what is causing this.  

 

0049

Wednesday, August 23rd 2023, 10:11:57 am

Info0041hOS46h

os_stop_or_shutdown

20h6fha1h61h74hRun-time Critical Stop - Asserted
Event Data1 Run-time Critical Stop
Event Data2 N/A
Event Data3 N/A

this post explains similar symptoms 

 

I do have custom ip's set on a few dockers so I did change docker network type to ipvlan but yet I continue to have problems

Macvlan issues usually leave the call traces on the syslog, so probably not that, 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. 

Thanks for that information I will try to isolate