March 5, 20233 yr I have had some issues with improper shutdowns and the server starting parity after every shutdown, then I had a cache drive fail so I replaced it and during parity I had another fail. I have done the following: 1. Started a new config, I preserved the Array but built the cache pool with new drives. I added my process pool back with no changes. 2. I reinstalled my dockers using the previous apps reinstall. 3. I had some freezing issues so I deleted the docker image and started over again. 4. After reinstalling all again it seemed to be fine for a couple days. Today, I started having issues with dockers running slow and refusing to stop (example SAB went from download speeds in the 200-300M range to 1-2K range) , I get a server error while trying to stop the container. I stopped the docker service and tried to restart it but it shows yes but also shows it is not running, next I tried to stop the array and restart but array won't stop because cache target is busy. This server has been running pretty solid for a few years now, I have recently upgraded my internet to 2.5G fiber and changed the router to accommodate 2.5G. My backup server is running perfect after this change. I'm having a hard time finding the issue with this one so any help would be greatly appreciated. Seems like after a reboot it is more stable but the dashboard takes a long time to load (all adblockers are disabled for that site) and I can't update the dockers because I get server errors trying to stop the dockers Thanks in advance Phil crimson-diagnostics-20230301-0032.zip
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.