DrSpaldo

Hi @MrK, yes, I do think that was either the primary cause or a big part of it. Although I have no concrete proof. I know originally when I was deep into the issue, I found out that the --memory line doesn't always work with Unraid. I did a quick search earlier and didn't find the exact post where I remember seeing it though... Here are a few to look through that may help - Unraid OOM Issues · blakeblackshear/frigate Edit: check this post to see if you are using the fuse file system for your Unraid Frigate container - FUSE post - Frigate Github

No worries, thanks @bucketphobia@itimpi

@bucketphobiaI've turned on the permit exclusing shares, however, I don't see how to turn on the exclusive access part anywhere. Although, I do remember that I did change the default for my dockers to point directly to the drive and not use fuse... /mnt/cachetwo/appdata/opera rather than /mnt/user/appdata/opera

Thanks @bucketphobia, I will also turn that on. Fortunately mine has died down heaps since I made the above other changes, but who knows what the actual root cause is. Seems to be so many people in similar (but not exactly) the same situation

I would love to say that I figured out exactly what was causing the issue, but, I didn't. I made so many changes and in the end I am not sure if it was one of them or the combination of them. I am not getting the same CPU max out or freeze/crashes that I was before. It is back to normal. Here are some of the things that I did: - Daily script to delete docker locks - increase tmpfs run size script on boot - create 4G tmpfs plex ram scratch script on boot - use the swapfile plugin - change the VM dirty background ratio - Replace the MB & CPU - Replace the SATA card - Pinned CPU cores / docker isolation - Move some of the things running on Unraid to my Proxmox server; this included the Frigate container (my CCTV) & the Windows VM I would say that I noticed some differences from the top down, but, the main one was moving Frigate & the VM to the Proxmox server. I am sorry this isn't a good answer, but I just don't know. When you start searching for similar issues, many many people are having them as well, just in slightly different ways. The Unraid staff are not really helping (only sometimes, then they just give up). Fortunately I had JorgeB trying to help in this instance.

For those having issues with MagicMirror after the most recent update (constant reboots, essentially not starting up) It looks like for me it was the plugin/module MMM-MyCalendar breaks it. I have disabled it for now and there has been a issue created below. Let's hope it is looked at soon... Release 2.25.0 of MagicMirror breaks the module · Issue #40 · jclarke0000/MMM-MyCalendar (github.com)

Hi @Giorgioare you able to expand on how you did this? I am thinking of doing the same...

Hi, I just left it at the default (60)

Is there a reason the swap file would fill up if I still had heaps of ram free? Today I had about 30 gigs RAM free and the swap file was sitting at around 7 gig (91%)

I've switched that (Frigate container) over to my Proxmox server. So I will see how it goes...

Thanks for the reply @yayitazale. I will try some of these changes on my system and see if it makes a difference.

Add me to the list. I have been having issues on and off since June. It started happening after updating Unraid from 6.9.2. I have since updated a few times with no great change, I am now running 6.12.3 I can't remember all the changes that I have made to the Unraid system itself along with the Frigate container. But it seems to have limited it recently to one crash/system freeze per week. Here is part of my journey

Ah ok, interesting. My Ubuntu VM is actually still running without issue. So maybe not that!

@Mbeco although it hasn't 100% fixed the issue (and I changed so many things in the process, they could also take part) but one of the top 3 potential issues that I feel it may be was the VM's I was running. I am running a Windows 10 VM & MacOS VM. I cannot tell you which was the most likely culprit but I lean towards Windows. For me, what I did was move both of the VM's over to another Proxmox server I had. Obviously this is not a solution, but, like you, I didn't have the time for weeks of downtime like people above have suggested. Because to truly work out what is causing the issue, you would need massive amounts of server downtime as well as your own time sitting there watching. If you can, I suggest turning off one of the VM's, or better still if you have spare hardware, move them over to a Proxmox instance and just see if that helps your situation. If it doesn't, then I can make suggestions on what I did for my docker troubleshooting & changes along the way... PS. I see you are using PhotoPrism. You should give a very nice project Immich a go. Although in early development, I have been very impressed so far. There is an Unraid community app as well.

Thanks for the reply & info @primeval_god