January 21, 20251 yr Hi my fellow Unraiders, Many of my dockers apps are not working after I have updated my server with the latest Unraid OS 7 update from v6.12. When I start some of them they stops i.e. Radarr and QdirStat. I was wondering if I could have some help. I have a warning about the size of the hardware where the vm is located. I thought it could have been the size of the docker image, so I have increased it to 200 Gb but it didn't fix it. I have included the diagnostic file before and after rebooting the server. kingfisher-diagnostics-20250121-1233 (before reboot).zi kingfisher-diagnostics-20250121-1233(after rebooting).zip
January 21, 20251 yr Community Expert 37 minutes ago, Yannoviche said: size of the docker image, so I have increased it to 200 Gb but it didn't fix it. That would only hide the problem if docker.img was growing, and it would eventually fill up again. Your diagnostics shows you were using 34G, which is more than default 20G size, but might be reasonable if you have a lot of containers. If it normally uses that much, and it isn't growing, then you might consider 40-50G. Was usage growing? The usual cause of that is an application writing to a path that isn't mapped. 40 minutes ago, Yannoviche said: warning about the size of the hardware where the vm is located. Are you actually talking about VMs here? Not related to docker. Can you post the exact text or a screenshot? 42 minutes ago, Yannoviche said: When I start some of them they stops i.e. Radarr and QdirStat. Have you looked at the logs for those containers? You can access the logs for a container by clicking its icon and selecting Logs.
January 21, 20251 yr Community Expert On the Docker page, click Container Size at the bottom and post the results.
January 21, 20251 yr Author 8 hours ago, trurl said: On the Docker page, click Container Size at the bottom and post the results. Hi @trurl, Thank you for the help. Here is the container size. Container Size Name Container Writable Log tdarr 3.47 GB 170 MB 48.9 M binhex-overseerr 3.43 GB 1.18 GB 6.66 k tdarr_node 3.01 GB 82.2 MB 43.7 M binhex-sonarr 2.38 GB 490 MB 73.2 k binhex-lidarr 2.36 GB 345 MB 73.3 k binhex-delugevpn 2.28 GB 650 kB 6.86 k binhex-qbittorrentvpn 2.21 GB 1.23 MB 550 k binhex-radarr 2.03 GB 463 MB 12.7 k binhex-prowlarr 1.96 GB 428 MB 74.3 k homeassistant 1.73 GB 0 B 37.5 M binhex-emby 1.66 GB 74.1 MB 50.3 k jellyseerr 1.42 GB 0 B 12.9 M luckyBackup 1.29 GB 594 kB 12.3 k unmanic 1.20 GB 21.9 kB 16.7 M Krusader 1.13 GB 3.12 MB 14.7 k Nginx-Proxy-Manager-Official 1.09 GB 28.8 kB 18.1 M binhex-syncthing 1.06 GB 3.81 kB 15.4 M Jellyfin 1.04 GB 16.7 kB 101 k homarr 989 MB 2.20 MB 3.34 k Emulatorjs 873 MB 31.7 kB 43.6 k netdata 607 MB 1.76 kB 13.9 k romM 575 MB 15.7 MB 42.8 k telegraf 520 MB 0 B 0 Grafana 486 MB 0 B 396 k mealiev1 452 MB 0 B 37.5 M UptimeKuma 440 MB 0 B 24.8 k MariaDB 407 MB 0 B 2.51 k scrutiny 404 MB 67.8 MB 210 k Plex-Media-Server 351 MB 339 kB 27.5 M Actual 258 MB 0 B 1.28 k SFTPGo 231 MB 0 B 618 k QDirStat 184 MB 1.71 kB 23.1 k tautulli 146 MB 23.5 kB 20.1 M PuTTY 131 MB 3.17 kB 46.2 k goaccess 77.3 MB 27.4 kB 4.64 k duckdns 34.5 MB 21.8 kB 607 k Dozzle 20.0 MB 0 B 1.81 k Docker-WebUI 17.5 MB 0 B 645 Terraform-HTTP-Backend 17.0 MB 12.3 kB 116 NoIp 16.1 MB 329 B 2.51 M Total size 42.0 GB 3.32 GB 284 M Containers Size.docx Edited January 21, 20251 yr by Yannoviche
January 21, 20251 yr Author 9 hours ago, Yannoviche said: I have a warning about the size of the hardware where the vm is located. Sorry I meant vDisk. I had a quick look at one of them. But I haven't focus on it yet. But I don't really know what I'm looking for in the log. I don't have much experience yet. A bit of help learning how to diagnose the log will be appreciated.
January 21, 20251 yr Community Expert Often a container log will end with some lines about why it failed or is exiting
January 23, 20251 yr Author Because of the high number of failures to start of the apps, would this indicate that it is rather a global failure instead of a specific app failure? Before the update, the apps the loading with issues and I have even reinstalled all of them... Edited January 23, 20251 yr by Yannoviche
January 23, 20251 yr Community Expert 4 minutes ago, Yannoviche said: I have even reinstalled all of them... Did you delete and recreate docker.img before reinstalling? https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications
January 23, 20251 yr Author 6 hours ago, trurl said: Did you delete and recreate docker.img before reinstalling? Yes I did. And that's when I increased vDisk to 200GB.
January 23, 20251 yr Community Expert On 1/21/2025 at 9:28 AM, trurl said: Your diagnostics shows you were using 34G, which is more than default 20G size, but might be reasonable if you have a lot of containers. If it normally uses that much, and it isn't growing, then you might consider 40-50G.
January 23, 20251 yr Author When I run the Fix common Problems plug I get the following issue (among other issues) : /var/log is getting full (currently 66 % used) --------- Either your server has an extremely long uptime, or your syslog could be potentially being spammed with error messages. A reboot of your server will at least temporarily solve this problem, but ideally you should seek assistance in the forums and post your diagnostic. Following a link to the /var/log issue give me a post by Squid explaining that Nerdpack could be the issue. When I previously run the Fix common Problems it was saying that for Unraid OS 7, I need to remove Nerdpack which I did but I haven't rebooted the server yet. So I will do it now, run again the Fix Common Problems and post the result. Edited January 23, 20251 yr by Yannoviche
January 23, 20251 yr Author Here is the latest diagnostic. But it seems like the problem is persistent. kingfisher-diagnostics-20250123-2306.zip
January 23, 20251 yr Community Expert Your appdata is configured to only go to temp_cache, and it has Minimum Free 390G, which is less space than temp_cache has. So syslog is filling with these: Jan 23 22:54:44 Kingfisher shfs: share cache full Jan 23 22:54:44 Kingfisher shfs: assign_disk: /appdata/tautulli/.TEST (28) No space left on device ... Similar for your system share, which is where docker.img is configured to go. Even if you reduce the Minimum Free settings for those shares, temp_cache is pretty full. Some of that is needlessly large docker.img, but probably more things need to be fixed. Here is all the shares with files on temp_cache: appdata shareUseCache="only" # Share exists on temp_cache, disk1 B-----s shareUseCache="only" # Share exists on temp_cache C-----------s shareUseCache="only" # Share exists on temp_cache D---2 shareUseCache="yes" # Share exists on temp_cache, disk1 domains shareUseCache="only" # Share exists on temp_cache d-------s shareUseCache="yes" # Share exists on temp_cache isos shareUseCache="only" # Share exists on temp_cache system shareUseCache="only" # Share exists on temp_cache T-------------r shareUseCache="only" # Share exists on temp_cache Those that say "yes" would be moved to the array, but those that say only won't be and can't go anywhere else. Looks like you have 2 other pools barely used. No shares are even configured to use tmp pool. Why do you need 3 pools each 4TB in size anyway?
January 24, 20251 yr Community Expert Disable Docker and VM Manager in Settings and leave them disabled until we can clean up this mess. And Uninstall the Mover Tuning plugin. Then go to MAIN - Array Operations, click Move, wait for it to finish. Then post new diagnostics.
January 24, 20251 yr Author For the 4TB, I got one call Home where all the users data are, I've got one to set up as a parity for the user home, one called temp_cache for cache and another 1TB, I want to install for another cache as well. The mover is running. I will post the diagnostic avec it is done. I probably need help to set up my server correctly. Edited January 24, 20251 yr by Yannoviche
January 24, 20251 yr Author 1 hour ago, trurl said: Your appdata is configured to only go to temp_cache, and it has Minimum Free 390G, which is less space than temp_cache has. So syslog is filling with these: Jan 23 22:54:44 Kingfisher shfs: share cache full Jan 23 22:54:44 Kingfisher shfs: assign_disk: /appdata/tautulli/.TEST (28) No space left on device ... appdata shareUseCache="only" # Share exists on temp_cache, disk1 B-----s shareUseCache="only" # Share exists on temp_cache C-----------s shareUseCache="only" # Share exists on temp_cache D---2 shareUseCache="yes" # Share exists on temp_cache, disk1 domains shareUseCache="only" # Share exists on temp_cache d-------s shareUseCache="yes" # Share exists on temp_cache isos shareUseCache="only" # Share exists on temp_cache system shareUseCache="only" # Share exists on temp_cache T-------------r shareUseCache="only" # Share exists on temp_cache Those that say "yes" would be moved to the array, but those that say only won't be and can't go anywhere else. The ones that say Only are shares which supposed to have data that will be often moving like backups for example.
January 24, 20251 yr Community Expert 52 minutes ago, Yannoviche said: The ones that say Only are shares which supposed to have data that will be often moving like backups for example. Mover won't move "only" shares.
January 24, 20251 yr Author 5 hours ago, trurl said: Disable Docker and VM Manager in Settings and leave them disabled until we can clean up this mess. And Uninstall the Mover Tuning plugin. Then go to MAIN - Array Operations, click Move, wait for it to finish. Then post new diagnostics. Here is the diagnostic after running mover. kingfisher-diagnostics-20250124-0543.zip
January 24, 20251 yr Community Expert Solution These shares (anonymized) still have files where they probably shouldn't still be after running mover, so you probably have them misconfigured: appdata shareUseCache="only" # Share exists on temp_cache, disk1 d-------s shareUseCache="yes" # Share exists on temp_cache, disk1 Y-----s shareUseCache="yes" # Share exists on home, disk1 appdata should be Primary:temp_cache; Secondary:array; Mover action:array->temp_cache d-------s should be Primary:temp_cache; Secondary:array; Mover action:temp_cache->array Y-----s should be Primary:home; Secondary:array; Mover action:home->array Make those changes, run mover again, post new diagnostics
January 24, 20251 yr Author 2 hours ago, trurl said: These shares (anonymized) still have files where they probably shouldn't still be after running mover, so you probably have them misconfigured: appdata shareUseCache="only" # Share exists on temp_cache, disk1 d-------s shareUseCache="yes" # Share exists on temp_cache, disk1 Y-----s shareUseCache="yes" # Share exists on home, disk1 appdata should be Primary:temp_cache; Secondary:array; Mover action:array->temp_cache d-------s should be Primary:temp_cache; Secondary:array; Mover action:temp_cache->array Y-----s should be Primary:home; Secondary:array; Mover action:home->array Make those changes, run mover again, post new diagnostics
January 25, 20251 yr Author 11 hours ago, trurl said: These shares (anonymized) still have files where they probably shouldn't still be after running mover, so you probably have them misconfigured: appdata shareUseCache="only" # Share exists on temp_cache, disk1 d-------s shareUseCache="yes" # Share exists on temp_cache, disk1 Y-----s shareUseCache="yes" # Share exists on home, disk1 appdata should be Primary:temp_cache; Secondary:array; Mover action:array->temp_cache d-------s should be Primary:temp_cache; Secondary:array; Mover action:temp_cache->array Y-----s should be Primary:home; Secondary:array; Mover action:home->array Make those changes, run mover again, post new diagnostics Hi @trurl, This se resolved the issue. It is now working. I have try to run a few apps in docker and they work fine. Would you explain what I did wrong in my setup? Is there anything else that you see I need to fix in my server?
January 25, 20251 yr Author 7 hours ago, trurl said: Post new Diagnostics Here is the latest diagnostic. kingfisher-diagnostics-20250125-0859.zip
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.