Hi!

I need to replace my cache drive but first i have to eliminate the current one, I've started by disabling docker and VMs, then changed all shares to use array only and stopped the array, then manually run Mover.

 

At first around 115 GB where stored in cache and after executed mover the first time around 60GB still stored, Mover Tuning was not installed until today after several manual runs failed but same results.

 

corellia-diagnostics-20250512-1457.zip

Edited May 12, 20251 yr by surferjsmc

Uninstall the mover tuning plugin, enable mover logging, run the mover, post new diags.

New diags, Thx Jorgecorellia-diagnostics-20250512-1537.zip

1 hour ago, surferjsmc said:

then changed all shares to use array only and stopped the array, then manually run Mover.

Mover will ignore any share that does not have both Primary and Secondary storage set.

18 minutes ago, itimpi said:

Mover will ignore any share that does not have both Primary and Secondary storage set.

This is the only way you can specify a Mover action. Without Mover action, mover skips the share.

The only way I see to set a secondary storage location is by changing the primary to "cache," which doesn't seem logical to me, since my goal is to eliminate the cache drive.

1 hour ago, surferjsmc said:

The only way I see to set a secondary storage location is by changing the primary to "cache," which doesn't seem logical to me, since my goal is to eliminate the cache drive.

You have to have a secondary storage set so you can control the mover action "Primary -> Secondary" or "Secondary -> Primary"
 

 

vs

 

 

Keep in mind, mover depends on there being both because otherwise if there is only a primary there would be no reason for mover to try to move something that should only ever be on a single pool at all times.

Without a secondary storage location, files should only ever be written to the primary storage location. There would never be files on any other pool/array for mover to even be concerned with.

Edited May 12, 20251 yr by MowMdown

55 minutes ago, surferjsmc said:

he only way I see to set a secondary storage location is by changing the primary to "cache," which doesn't seem logical to me, since my goal is to eliminate the cache drive.

You have to do this initially (with mover direction set to be cache->array) to get mover to take any action.  After you have then run mover and all the files have been moved to the array you can change the share so that the Array is Primary, and the Secondary is None.

 

I guess in theory you could also set Array to be Primary; Cache to be secondary and the mover direction to be Cache->Array to achieve the same effect although most people would do it the other way around.

Well I've set all the shares that had data to use cache as primary and array as secondary then executed mover and now the cache drive is empty after all files where moved.

 

I'll set everything back to array only, stop the array, delete the cache pool and replace the drive.

 

Thank you all!

 

Don't enable Docker or VM Manager until you get cache going again and get the related shares moved back.

Well after a few weeks I'm facing several issues, docker starts and after i don't know what it fails, here are some screenshot of fix common problems and how i have the pools and shares, obviously is a appdata location issue and I've tried to changed from cache only to cache-array and even revert to just array but i can't find the solution :(

Perhaps i just need to move appdata and system files from the array to the cache?

Also I'm concern about the memory issue, I've replaced my previous hardware and maybe RAM is failing.

corellia-diagnostics-20250604-1130.zip

Edited June 4, 20251 yr by surferjsmc

Leave Docker and VM Manager disabled until everything is moved.

Set each of the "default shares"

https://docs.unraid.net/unraid-os/manual/shares/user-shares/#default-shares

to Primary:cache; Secondary:array; Mover action:array->cache

Run mover, wait for it to complete, post new diagnostics.

Mover is done and here are the diagnostics corellia-diagnostics-20250608-0916.zip

I don’t understand why, if the shares are 22 GB and 54 GB, the cache pool only shows 42 GB used.

Likely to be because the docker.img file is a 'sparse' file so only physically occupies the current used space (although you need to make sure it has room to grow towards the full size you specified) so make sure you have set a sensible Minimum Free Space value for the pool.

Well, I guess now I just need to set both shares to 'cache only' and start Docker, right?

6 hours ago, surferjsmc said:

Well, I guess now I just need to set both shares to 'cache only' and start Docker, right?

Your screenshot show ‘appdata’ still has something on disk1 and disk3 (Could be just empty folders). You do not want to set it to cache only until this is resolved.