007craft

I did eventually resolve the issue.  The problem was that the hard drive I have been recording all my Camera footage to (With Shinobi) had died and Shinobi was constantly throwing up errors.  These errors were essentially 1000+ a minute and so after a day or 2, the memory would get flooded and cause this meltdown on unraid.  I didnt notice because using Shinobi, I could still see the camera streams and dont often check the saved footage and in the software, there was no obvious errors posted unless you poked around and looked for the logs.

So the problem was being caused by the Shinobi docker.  But thats not to say others cant have the same problem caused by different issues with other dockers.  Whats clear here is Unraid failed to provide any sort of logs/indication that the problem was being caused by memory overflow from a docker.  So if youre having this problem yourself, I recommend going down to 0 dockers, and enabling one after each week of stability to make sure no one individual docker is causing your problem, since one definitely COULD be

From Unraids end, I would like to see some improvements made to the error reporting system.  A docker (Any docker container) should not be allowed to get out of control like this where it takes down my entire server, and then the server doesnt even tell me anything thats wrong and just stops working, throwing up USB not recognized errors.  How about an error that says something like "hey you have a docker thats utilizing 80+% of all your memory.  Or "memory usage is increasing in this docker, etc etc.  SOME sort of indication that could help troubleshoot.  I wasted WAY too much time trying to solve this issue and unraids logging was useless in trying to diagnose the issue.