Camo200sx

I'm back. I ended up disabling the VM backup plugin. I think it was causing the cache drive to become full and everything to grind to a halt. Filesystem Size Used Avail Use% Mounted on /dev/loop5 90G 26G 65G 29% /var/lib/docker

OK. I didn't reboot, but rebuilt my dockers 2 days ago. Attached logs. Sorry been super busy. Container size only 2.82GB I had a custom ntp server. From memory had issues with time. Without I see a 4min difference vs local time. Odd. Have removed for now. camraid-diagnostics-20260219-0747.zip

I don't think it was filling beyond about 30g. I did increase it to 90 at one point just because I noticed it close or to try solve this issue I'm having. Will have to monitor.

Would be greatful if someone could please take a look at my logs. Thought this was an issue to do with running out of space but has since happened with lots of free space. Hoping someone more knowledgeable can help me out here. Basically every week this seems to happen and I need to delete the docker Img and re-download all dockers. It's getting pretty old now. Thanks! camraid-diagnostics-20260216-0704.zip

Thanks. I'm familiar with this and did just that :). Previously had this issue twice but believe it to be unrelated (disk ran out of space). This time though it seems related to not being able to shut down cleanly. Something hopefully doesn't happen often as I live in the boonies and the power isn't so reliable.

Long story short - power failed middle of the night. I have a UPS and it would appear from the logs that there was an unclean shutdown, now I have no Dockers. Can anyone understand why this would have happened and if that is the reason why I now have the "No Docker containers installed"? Thanks! Logs attached P.S. This is from Gemini 👇🏼 This log confirms exactly what happened: The UPS worked perfectly and commanded a clean shutdown. The Unraid shutdown script failed to stop a process that was using your cache pool. Because it couldn't unmount the cache pool, the pool was not cleanly exported. This directly caused the "unclean shutdown detected" error you saw in the first log. When the server booted back up, it saw the "busy" or "unclean" cache pool. This likely led to the docker.img and libvirt.img files (which live on that pool) being inaccessible or appearing corrupt, forcing Unraid to create new, empty ones. The root cause was a process that refused to close, preventing your ZFS cache pool from unmounting cleanly. camraid-diagnostics-20251113-1916.zip

Any luck? I have the same issue. Nothing I do fixes it

Anyone experience this in radarr and sonarr using the tailscale integration? With tailscale enabled, NZBGet fails. I think it's DNS related but I'm no good at networking

Just to others out there that find this. Have been battling with the binhex version and couldn't get it to work so tried the official. All is well without adding anything to the go file . Am using a 12400