Moerky

Having done that which worked like a charm I have the impression every time I login to Unraid I see the two 6TB drives of the array spinned up which shouldn't be the case as they're normally not used. Especially not being at home ... I'm pretty sure there is a way how I could monitor this or to see why this could be the case? Thank you for any help on this topic.

I have all my docker compose files running on my cache drive and now it gets quite full (950GB/1 TB). What I can see is the the docker.img file is not so much used as I initially thought with reserving 500GB for it. See the screenshot. I asked Perplexity how to save some space on that drive and it came with quite complex instructions, is there an easy way / strategy on reducing the drive / image? I already did a system prune and the state is now Thanks for advices / strategies.

I've been using UNRAID for a while now and I am fully convinced. I use an Array with a 6TB Parity Drive and another 6TB drive and a 1TB SSD cache which is not part of the array. All of my VM's and Docker Containers reside on this cache for fast execution. My 6TB array space is mainly used for multimedia stuff (pictures & videos) and backup of the data of my dockers / timemachine etc. They are spinned down most of the time to save energy. Now the 6 TB space runs down and I though of giving up the parity drive and use the 2x6TB as is as a pool as it's not used that often. Even if one of the drive breaks suddenly then I could use one of the recent backups as the data on these drives don't change that frequently, apart from the backups which is anyhow redundant. How would I best tacle this to not have to copy data back and forth when breaking up the array? Anything that speaks against such an idea? Thank you for your advise!

@bmartino1 sorry to be so late with my Thank you very much for this fast solutiont

@mguttTo avoid having a named list of several directories and each directory versioned separately I wanted to use a directory where softlinks point to the directories, i.e. # backup source to destination backup_jobs=( # source # destination "/mnt/user/backup-links/" "/mnt/disks/EXTERNAL_3TB_A/tower-backup" whereas in the backup-links directory I have softlinks to all the directories I'd like to backup root@Tower:/mnt/user/backup-links# ll lrwxrwxrwx 1 root root 18 Mar 16 18:17 appdata -> /mnt/cache/appdata/ lrwxrwxrwx 1 root root 16 Mar 16 18:18 archiv -> /mnt/user/archiv/ lrwxrwxrwx 1 root root 5 Mar 16 18:17 boot -> /boot/ lrwxrwxrwx 1 root root 23 Mar 19 18:01 docker-volumes -> /var/lib/docker/volumes/ lrwxrwxrwx 1 root root 17 Mar 16 18:18 domains -> /mnt/user/domains/ lrwxrwxrwx 1 root root 18 Mar 16 18:18 download -> /mnt/user/download/ drwxrwxrwx 2 root root 53 Mar 16 18:19 multimedia/ lrwxrwxrwx 1 root root 18 Mar 19 18:01 pdfocred -> /mnt/user/pdfocred/ which unfortunately creates root@Tower:/mnt/disks/EXTERNAL_3TB_A/tower-backup/20250319_230326# ll total 32 -rw------- 1 root root 1300 Mar 19 23:03 20250319_230326.log lrwxrwxrwx 2 root root 18 Mar 16 18:17 appdata -> /mnt/cache/appdata/ lrwxrwxrwx 2 root root 16 Mar 16 18:18 archiv -> /mnt/user/archiv/ lrwxrwxrwx 2 root root 5 Mar 16 18:17 boot -> /boot/ lrwxrwxrwx 2 root root 23 Mar 19 18:01 docker-volumes -> /var/lib/docker/volumes/ lrwxrwxrwx 2 root root 17 Mar 16 18:18 domains -> /mnt/user/domains/ lrwxrwxrwx 2 root root 18 Mar 16 18:18 download -> /mnt/user/download/ drwxrwxrwx 1 root root 46 Mar 16 18:19 multimedia/ lrwxrwxrwx 2 root root 18 Mar 19 18:01 pdfocred -> /mnt/user/pdfocred/ is there any way to avoid / work around this?

Hello im using one of the shell scripts to backup data from my unraid server. Instead of naming each directory to backup within the script i’d rather like to use one directory which contains softlinks to the directories to backup. Where is the best place to put that? I placed them in /mnt/backup-links which seemed to be not the best idea. Thank you for help!

Thank you. The stick was repaired and after that it worked again. Must’ve been some minor errors. But now I know how to proceed on the future. Thanks!

Suddenly my USB drive seemed to have issues and I didn't find proper instruction on what to do. The disk log says the file system is corrupted. UNRAID complains the key file is not there. I could somehow repair it but no files can be seen anymore. What is the best way to handle it? I have a recent backup of the stick - shall I copy that to a new one? anything that needs to be considered?

I've done as supposed by you. But I don't get rid of the array files for app data. Secondary storage set to Array Mover set to array > cache temporarily disable Docker and VM services Invoked mover Removed secondary storage option Leaving all docker and VM setting disabled Running Fix-Common-Problems > still get the error for Share appdata set to cache-only, but files / folders exist on the array Diagnostics attached. Shall I manually delete these files? Where do they reside? I'd like continue with my setup of other containers but want to sort this out first.

Here again...

Ok, that did work now and my array is spinning down correctly and the server consuming 50% less power than before! Very cool as I wanted this since months. What I still have is the following errors when executing the fix common problems. Is there a way I can get rid of these too?

How could I configure them wrong? I set everything to Cache which can be seen on my last config post - nothing changed apart from that I took everything offline - Dockers, Docker-Compose, VMs.... Shouldn't there be an error message at least if the mover can't run properly?

Tried to follow the instructions but when clicking on Move on the Main Tab nothing happens. Normally I'd see a message that the mover is running.

Here you are

Thank you! Done! But when looking at the read/writes it's still continuously accessing the array - about 150 writes/sec.