stainless_steve

I understand, and already identified the containers that are increasing in size. But I what I don´t understand if that is normal and if the container sizes are reasonable in size. Is it possible to just delete all the logs of the containers somehow?

Can anybody help with this? Container, Writable and Log are slowly getting bigger. I am now standing at 31.8GB, 1.88GB and 2.72 GB. What can I do? homeserver-diagnostics-20251226-1039.zip

I have nearly the same problem and I just checked the container sizes but I don´t know if any of those containers are unreasonably big. I am at 91% of the docker.img which is 35GB big. What container should be smaller in size? thanks

Hi, I wanted to update the Immich Docker Container to the newest Version, as it stopped syncing my photos. When clicking "apply update" it started the update process but after downloading everything (took unusally long) I got the following message: After that I expanded my Docker Image from 30GB to 35GB and after that it worked so far that it said "command executed successfully". But I could see that the Container was not updated. So I tried again, and this time by clicking "update all". The download took even longer and again, nothing happend to the Immich container, but the others were updated. It seems that Immich cannot be updated. Hope somebody can help me. Thanks in advance. homeserver-diagnostics-20250909-1607.zip

Danke euch! Es funktionierte dann nach einem Neustart und ohne laufenden Dockers, dass der Mover das wieder freischaufelt. Habe dann als er fertig war, "balance" ausgeführt und den Mover auf alle 4h gestellt. Heute noch "Scrub" gestartet und jz sollte es laufen. Ich bin relativ neu bei Unraid und auch nicht wahnsinnig versiert in solchen Dingen, bin einfach ein Noob. Ich hab das ganze Ding mit Hilfe von Tutorials aufgebaut um mir einen Medienserver zu basteln. Von Filesystems hab ich leider keine Ahnung. Hatte in der Vergangenheit schon Probleme mit dem Cache, die ich nicht lösen konnte. Ich checke es leider einfach nicht zum Teil, da mir Hintergrundwissen fehlt, was hier im Forum oft vorausgesetzt wird, versuche mich aber immer so gut als möglich einzulesen. Habe dann beim letzten mal den Rechner komplett neu aufgesetzt und nochmal von vorne gestartet. Sollte man Balance und Scrub automatisiert laufen lassen, bspw. 1 mal im Monat?

Were you able to solve this? I have the same problem and cannot find anything that shows how to do this correctly ( or at all)...

Hallo, gerade habe ich nachgesehen und festgestellt dass der Mover seit 12h läuft aber mein Cache noch immer voll ist und sich anscheinend einfach nichts tut. Was kann ich hier machen? Wieso wird der Cache nicht leer? Bis vor ein paar Tagen lief es noch einwandfrei, vorgestern habe ich Sonarr installiert, sonst eigentlich nichts geändert. Ich hoffe es kann mir wer helfen, danke. homeserver-diagnostics-20241009-1507.zip

Danke für deine Antwort! Hatte gar nicht am Schrima dass ich das installiert habe... D.h. es hat womöglich mein klicken auf "resume" gar nicht angenommen? Der Parity Sync läuft jetzt und die nächste Mover-Aktion steht am Sonnatg an, das sollte sich also ausgehen.

Hallo zusammen, ich habe eine neue Parity Disk installiert, welche nun bei 41% Paritäts-Check steht. Ich denke dass dieser in der Nacht durch den Mover unterbrochen wurde. Soweit ich das sehen kann läuft dieser angeblich noch, nur kann ich mir das nicht vorstellen, das wären nun schon in etwa 18h… “resume“ hilft nicht den Check fortzusetzen. ich hoffe es kann mir hier jemand weiterhelfen, wie ich hier rauskomme. Danke schonmal homeserver-diagnostics-20240924-2139.zip

Thanks! Maybe I followed I guide and I can´t remember. Can I just change it to vxfs or vbtrfs? Would that be better? All in all it comes down to 2 questions: Will i run into troubles if I reach the 100% and if so, what can I do to prevent this? I am now at 90% and lost. Can I change any settings that will expand the available space to more than 1TB? Or do I have to set my server from scratch again? I am a noob and still wrapping my head around this.

@JonathanM oh so you mean, that the setting directory (did not change this, seems to be default) made it that nothing is stored in docker.img but in the folder "installed"? But if so, shouldn´t be the maximum all that free space that is available on all included disks on the array instead of 1TB? And can or should it be changed to a different setting? As I understand it, everything I do in a docker container would be stored in "appdata" like in my screenshot under "Default appdata storage location" as long as I don´t change the path mapping (which I have done).

Thank you both for your answers. I have built a completely passively cooled system with only SSDs. As the first server I build was with a cache drive, but I had so many troubles that I could not solve, I started from scratch. Initially I wanted to use that cache but then decided to don´t use it, as I only have SSDs and therefore no spinning up and down of hard drives. But that is the reason, I still have some data on cache and the array. I decided to leave is as it is as it was working for the time being and with all SSDs there should be no performance issue. System is set to use all disks appdata is set to only use cache

This is what I am trying to tell you in my first post: The docker.img is small as it should be according to the "file explorer" (don´t know the proper name): If I have wrongly mapped the data storage into the containers itself, from my understanding the docker image itself (or atleast the "system" share) should grow in size. But it doesn´t do that. same as mine... As far as I know, I have mapped the downloads and so an correctly (tried to show you with the screenshots) out of the docker image to the appropriate paths on the share "data". When I hover over the 79% ( meanwhile it is already 80%) you can see that it is 737GB: I am not referring to the to the drive, but coincidentally it is 1TB. The docker.img is not 1TB, so how could it be INSIDE? I hope you can see where my confusion comes from...

I think/thought that I will run into a problem, when Docker reaches 100% (see first post). It seems to fill up when downloading. I am at 80% (737GB) but I have 4.5 TB free space left on the array. I am unsure what will happen?! I thought I will run into troubles as I did when previously my cache was full. It was also docker, but then I started from scratch and it was just quite some work to get everything back running as I like...

Please excuse me, but I am still quite new to Unraid and I am trying to learn. The only container that could build up this much, is deluge I think. But as you can see in the screenshot, data should be stored outside the image. But this is set up following specific YT guides... So config is in appdata on the cache and all the downloads should be on the data share. Could it have something to do with the settings in deluge? I don´t see where, because as I understand it, "torrents" is located under /mnt/user/data/... and not under config as I could be, I assume, if it is like default and this post in the FAQ suggests: Besides hosting my movies with jellyfin, I do not much with my server. appdata is the only one of my shares that is on the cache, and it takes up 1.27GB... Can you see and tell me what setting is wrong and should be changed in your opinion? thanks in advance!