tknx Posted June 12, 2022 Share Posted June 12, 2022 Was trying to install some dockers and ran into errors. Fix Common Problems shows the following: The only new thing is I added a new drive to the array. I looked through my logs and see a ton of bluetooth errors? No idea why or what is going on there. Diagnostics attached. mnemosyne-diagnostics-20220611-2013.zip Quote Link to comment
JorgeB Posted June 12, 2022 Share Posted June 12, 2022 Go to the board BIOS and see if there's an option to disable the Bluetooth module. Quote Link to comment
tknx Posted June 12, 2022 Author Share Posted June 12, 2022 Yeah - I will try that, but what is going on with that docker image? Quote Link to comment
Solution trurl Posted June 12, 2022 Solution Share Posted June 12, 2022 27 minutes ago, tknx said: what is going on with that docker image? Probably you have corrupted it by filling it. The fact that it is currently using 45G of the 100G allocated is further evidence that you have something wrong with one or more of your docker applications. 20G allocated is often more than enough. Maybe a little more depending on how many and which dockers. But not as much as you have. The usual reason for an application to fill docker.img is writing to a path that isn't mapped to host storage. Quote Link to comment
tknx Posted June 12, 2022 Author Share Posted June 12, 2022 Yep - I disabled bluetooth and it is fine. Not that I am using bluetooth, but I would love to know how to fix this error since it feels like cheating Quote Link to comment
tknx Posted June 13, 2022 Author Share Posted June 13, 2022 So my docker image is quite large still, but diagnostics look cleaner. mnemosyne-diagnostics-20220613-0816.zip Quote Link to comment
trurl Posted June 13, 2022 Share Posted June 13, 2022 Go to Docker, click Container Size button, and post the results Quote Link to comment
tknx Posted June 13, 2022 Author Share Posted June 13, 2022 So, it says I have 40GB+ to scrub, but these sizes seem okay - maybe it is all good? Name Container Writable Log --------------------------------------------------------------------- binhex-jellyfin 2.98 GB 781 MB 506 kB calibre 1.79 GB 368 MB 49.0 kB calibre-web 1.24 GB 624 MB 81.2 kB binhex-sonarr 1.19 GB 62.5 MB 1.61 MB binhex-mc-creative 1.17 GB 298 MB 80.6 kB binhex-mc-peaceful 1.17 GB 298 MB 81.0 kB frigate 1.10 GB 4.39 MB 1.84 MB binhex-radarr 969 MB 155 MB 1.90 MB telegraf 493 MB 139 MB 4.63 MB postgres 419 MB 43.4 MB 7.27 kB CloudBeaver 380 MB 434 kB 17.6 kB Influxdb 341 MB 0 B 145 kB HDDTemp 339 MB 0 B 0 B mariadb 293 MB 16.5 kB 21.3 kB Grafana 286 MB 0 B 14.1 MB vaultwarden 197 MB 0 B 216 kB promtail 184 MB 0 B 7.44 MB cops 167 MB 24.7 MB 42.8 kB vernemq 160 MB 20 B 7.53 kB GrafanaLoki 60.8 MB 0 B 9.25 kB syncthing 48.0 MB 11.6 kB 34.5 kB CaddyV2 44.4 MB 0 B 1.81 MB mosquitto 11.8 MB 89 B 35.4 kB --------------------------------------------------------------------- Total size 15.0 GB 2.80 GB 34.7 MB Label: none uuid: 9757a167-f114-4ae6-adc7-322ad0955765 Total devices 1 FS bytes used 43.04GiB devid 1 size 100.00GiB used 48.07GiB path /dev/loop2 btrfs scrub status: UUID: 9757a167-f114-4ae6-adc7-322ad0955765 Scrub started: Sun Jun 12 16:34:09 2022 Status: finished Duration: 0:06:19 Total to scrub: 43.92GiB Rate: 119.16MiB/s Error summary: no errors found Quote Link to comment
trurl Posted June 13, 2022 Share Posted June 13, 2022 You could just delete, recreate as 30G, reinstall your containers from previous apps. https://wiki.unraid.net/Manual/Docker_Management#Re-Create_the_Docker_image_file https://wiki.unraid.net/Manual/Docker_Management#Re-Installing_Docker_Applications Quote Link to comment
trurl Posted June 13, 2022 Share Posted June 13, 2022 Why did you make it 100G to begin with? Quote Link to comment
tknx Posted June 13, 2022 Author Share Posted June 13, 2022 I honestly don't remember why. Maybe I was facing a similar log issue in the past and just upsized to buy time? Does it really matter though? Quote Link to comment
trurl Posted June 13, 2022 Share Posted June 13, 2022 1 hour ago, tknx said: Maybe I was facing a similar log issue in the past and just upsized to buy time? Increasing size of docker.img won't fix the problem of filling it, it will only make it take longer to fill. You should try to get to the bottom of why you fill docker.img with it only 30G as I recommended. 1 hour ago, tknx said: Does it really matter though? It is wasting space and possibly causing you to ignore problems with one or more of your container configurations. The steps I linked in the wiki are simple. Did you read them? Quote Link to comment
tknx Posted June 13, 2022 Author Share Posted June 13, 2022 Yeah - I will change it. I believe the last time I just upped it since I didn't have time to deal with the log issue and then fixed the log issue and didn't downsize. But I guess I'll reduce it back. Thanks! 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.