shtnarg

Over the past few weeks I've tried a few things, Limiting ram to the frigate container etc. The issue persists and is very intermittent, This morning for instance, Im on my 3rd reboot in an hour. Docker keeps causing oom errors. This last time, It was with every docker container stopped, does this indicate the docker image itself is corrupt? Diagnostics attached before reboot. tower-diagnostics-20240818-0947.zip

Hi, About once a week I notice my cameras, via Frigate docker, are down. I sometimes can restart Frigate (through its GUI), but sometimes it doesn't come back up and that's when I notice the "Docker Failed to start" error in Unraid. It seems Frigate crashes (another issue) and potentially causes Docker to crash? I generally just reboot the Unraid machine at this point as I can never determine what the cause was and that brings my dockers back, recently though the entire docker image was corrupt and needed a rebuild. Hoping someone more familiar with the Diagnostics can point me in the right direction. Edit: I rebooted, All the dockers came back up. I stopped all but the critical dockers. CPU usage was pinned by docker. Docker Failed to start within 30 minutes. I attached a second set of diagnostics taken immediately after these series of events. Thank you. tower-diagnostics-20240721-1322.zip tower-diagnostics-20240721-1415.zip

In the case of UFS explorer, are both drives (the entire pool) required or just the 1 with the corrupt filesystem?

root@Tower:~# zpool import pool: disk2 id: 3778156303258639302 state: UNAVAIL status: One or more devices contains corrupted data. action: The pool cannot be imported due to damaged devices or data. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-5E config: disk2 UNAVAIL insufficient replicas md1p1 UNAVAIL pool: nvme-cache id: 9499952707851697450 state: ONLINE action: The pool can be imported using its name or numeric identifier. config: nvme-cache ONLINE nvme0n1p1 ONLINE

Hi, I've been helping a friend get an unraid box going over the last year. This week, we were doing some maintenance, updates and what-not. There were 2 Flash drives needed to keep the server happy? 1 seemed to have the key, the other the config? Not sure what happened there but, while consolidating the correct key to the correct drive, the incorrect config was loaded and the array started by accident. Its a 2x 4tb drive ZFS array with no parity. a 1tb NVME cache drive formatted ZFS. Disk 1 had about 1tb of data on it (nothing critical) The incorrect config set disk 1 as a parity drive. It started, was immediately noticed and shutdown. Correct config was reloaded and disk 1 now reads 'unsupported, missing or invalid file system'. With no dockers or VM's (although they appear to be on the cache drive). The Data on the drive is very replaceable, but if there is a possibility to recover the now blank unraid to where we were it would be desirable. Diagnostics attached. Thank you, tower-diagnostics-20240328-1805.zip.crdownload