netfox

I will like to move a Docker from Unraid to Debian+Portainer. how can I extract the Docker run command from UNRAID? I then will composerize.com it to use it with portainer

Hi All, I encrypted the arrays, however now, I will like that the Array starts without have to type the password. I dont care about the array encryption security at this point, is there a simple way of setting the encryption Passphrasse in Unraid so it will auto start the array at boot? John

Hello, I'm on Version: 6.12.3, why docker is taking 30gb (39%) of memory with no running containers? If I disable Docker than docker memory will go to ZERO.

How can I Rolled back to 6.11.5? And which is the best version to rollback to avoid this issue?

What go2rtc version are you running, its still crashing on m with the 1.5

Me and other users opened issues on github, unfortunately we were not able to fix the OOM error. https://github.com/blakeblackshear/frigate/issues?q=is%3Aissue+"out+of+memory"+

Unraid Version: 6.11.5

We actually opened multiple post on github for the OOM, I am also running Dev release frigate:dev-7e5abe7 (go2rtc 1.5) however it is still happening. I also disabled go2rtc and user rtsp, same crash We actually have 2 issues: 1) Frigate causes OOM 2) Unraid crashes when a container gets OOM I also opened a ticket with Unraid, however I haven't had not reply yet John

Same here, my server keeps going down.

Hi guys, Frigate container OOM causes Unraid (Version: 6.11.5) Crash I am also using the following parameter so not sure why it crashed the server: --memory=3G --shm-size=1024mb --mount type=tmpfs,target=/tmp/cache,tmpfs-size=100000000 --restart unless-stopped Any suggetion on what to do to avoid that a container oom causes a unraid server crash? I tried --memory=1G 2G and 3G with no difference. Unraid crashes. Here are more details on the OOM error: Thanks

Is it possible to backup a single VM, as example with an export and eventually import afterwords? And where VMs are stored, cant find /etc/libvirt/qemu John

The Frigate container was eating all of the ram, I added --memory=2G however the container keeps bringing down the server and gets unresponsive. The only think to do is to hold the power button and start again the server

Hi guys, I had the message : Legacy PCI Stubbing found, so I wanted to reconfigure my config to ht lates passtrough: This is my cold config I removed "pcie_acs_override=downstream vfio-pci.ids=8086:150e" however the server does not boot this is what I see in the vfio-pci.cfg BIND=0000:01:00.0|8086:150e 0000:01:00.1|8086:150e 0000:01:00.2|8086:150e 0000:01:00.3|8086:150e I restored the old config and now i am getting this error this is my Attaching diagnostic unraidsrv-diagnostics-20230319-1919.zip

Here is an other crash and grafana and influxdb and telegraph were also off:

My guys, my pfSense VM crashes I actually see only a spike in CPU usage in Frigate: and spike in read as spike in system: These are the red errors in the logs: And these are the logs