Hi All,

I was wondering what is the best way to move data from one drive to another, then what setting to use to leave at least 100GB of space on the drives, so they don't get filled up.

Currently my drives looks like below. I'd like to leave 100GB of space on each drive automatically.

Thanks!

Minimum Free won't leave a specified amount of space. What it does instead is specify an amount of space a drive must have before it can be chosen for writing user share data. If a disk has less than Minimum Free, another disk will be chosen when writing user share data. Each user share has a separate Minimum Free setting.

Each pool (such as cache) also has a Minimum Free setting. If the pool has less than Minimum Free, user share writes will go to the Secondary storage (overflow). Each user share has settings for Primary, Secondary, and Mover action.

https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/shares/#share-settings

8 hours ago, trurl said:

Minimum Free won't leave a specified amount of space. What it does instead is specify an amount of space a drive must have before it can be chosen for writing user share data. If a disk has less than Minimum Free, another disk will be chosen when writing user share data. Each user share has a separate Minimum Free setting.

Each pool (such as cache) also has a Minimum Free setting. If the pool has less than Minimum Free, user share writes will go to the Secondary storage (overflow). Each user share has settings for Primary, Secondary, and Mover action.

https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/shares/#share-settings

This is great! Thank you. I understand the idea of the min free space setting. Looks like it has to be done for every share, which I didn't have configured.

Any tips on moving the data? Will the mover handle it if the setting is set? Or do you have to manually do it?

Mover moves data according to the Mover action setting for each user share.

For more specific advice

Attach Diagnostics ZIP to your NEXT post in this thread.

And mover won't move data between array disks. You can use the built-in File Manager in the webUI to move them yourself. Note that nothing can move open files.

17 minutes ago, trurl said:

Mover moves data according to the Mover action setting for each user share.

For more specific advice

Attach Diagnostics ZIP to your NEXT post in this thread.

gemini-diagnostics-20260128-1737.zip

Diagnostic attached.

If you want to move some files from disks 1,2 to disks 3,4, you will have to do that yourself.

Your system share has some files on disk1. Better if these were all on cache. You have to disable Docker and VM Manager in Setttings before you can work with that share. Nothing can move or delete open files.

5 minutes ago, trurl said:

If you want to move some files from disks 1,2 to disks 3,4, you will have to do that yourself.

Your system share has some files on disk1. Better if these were all on cache. You have to disable Docker and VM Manager in Setttings before you can work with that share. Nothing can move or delete open files.

Thanks for the advice! I started to move things manually as you suggested.

Regarding the systems share, is this setting not correct?

I shouldn't have the "Include disk(s) 4" ?

Those Primary, Secondary, Mover action settings are sort of correct, since it says to move any overflow from array to cache. But nothing can move open files, and the files in system share (docker.img, libvirt.img) are always open if Docker or VM Manager is enabled.

I usually recommend these settings for appdata, domains, system shares - Primary:cache, Secondary:none and Exclusive access:yes

Possibly you enabled Docker and/or VM Manager when you didn't have cache, so that share was initially created on disk1.

23 minutes ago, trurl said:

You have to disable Docker and VM Manager in Setttings before you can work with that share. Nothing can move or delete open files.

Probably simpler to use built-in File Manager to take care of that share. You may find instead of moving to cache you might already have a file in both places so you would have to keep the newest one and delete the other and move to cache if necessary.

Just now, trurl said:

Those Primary, Secondary, Mover action settings are sort of correct, since it says to move any overflow from array to cache.

And that share shouldn't overflow anyway since there should only be 2 files on it that are created on cache already.

Thanks for the tips! I will adjust those settings after doing the file moves.

Hi Trurl,

Quick question regarding the move of the files you mentioned. The first time i did it I forgot to disable docker and vm manager. Now it seems the files are on both disk1 and in the cache. Any idea if it should live on both? I think one has a more recent date than the other at this point ....

File in disk1

File on cache...

Thoughts on what to do?

Thanks!

On 1/28/2026 at 6:04 PM, trurl said:

You have to disable Docker and VM Manager in Setttings before you can work with that share. Nothing can move or delete open files.

Delete the oldest and move the most recent to cache if it isn't already, then delete the system folder from disk1.

Done. Thanks!