The story:

I wanted to replace my 2 cache drives with a single one.

I tried first using the mover to get all the data onto the array. This did not work. Unfortunately most of the instructions I found online said something about having cache set to yes (which is not a setting in 6.12). I so I set primary to cache, secondary to array, and then cache to array for the move bit.

Tried the mover again, nothing.

I then installed the mover helper thing in apps (was not installed previously apparently, as it wasn't in the plugins tab until I installed it).

Tried the mover again, still nothing.
I opened console and typed 'mover start'. It started and immediately finished (in under a second).

I then decided, maybe the data had moved (despite showing 160gb used on the cache) but it was just keeping a copy on the cache as well.

So I set the shares to all be array only (swapped primary to array (secondary was then defaulted to be empty). I restarted the array, and docker still worked. So I thought, I must be right about the shares having been copied.

I stopped the array, and unassigned the cache drives. Then restarted the array (clicked the button to remove cache first (figured I had already tested the theory that the data was on the array and everything is working)).

Restarted the array to confirm that everything was working one last time before pulled out the drives and installing the new one.

To my surprise and panic, all my VMs and dockers are not appearing under VMs and Docker...

I am a bit upset at my stupidity, but also confused about why it appeared to work with the shares on the array only.

 

Anyway. I am hoping there is a way to re-add my old dockers from the image that is still on the cache drives

tldr;

I am an idiot and removed my cache drives.

Now my docker containers are all missing.

I still have the old docker image.

How do I re-add this to current docker?

Edited May 30, 20242 yr by [email protected]

This is the settings I mentioned toward the start:

 

Update:

I reverted the change to the system share > I set primary to cache, secondary to array, and then cache to array for the move bit.

It did nothing. So I turned the server off in hopelessness.

A little while later, I was reading this > https://forums.unraid.net/topic/36647-official-guide-restoring-your-docker-applications-in-a-new-image-file/

And thought, I'll give this a go.

Turned on server. Docker containers are all back.

 

So now my question is. What on earth is going on?!

How do I safely change the drives without risking a data/functionality loss.

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=511923

 

 

48 minutes ago, JorgeB said:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=511923

 

 

Stop all running Dockers/VMs - Done.

Settings -> VM Manager: disable VMs and click apply - Done.

Settings -> Docker: disable Docker and click apply - Done.

For v6.12.0 or newer: Click on all shares that are using the pool you want to empty and change them to have the pool as primary storage, array as secondary storage and mover action set to move from pool to array - Done.

Check that there's enough free space on the array and invoke the mover by clicking "Move Now" on the Main page - Doesn't work. "Move" button (on main page), "Move Now" (in plugin itself) and "mover start" (in console) do nothing. Doesn't say "In progress" or anything, just flashes and is immediately able to be pushed again. Leaving 160gb on the cache pool...

When the mover finishes check that your cache is empty (any files on the cache root will not be moved as they are not part of any share) - Mover never starts, or perhaps finishes immediately without doing anything.

Edited May 30, 20242 yr by [email protected]

18 minutes ago, [email protected] said:

Check that there's enough free space on the array and invoke the mover by clicking "Move Now" on the Main page - Doesn't work. "Move" button (on main page), "Move Now" (in plugin itself) and "mover start" (in console) do nothing. Doesn't say "In progress" or anything, just flashes and is immediately able to be pushed again. Leaving 160gb on the cache pool...

Enable mover logging, run the mover, post the diagnostics.

14 minutes ago, JorgeB said:

Enable mover logging, run the mover, post the diagnostics.

tower-diagnostics-20240530-1941.zip

Try removing the Mover Tuning plugin and then trying again. 

Wondering if I should now remove or reinstall the mover plugin.
Also noted these setting in the plugin:

Roger. Will try that now.

7 minutes ago, itimpi said:

Try removing the Mover Tuning plugin and then trying again. 

It seems to have started. According to the syslog at least.
Though its only going at about 1 Mb per second. Guess its hitting a tonne of little files or something?

 

(will mark your response as solution once I confirm its not doing something silly again).

Edited May 30, 20242 yr by [email protected]

its moving thumbnails from plex. Might explain the speed I think.
Guess it will start speeding up when it starts hitting larger files. Here's hoping!

Edited May 30, 20242 yr by [email protected]

Just now, [email protected] said:

It seems to have started. According to the syslog at least.
Though its only going at about 1 Mb per second. Guess its hitting a tonne of little files or something?

It is always possible to do the move manually using something like the Dynamix File Manager plugin which is faster as mover does a few checks before moving files for which the overhead becomes noticeable when there are lost of small ones.    However slightly more prone to the user not getting it right.

 

Any idea what all these red bits are in the syslog?
 

Guessing its trying to copy an empty directory or something?

Mover finished. Still has 110Gb on the cache pool for some reason...

File exists was the issue. So renamed the one on the array and it appears to be moving the 100gb image now.

The remaining 10Gb is useless old stuff anyway. So as long as my docker and VMs actually carry over this time. We are done here.