April 2, 20215 yr Hello, After updating Plex (Linusserver.io version), did Plex docker die. The docker did not want to stop, did try the other dockers, but none of them did stop. So I tried to restart Docker service, and now the service won't start. Some help ? Thanks! lucifer-diagnostics-20210402-1528.zip
April 2, 20215 yr Delete and recreate https://forums.unraid.net/topic/57181-docker-faq/#comment-564309
April 2, 20215 yr Author 1 minute ago, Squid said: Delete and recreate https://forums.unraid.net/topic/57181-docker-faq/#comment-564309 Will I need to download my dockers again, and set them up ? Edited April 2, 20215 yr by ChillZwix
April 2, 20215 yr Author 1 hour ago, Squid said: Not if you follow the directions (ie: Apps - Previous Apps) Thank you for help! It did work and things is back up running.
April 2, 20215 yr Community Expert @ChillZwix Why have you given 50G to docker.img? Have you had problems filling it? 20G is usually more than enough, and making it larger won't fix the problem causing it to fill, it will only make it take longer to fill. The usual cause of filling docker.img is an application writing to a path that isn't mapped. Linux is case-sensitive. Also, your cache was completely full in those diagnostics and that is probably what corrupted docker.img. You need to configure things so you don't fill cache or you will corrupt docker.img again and probably corrupt cache and have to reformat it. Go to Main - Array Operations and Stop the array. Go to Main - Pool Devices and click on Cache. Set Minimum free space to larger than the largest file you expect to write to a cached share. If cache has less than that amount free new writes will overflow to the array. Go to Main - Array Operations and Start the array.
April 2, 20215 yr Community Expert You might even consider not caching some shares. And don't think you can fix things by running Mover more often. Mover is intended for idle time. It is impossible to move from cache to array as fast as you can write to cache. If you need to write more than cache can hold, don't cache.
April 2, 20215 yr Author 1 hour ago, trurl said: @ChillZwix Why have you given 50G to docker.img? Have you had problems filling it? 20G is usually more than enough, and making it larger won't fix the problem causing it to fill, it will only make it take longer to fill. The usual cause of filling docker.img is an application writing to a path that isn't mapped. Linux is case-sensitive. Also, your cache was completely full in those diagnostics and that is probably what corrupted docker.img. You need to configure things so you don't fill cache or you will corrupt docker.img again and probably corrupt cache and have to reformat it. Go to Main - Array Operations and Stop the array. Go to Main - Pool Devices and click on Cache. Set Minimum free space to larger than the largest file you expect to write to a cached share. If cache has less than that amount free new writes will overflow to the array. Go to Main - Array Operations and Start the array. I have set a max size now, thank you! How do I reduze it? I have set it to 20GB now, but it still 50. does I need to delete and make a new one? 1 hour ago, trurl said: You might even consider not caching some shares. And don't think you can fix things by running Mover more often. Mover is intended for idle time. It is impossible to move from cache to array as fast as you can write to cache. If you need to write more than cache can hold, don't cache. I use it most for download. Did download a full serie that did fill it up..
April 2, 20215 yr Community Expert 2 minutes ago, ChillZwix said: does I need to delete and make a new one? yes
April 3, 20215 yr Author 53 minutes ago, trurl said: yes Thank you for help All fixed and up and running!
Archived
This topic is now archived and is closed to further replies.