First real issue I've had with Unraid since purchasing over a year ago so that's a plus for the product, but I've been having serious issues the past two plus weeks.  It started with the server essentially being resource locked (or what appeared to be).  UI wasn't responding and CLI showed a rather long hex code error.  Okay no big issue, quick restart should fix it.  Restarted seemed fine until the next day...boom same issue.  Went through the system to make sure I didn't have any kind of hardware issues (loose plugs etc.) causing the issue and restarted the device.  Few days later, system rebooted randomly at 11:30 at night...most VM's and Dockers failed to start upon reboot.  

 

Looked through the logs and I see a couple of corrupt video files from Frigate, but nothing that 'should' crash a system, however, the a long hex error code was present there as well.  This morning I woke up to email errors saying my FlightAware and a few other systems were offline for most of the night, logged in and see the error message that docker service failed to start.  At this point the only other thing I can think is a USB drive going bad perhaps?   Attached the syslog file from Feb. through today to assist, but any insight would be greatly appreciated.  

syslog-Feb_Current.zip

You appear to have a docker container constantly restarting, check the up times to see which one it is.

 

There's also a network configuration issue:

br0: received packet on bond0 with own address as source address (addr:c8:7f:54:66:c2:5d, vlan:0)

 

Fix that and also try this to see if it helps with all the PCIe errors:

https://forums.unraid.net/topic/118286-nvme-drives-throwing-errors-filling-logs-instantly-how-to-resolve/?do=findComment&comment=1165009

 

Then start a new syslog and post that after the next crash, hopefully it will have a lot less spam.

 

Thanks much.  Ill report back when/if it happens again with a new syslog.

 

Froze up this morning.  Been happening pretty frequently so I swapped out USB sticks hoping that was the issue. Worked great for a few days then boom right back to waking up to frozen system with the same log output of hex code.  

syslog-172.16.0.150.log

Several apps segfaulting, would recommend running memtest.