stainless_steve

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!

Ok thanks. Unfortunately I don't understand this. Is this something I can change and eliminate this limitation?

I always thought I understood how the on the dashboard the system overview is to read or at least did not give it much thought. But now I have troubles as my understanding seems to be wrong. As you can see I have 64GB of RAM and around 5% are used, which should be around 3.2GB. I also think, that from the FLASH drive´s 16GB 4% are used. Where is the maximum size of 128GB coming from? what determines the maximum size of the Log ? and most importantly: why is the docker at 79% (732GB)? I checked and the docker.img file is just 21.5GB big and I have plenty of space available. It seems that the maximum is about 1TB but where does it referre to? It seems I am running out of spce and I don´t know why. Can somebody explain and help me please? Thank you homeserver-diagnostics-20240415-2053.zip

yes, but as you can see in the picture in my previous post, it just says under last modified "5 years ago". This all I can see, and I don´t know how to delete only the old version, if I only see this one file. The only option is, from what I can see is, that I can choose to delete if I click on "cache" or "disk3". I suppose it then deletes the cache or the disk3 version. But I don´t see more information

OK maybe I understand it now. You mean that some file exist on the cache and the array? When I click through, I see that most of the files that are on cache and disk3 are orange. And as I understand it those are duplicates and you mean a I should dele the older one of both? And if so, how do I find out which one is the older one?

OK, thanks, found them. Those are in "user/system/docker/installed/btrfs/subvolumes/random name/dev" . Those are lots of folders with a random name. The oldest are on location "disk3", some of them are "cache" and "disk3", some onle "cache". You mean I should delete just the oldest folder (location: disk3)?

please excuse me, but I cannot follow you. I don´t know what files those are. I clicked through all folders, but I cannot identify what files are meant...

homeserver-diagnostics-20240317-0903.zip

I also observed that, after stopping the mover with "mover stop" ( I have no other way to stop it), I cannot stop the array. It gets stuck with "retry unmounting user share(s)".

DId as it is written in the procedure in the FAQ, added the HDD to the pool, unassigned the NVME, started the array. Everything working and I tried to continue with the mover. still nothing happens homeserver-diagnostics-20240315-2229.zip