May 30, 20197 yr I have been using unRaid for some time and never had an issue prior to the 6.7.0 update. Since the update it seems when Mover runs the array becomes extremely bogged down webui's of dockers begin failing to load, plex (hosted on a seperate server) is unable to play files over network from the array and if they do start will buffer constantly. I have moved things like AppData folder on and off the Cache drive to see if it made a difference with no success. NetData shows write speeds across the array are still rather high, however the cache drive itself has not freed up any space in the time mover has been running. Any help or recommendations to try solve will be greatly appreciated. tower-diagnostics-20190530-0001.zip
May 30, 20197 yr Your appdata, domains, and system shares are on the array. They should be on cache. Also, your docker image is much larger than necessary. 20G is the usual recommendation. I don't know what you may have had before but the way you have it now is not going to perform well.
May 30, 20197 yr Author Used to have appdata on cache had same issues. Will move that all back to cache now and see if the problem continues. Looking at other posts seems a common'ish problem on 6.7.0. Docker container was getting errors about being full in the past and since I had the space I just made it bigger to stop them. If a smaller docker image effects performance for anything other than free space I will change it back otherwise it makes little difference.
May 30, 20197 yr 2 hours ago, TehRobot said: Docker container was getting errors about being full in the past and since I had the space I just made it bigger to stop them. If a smaller docker image effects performance for anything other than free space I will change it back otherwise it makes little difference. If you find that the docker image is running out of space then it almost certainly means that you have at least one docker mis-configured so that it is writing files internally to the image. If properly configured one expects docker variable information to be written to locations external to the docker image.
May 30, 20197 yr Author Have moved the appdata, domains and system folders back to the cache drive. I got an error from the docker image so have deleted and redone that. Your existing Docker image file needs to be recreated due to an issue from an earlier beta of Unraid 6. Failure to do so may result in your docker image suffering corruption at a later time. Please do this NOW! So far have had no issues but time will tell. itimpi, I have no leaks in my dockers and most of the usage comes from Sonarr and Radarr storing metadata info within the docker. Happy to provide my configs if you think I am still missing something. Before the reinstall they were sitting at 17gb and since I have not reinstalled a large number of dockers it is only at 8gb.
May 30, 20197 yr 23 minutes ago, TehRobot said: most of the usage comes from Sonarr and Radarr storing metadata info within the docker These would normally be configured to store this externally to the image file. Ideally You do not want any variable data stored within the image file - just the binaries for the container.
June 2, 20197 yr Author Parity ran yesterday and completed the fastest it has in ages and didn't cause the server to hang at all, during the time it ran. So seems to have done the trick Thanks heaps. On 5/31/2019 at 4:17 AM, itimpi said: These would normally be configured to store this externally to the image file. Ideally You do not want any variable data stored within the image file - just the binaries for the container. I only have the config files mapped to the docker everything else is on the array. Looking at the files seems it is the images and info for the movies and tv shows. When I run docker ps -s I can account for 7.5gb but the docker image is at 14gb. Have run prune and removed all dead containers.
Archived
This topic is now archived and is closed to further replies.