coolasice1999

https://pastebin.com/xqePujMQ Nevermind... I guess Pia's dns servers are dead, added cloudflare and away it went.

Mine started doing the exact same thing yesterday... Haven't changed a thing other then restoring a previous docker backup

Its not a powerhouse, it can't do a whole lot, but works seamlessly as a kodi sql server for all my media! (after quite a fandangle to get it automated) Very low power... at full parity check with 4 drives and 3 ssds, a Home Security NVR, Wifi Router, and Cable Modem... i'm drawing 99watts of power..... love it. Finally bought a Cyberpower 1500va UPS for those pesky power blips we've been getting during thunderstorms.

I tried to update my docker, but the new v3 radar is passing an error migrating my database to v3... had to roll back to v2 and restore my database from backup...

I picked up a handful of asmedia based 2 port cards to add ssds to my system. Filled up all my 1x slots. Kept my hds on hba card and now have 6 ssds connected.

moving appdata didn't fix it... but i did find that shutting down the array caused it to freeze and after a hard reboot it fixed itself.

That's the plan for tonight after work as the array is currently in use.

not sure how that's possible when the only folder on the cache drive is the appdata folder. Guess I'll have to run a backup tonight and do a restore on that one.

Okay but I only have 4 gigs of data on there how do I find out what else is using all the space? Even Windows tells me there's only 4 gigs of data on there.

Not sure if my cache problem is related to overhead on raid0 configuration or something else entirely. I have a raid0 configuration of 3 small 32gb SSDs which should yield 96GB cache pool which it does but the drive shows 18GB used. My appdata folder is only 4.4GB and is currently the only thing on the cache drive? What could possibly be using 14GB of information that wouldn't be shown in the drive? (there are no hidden files that I missed). Wondering if I should recreate the cache array?

Think i got it sorted... went ahead and recreated a new docker.img on the cache instead of an unassigned device, made it only 12gb and it seems to be working fine and updating as needed. Found out my hba doesn't support trim on ssds which was where the unassigned device was connected. Not sure if that had something to do with it.

So i went ahead and expanded my docker image size to 20gb... and once again, it still doesn't update. the only docker that does not give me problems is duckdns... it updates just fine, all others, binhex-jackett, mariadb, bazarr... none update properly, they look like they are updating, but never properly update. Annoyed to have to delete the docker every time to update it.. could having my docker.img on an unassigned ssd cause the problem?

Yea, I tried to figure out how to pass the variable to the file but alas I have no clue

there already is a tmm gui version, this used the same software just via commandline. there is one catch, if you use radarr/sonarr and your files get updated, tmm will not rescrape the data for the newer file, you have to do that manually with the gui version as it already thinks the movie is scraped. its a limitation to tmm itself.

to change the runtime you have to change the entrypoint.sh and rebuild the docker. I didn't try to hard to make it variable as it worked for my needs.