tonsofguns Posted August 8, 2021 Share Posted August 8, 2021 I'm thinking this was caused by a docker update since I haven't added any new dockers in quite a while. Haven't changed anything. I've rebooted a few times to clear it and it's filling back up pretty fast. How can I tell what is filling it up? Can I prevent it from happening? r510-diagnostics-20210808-1717.zip Quote Link to comment
itimpi Posted August 8, 2021 Share Posted August 8, 2021 According to the syslog in the diagnostics the docker.img file is corrupt. Quote Link to comment
tonsofguns Posted August 8, 2021 Author Share Posted August 8, 2021 (edited) 18 minutes ago, itimpi said: According to the syslog in the diagnostics the docker.img file is corrupt. So I need to delete the docker.img and reinstall everything? All the dockers seem to be working until the log fills up. Edit: docker service won't start at all after this last reboot. gonna try recreating it. how can i find out what was filling the log to begin with? or would it be the corrupt docker image? Edited August 8, 2021 by tonsofguns Quote Link to comment
trurl Posted August 8, 2021 Share Posted August 8, 2021 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 filling it, 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. Your system share is set to cache-yes instead of cache-prefer. You want that share to stay on cache so dockers/VMs perform better and don't keep array disks spinning. Set system share to cache-prefer, then when you recreate docker.img it will go to cache and stay there. Do you actually have any VMs? Quote Link to comment
tonsofguns Posted August 8, 2021 Author Share Posted August 8, 2021 5 minutes ago, trurl said: Why have you given 50G to docker.img? Have you had problems filling it? No specific reason. I just set it to that 5 minutes ago, trurl said: Set system share to cache-prefer, then when you recreate docker.img it will go to cache and stay there. done 5 minutes ago, trurl said: Do you actually have any VMs? no Quote Link to comment
trurl Posted August 8, 2021 Share Posted August 8, 2021 Disable VM Manager in Settings and from that same screen delete libvirt.img Recreate docker.img at 20G https://wiki.unraid.net/Manual/Troubleshooting#How_do_I_recreate_docker.img.3F but don't reinstall dockers yet. Then post new diagnostics. Quote Link to comment
tonsofguns Posted August 8, 2021 Author Share Posted August 8, 2021 (edited) 16 minutes ago, trurl said: Disable VM Manager in Settings and from that same screen delete libvirt.img Recreate docker.img at 20G https://wiki.unraid.net/Manual/Troubleshooting#How_do_I_recreate_docker.img.3F but don't reinstall dockers yet. Then post new diagnostics. I've already started reinstalling them. I THINK this was caused by my cache being completely full. I was downloading an extremely large file and didn't think about it writing to the cache. I usually have around 190gb free on the cache and it was 100% full due to this download. Would that cause something like this? If it's not resolved after they reinstall I'll do what you suggest and repost the diagnostics. Edited August 8, 2021 by tonsofguns Quote Link to comment
trurl Posted August 8, 2021 Share Posted August 8, 2021 I mostly wanted diagnostics to see if you had cleaned up those shares. You can see how much of each disk each user share is using by going to User Shares and click Compute... for the share. Quote Link to comment
Recommended Posts
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.