February 1, 20233 yr The official plex docker stopped working with a 403 error. I rebooted and the dockers are all gone. This is the second time this has happened. Any thoughts as to what it could be? nas-rm-unraid-diagnostics-20230131-1906.zip Edited February 1, 20233 yr by steelhead Added diagnostics
February 1, 20233 yr Community Expert Solution Probably you corrupted docker.img by filling it. Why do you have 100G docker.img? 20G is often more than enough. Making it larger won't fix filling it, it will only make it take longer to fill. Recreate docker.img. Try making it only 20G. If that is enough to start your dockers in then it is probably enough to run them in if you fix the reason you are filling it. The usual reason for filling docker.img is an application writing to a path that isn't mapped. https://wiki.unraid.net/Manual/Docker_Management#Re-Create_the_Docker_image_file https://wiki.unraid.net/Manual/Docker_Management#Re-Installing_Docker_Applications
February 1, 20233 yr Community Expert Before you recreate docker.img, set your system share to cache:prefer. It has files on the array, you should delete those and keep it all on its fast pool.
February 1, 20233 yr Community Expert Also, some of your array disks are too full. I recommend keeping at least 50G on each disk at least until you get things setup, figured out, and working well. You must set Minimum Free for each of your User Shares to larger than the largest file you expect to write to the share.
February 1, 20233 yr Author That seems to have worked. I reduced the docker.img to 20GB using a btrfs vdisk but I had it set to directory before. appdata and system are on cache prefer now too. I will reduce the disks shortly. Thanks you!
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.