mini_raid

Recreated this today. Seems to be working so far. Thanks for the help

Thanks! Will have a look at this tomorrow

So after getting a notification about my docker image getting threshold of 85% I started to look into how to determine if there was an issue. Getting good help from Spaceinvaders video (https://www.youtube.com/watch?v=9DxPEfbAJJ0&t=27s), I could see something very wrong. I have 82998 local volumes not connected to any containers that I know of. And Spaceinvaders script did not erase any of them when switching to "remove_unconnected_volumes="yes"". I've also tried with "docker image prune -a -f" via console terminal. But nothing reclaimed or deleted. How can I find what is (or was) causing this? Here is the log after I ran the user script: https://pastebin.com/bAjKDTVx I didnt paste all the lines because everything is the same after: mini-diagnostics-20240717-1614.zip

Hi, I have the same issue, though I have 82998 local volumes, but only 217 MB in size 🙃 https://pastebin.com/bAjKDTVx I also changed the script to "yes", but it does not reclaim anything. Anyone else that can help out here please?

So, I think I solved it... Stopped all containers, and started one at a time until I found that Rebuild-DNDC was looking like the bad guy. Obviously Rebuild-DNDC is the last one in my startup order too... so it took a while due to the 5 minutes wait time for each container 🤡 Rebuild-DNDC had cached all my *RR-containers for whatever reason, and tried a rebuild every 5 minutes triggered from the default configured CRON-job. I was not using any VPN-network for the *RR-containers. Probably something I've tested for a long time ago. Solution: Stop Rebuild-DNDC Delete all .tmp-files in Rebuild-DNDC /config-folder (in my case it was in "/mnt/user/appdata/rebuild-dndc" Start up Rebuild-DNDC Now it works like it should again. What still makes me annoyed is that I don't understand why there is no logs in the containers that "Rebuild-DNDC" tries to rebuild, or in the docker.log? Should be traceable some way that a container schedules a stop/start for other containers.

Yes, just tried this and it behaves the same. Is it something else I can try or look at during safe mode? I've attached a new diagnostics. mini-diagnostics-20231229-1152.zip

I can't say 100% sure, but I can't find any user script, scheduler, mover or appdata backup scheduled for every 5 minutes for these 4 containers. But maybe somewhere where I dont know to look. I would hope that a log somewhere would tell if this was the case though?

Hey guys, I have the weirdest thing happening with my RR-container (sonarr, radarr, bazarr & prowlarr). They restart every 5 minutes. And even when I stop the containers, they start up at the same time again when they usually restarts. E.g 19:45, 19:50, 19:55 and so on... Can't find anything specific in the logs that helps me, but maybe you guys can? These are the only containers behaving like this. I have probably 20+ more containers just running fine. I've restarted docker 2-3 times and also rebooted the server twice today. Same isssue still. Please let me know what else I need to collect, and also maybe how to collect it. I've started a syslog-server. But not sure what to do else with it for now. mini-diagnostics-20231228-1956.zip