RobFlix
Members
-
Joined
-
Last visited
Solutions
-
RobFlix's post in Unable to stop containers which leads to unclean shutdown. Parity check running at 136kbps was marked as the answerJust wanted to follow up in case anyone else has had similar struggles. I was able to get a refund for my 14900K and replaced it with a 12900K. I installed the new CPU Saturday and have not had a single blip. It appears completely stable and the 12900K is still more than overkill for my usage with room for growth. Thanks for the input JorgeB!
-
RobFlix's post in Replaced single cache m.2 with two m.2's. Lost docker settings. was marked as the answerOK, I'm pretty much whole again. I had issues with multiple Dockers. The above was just an example. I went through each folder in appdata on the old drive, found the corresponding files on on the new cache pool, deleting them, and copying over the old files. Once I did that and fired the containers back up almost everything was back as it was. I did need to re-apply the api key from Prowlarr to all of the indexers in my *arr suite and qBitorrent may or may not be using my VPN. That's the last issue I need to resolve. Appreciate the pointers.