Bsdragster

Sorry for the late response, but at this point I think this issue can be considered resolved as it has not occurred again. I have not installed all of the previous dockers containers again and only have Plex, qBit, and Gluetun running. The docker image file constantly increasing in size is a separate issue that is not occurring for now. The cache pool is working fine for now and the other cache drive I was using also had errors so I simply reformatted that drive and no issues.I will remove the overclock and continue monitoring. Thanks for the help.

Thanks for the response. Terminal worked on Edge and the command brought back the docker. However, I have limited time before the server simply stops responding and I have to reboot the system again. It occurred to me to try to backup the docker image and when I made my way to the directory, I noticed the image file size was 32gb and my settings are set to 30gb. Thinking this might be the issue, I raised the limit to 50gb. I went back to the docker image file and noticed it immediately jumped to 53gb. I am attaching two diags. The first one is after raising the docker image to 50gb wherein the server hung up and I rebooted. Once it came back up, the unmountable error appeared. I typed the command again in the terminal, restarted array and ran another diag which is the second one. As I type this post, the server has not hung up again....yet... umbrella-diagnostics-20250619-1916.zip umbrella-diagnostics-20250619-1920.zip

So this past weekend I was advised by a friend that my Overseerrr was not working. I logged into the server and restarted the container and issue resolved. A while later, I was informed again that it was not working. This time, I was not able to log into the server or any container. Without thinking, I hit the reset button on the case to reboot the server and everything was fine after that. The next day, it failed again and I rebooted the system again which is when I noticed that the docker service failed to start and the cache pool had the error Unmountable: wrong file system. I tried finding a resolution to this on but have not been able to. I cannot use the terminal as the display is distorted and I cannot see anything. Nothing on the server has been installed or modified recently so I am unsure what could have caused it other than hardware failure or random software glitch. These drives contain the docker image of which I do not have a backup but I do have backups of the appdata and flash drive. If I reformat the pool, install containers, and transfer the latest appdata backup, will this restore the docker configs to what I had before? I am not looking forward to setting up all of the containers again but if I have to then so be it. I was on 7.0rc2 and updated to 7.1.2 after this issue appeared hoping that would resolve it but that didn't work. I have not tried a repair as I'd like to exhaust other options before going that route or reformatting. I did remove the drives and connect to my main PC which showed the drives are completely empty. When I start the array in maintenance mode and check the filesystem I get this response. Any help is greatly appreciated. [1/8] checking log [2/8] checking root items [3/8] checking extents [4/8] checking free space tree free space info recorded 9977 extents, counted 9978 There are still entries left in the space cache cache appears valid but isn't 1104150528 [5/8] checking fs roots [6/8] checking only csums items (without verifying data) [7/8] checking root refs [8/8] checking quota groups skipped (not enabled on this FS) Opening filesystem to check... Checking filesystem on /dev/sde1 UUID: 2cf09a03-f2c8-4272-9158-5a0d43294a8e found 131904970752 bytes used, error(s) found total csum bytes: 32962436 total tree bytes: 353304576 total fs tree bytes: 269467648 total extent tree bytes: 38502400 btree space waste bytes: 72317847 file data blocks allocated: 494660153344 referenced 121333932032 This is what the terminal looks like. umbrella-diagnostics-20250615-2244.zip