I am stuck trying to understand why this is occurring:

• Approximately every 8 hours or so, the server becomes unresponsive and requires a hard shutdown to come back online.
• The most recent changes that I made was adding
  • Frigate docker container
  • Coral USB Accelerator for Frigate

Woke up early (thanks dog) and thought I would logon and check. I was able to log in the dashboard and things seemed ok, then I clicked into Settings and got a warning about the flash drive being corrupted then the system went unresponsive. I checked the flash drive and it appears fine. I power cycled the box and it's now up and running again, but I am sure it will being unresponsive again. Flash drive reports no issues.

One last item, not sure if it means anything, but it's a "hmm" item: on my router, I see 2 MAC addresses to the same box. Only one network connection is enabled. The second address shows when docker is enabled, so it must be something with the custom network...?

 

Here is the last few lines of the server log. I searched (and am still looking) for what the state changes are signifying.
Also, attached is my diagnostics.

 

Aug 17 23:15:06 barad-dur kernel: br-f4287f76e280: port 15(veth6094d97) entered blocking state
Aug 17 23:15:06 barad-dur kernel: br-f4287f76e280: port 15(veth6094d97) entered disabled state
Aug 17 23:15:06 barad-dur kernel: device veth6094d97 entered promiscuous mode
Aug 17 23:15:06 barad-dur kernel: eth0: renamed from vethb86ba36
Aug 17 23:15:06 barad-dur kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth6094d97: link becomes ready
Aug 17 23:15:06 barad-dur kernel: br-f4287f76e280: port 15(veth6094d97) entered blocking state
Aug 17 23:15:06 barad-dur kernel: br-f4287f76e280: port 15(veth6094d97) entered forwarding state
Aug 17 23:15:16 barad-dur kernel: vethb86ba36: renamed from eth0
Aug 17 23:15:16 barad-dur kernel: br-f4287f76e280: port 15(veth6094d97) entered disabled state
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Aug 17 23:15:16 barad-dur kernel: device veth6094d97 left promiscuous mode
Aug 17 23:15:16 barad-dur kernel: br-f4287f76e280: port 15(veth6094d97) entered disabled state
Aug 17 23:18:05 barad-dur kernel: vethe5c4a51: renamed from eth0
Aug 17 23:18:05 barad-dur kernel: br-f4287f76e280: port 13(vethc8cc9a2) entered disabled state
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Aug 17 23:18:05 barad-dur kernel: device vethc8cc9a2 left promiscuous mode
Aug 17 23:18:05 barad-dur kernel: br-f4287f76e280: port 13(vethc8cc9a2) entered disabled state
Aug 17 23:18:05 barad-dur kernel: br-f4287f76e280: port 13(vethf985418) entered blocking state
Aug 17 23:18:05 barad-dur kernel: br-f4287f76e280: port 13(vethf985418) entered disabled state
Aug 17 23:18:05 barad-dur kernel: device vethf985418 entered promiscuous mode
Aug 17 23:18:05 barad-dur kernel: br-f4287f76e280: port 13(vethf985418) entered blocking state
Aug 17 23:18:05 barad-dur kernel: br-f4287f76e280: port 13(vethf985418) entered forwarding state
Aug 17 23:18:05 barad-dur kernel: eth0: renamed from vethebad642
Aug 17 23:18:05 barad-dur kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethf985418: link becomes ready
Aug 18 03:48:29 barad-dur webGUI: Successful login user root from 10.69.1.233

 

barad-dur-diagnostics-20240818-0443.zip

Unfortunately there's nothing relevant logged, this can 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.

I will do that now. 
Anything that I might be able to do to help isolate the failing/failed component?

I restarted in safe mode 8 hours ago. I was able to start docker and am using plex without issue.
So far, so good. Hopefully this does turn out to be software as I can work that out.