4 minutes ago, trurl said:

Mover does work if things are configured correctly. I see you have the mover tuning plugin installed. Good idea to remove that at least until you have things working correctly and moving normally. I personally don't use that and never saw a need for it if you have things setup well.

None of your user shares are currently configured to be moved. That doesn't necessarily mean they didn't have any files on cache.

How did you do this? Are you sure everything was off cache?

i just used the shares settings to change storage settings to array (I can't replicate it right now as there is no cache and everything has defaulted to array). Sorry it's been a long while since i looked at it so can't recall exactly why or howI changed every setting, iirc I was trying to diagnose why mover wasn't working, and seeing if a change to what was on the cache would start it working, so I experimented with moving things off the cache to see if mover would work, it didn't. In the end, i just gave up trying to get mover to work and set all shares to array - I haven't thought about it in a long time tbh. I had sort of come to the conclusion that i would need to rebuild to get it working, and so just went with it working without a cache drive doing anything - and future me can rebuild when I am motivated.

I installed mover tuner as an attempt to try and get the mover to work. It didn't make any difference. I have removed the plugin for now as directed.

I will install the new SSD and get it setup as the cache and come back to you. Thanks for helping.

4 minutes ago, sihorrocks said:

i just used the shares settings to change storage settings to array

That would not move anything, it would just mean any new files went to the array.

6 minutes ago, sihorrocks said:

I experimented with moving things off the cache

Still trying to understand this. How did you move things off cache?

If things were working with cache, then I think it's likely that some things needed for it to work was on cache.

If you are willing to start over with Dockers/VMs, we can forget about the failed cache and work on getting things setup with a new drive and configured correctly.

But I need to get some sleep so I will check back tomorrow.

Great thanks - I have loaded the new SSD. Its setup as cache and formatted to btfrs. Very happy to rebuild docker apps and VM. Let me know when you're around to help.

"Still trying to understand this. How did you move things off cache?" I may not be explaining myself using the correct language, I changed the settings for my shares, such as 'downloads', 'appdata', 'plugins' and 'domains' from cache to array. That's all. I manually moved media files off of cache to other drives.

7 hours ago, sihorrocks said:

manually moved media files off of cache to other drives

This is the part I'm trying to understand. How did you access cache and other drives?

7 hours ago, sihorrocks said:

loaded the new SSD. Its setup as cache and formatted to btfrs

Post new Diagnostics.

Currently on mobile for a while so won't be able to proceed until I can look at Diagnostics.

3 minutes ago, trurl said:

How did you access cache and other drives?

This may seem obvious to you but I can think of several different ways to do that.

You seem to think cache wasn't used and was actually empty when it failed. I think some stuff was still running from cache until it failed.

11 hours ago, trurl said:

your docker.cfg has

DOCKER_IMAGE_FILE="/mnt/user/docker.img"

This path is at the root of User Shares, so not actually in any user share.

Wondering where this is, if it still exists.

What do you get from command line with this?

ls /mnt/user

Apologies on New Zealand time, so we might have difficulty connecting at the same time! happy to try a discord server if that would be better?
This is the part I'm trying to understand. How did you access cache and other drives?
I just navigated into the cache, then moved changed the disk location of the files as per screenie below - or copied and pasted to the folder on the relevant disk was faster I think

So just change from 'cache' to 'disk X'

This may seem obvious to you but I can think of several different ways to do that.

Same as above, used the browse option in the gui via main to naviaget into the folders then move or copy/paste - I think it might be a plugin (i did check) to give you folder style access like this (can't recall)

You seem to think cache wasn't used and was actually empty when it failed. I think some stuff was still running from cache until it failed.
You're the expert not me!

What do you get from command line with this?
root@Tower:~# ls /mt/user

ls: cannot access '/mt/user': No such file or directory

Post new Diagnostics.

New diagnostics attached.
Thanks heaps!

tower-diagnostics-20260110-1802.zip

15 hours ago, trurl said:

Wondering where this is, if it still exists.

What do you get from command line with this?

ls /mnt/user

Here's the new main with cache working

So you are using the built-in File Manager. That is the simplest and often the best since it prevents you from making mistakes. I was unsure if you knew about it (many don't seem to, it's a new feature) since you didn't know how to see if your HA vdisk was still there.

8 hours ago, sihorrocks said:

root@Tower:~# ls /mt/user

ls: cannot access '/mt/user': No such file or directory

Try again. Better to copy/paste the command line I gave instead of making a typo.

Anyway, the purpose of my command line in that case was to see if docker.img still existed. You can see for yourself by browsing to the top of /mnt/user.

And you can see if your HA vdisk is there by browsing to its path as shown in your earlier "Execution Error" screenshot.

8 hours ago, sihorrocks said:

on New Zealand time

I spent 3 weeks there in 2006

8 hours ago, sihorrocks said:

Here's the new main with cache working

That looks good and a good place to start. Cache empty and no (existing) shares currently configured to use it. You have some .cfg files for nonexistent shares cluttering your diagnostics though. You can clean that up by going to Shares - User Shares and clicking the CLEAN UP button.

Docker and VM Manager still disabled. Leave them that way for now. We will make some changes to your docker.cfg before starting those.

Since you know how to use File Manager, give me screenshots that show

• if docker.img exists ( at /mnt/user )

• if your HA vdisk exists ( at /mnt/user/domains/Home Assistant )

• the contents of appdata (at /mnt/user/appdata )

Also, the contents of your docker templates at /boot/config/plugins/dockerMan/templates-user

1 minute ago, trurl said:

Also, the contents of your docker templates at /boot/config/plugins/dockerMan/templates-user

Maybe not so obvious how to get there. Go to Main - Boot Device, click on the "arrow-box" icon to the left of flash to begin browsing the flash drive (/boot).

12 hours ago, trurl said:

So you are using the built-in File Manager. That is the simplest and often the best since it prevents you from making mistakes. I was unsure if you knew about it (many don't seem to, it's a new feature) since you didn't know how to see if your HA vdisk was still there.

Try again. Better to copy/paste the command line I gave instead of making a typo.

Oops

Movies/ Music/ admin/ appdata/ config/ data/ domains/ isos/ log/ logs/ metadata/ plugins/ root/ system/

That looks good and a good place to start. Cache empty and no (existing) shares currently configured to use it. You have some .cfg files for nonexistent shares cluttering your diagnostics though. You can clean that up by going to Shares - User Shares and clicking the CLEAN UP button.

Done. Found seven shares to remove, none were actually removed from the GUI though?

Since you know how to use File Manager, give me screenshots that show

• if docker.img exists ( at /mnt/user )

Couldn't see the file in /user

• if your HA vdisk exists ( at /mnt/user/domains/Home Assistant )

Domains looks empty?

• the contents of appdata (at /mnt/user/appdata )

  HA_inabox is in here, to note, I just followed the setup instructions from spaceinvader
  

12 hours ago, trurl said:

Also, the contents of your docker templates at /boot/config/plugins/dockerMan/templates-user

1 hour ago, sihorrocks said:

Found seven shares to remove, none were actually removed from the GUI though?

The webUI only shows shares that actually exist. But you had .cfg files for shares that didn't exist. Those were removed.

1 hour ago, sihorrocks said:

• if docker.img exists ( at /mnt/user )

Couldn't see the file in /user

And it wasn't seen in the ls command either so it's gone. Probably was on cache where it belonged but gone now with the old cache. Just as well because it needed to be recreated anyway.

1 hour ago, sihorrocks said:

• if your HA vdisk exists ( at /mnt/user/domains/Home Assistant )

Domains looks empty?

Your HA vdisk and the folder it was in are gone, probably on the old cache where it belonged. The empty domains user share must be on the array, we will move it to cache.

1 hour ago, sihorrocks said:

the contents of appdata (at /mnt/user/appdata )

HA_inabox is in here, to note, I just followed the setup instructions from spaceinvader

All of that belongs on cache also. The appdata is the most important thing for getting your containers going again. They will have to be moved to new cache.

Do you know if that is all of them, or were some lost on old cache?

1 hour ago, sihorrocks said:

your docker templates

That is the other thing needed to get your dockers going again, they have all the settings made in the webUI when the each container was created or edited. These will let you easily reinstall those containers exactly as they were.

Your system share is on 2 different disks on the array. Probably libvirt.img for VM Manager, but that is a single file. Don't know if it is on both disks, or maybe there is actually a docker.img somewhere in there. It does belong in system instead of the path you had set in docker.cfg.

Show me what is in disk3/system and disk4/system

29 minutes ago, trurl said:

Your system share is on 2 different disks on the array. Probably libvirt.img for VM Manager, but that is a single file. Don't know if it is on both disks, or maybe there is actually a docker.img somewhere in there. It does belong in system instead of the path you had set in docker.cfg.

Show me what is in disk3/system and disk4/system

disk3

disk4

These are the other apps installed, but not disabled as not on the docker?

Those other apps are all plugins, as you can see tailscale needs updated.

tailscale.plg - 2025.12.17.0420  (Update available: 2026.01.08.0308)

Looks like these have been replaced so you should remove and reinstall them.

dynamix.s3.sleep.plg - 2023.03.23  (Unknown to Community Applications)
unbalance.plg - v2021.04.21  (Unknown to Community Applications)

We will delete docker since it needs to be recreated.

Let's take a look inside both of these, disk3/system/libvirt and disk4/system/libvirt.

1 hour ago, trurl said:

Those other apps are all plugins, as you can see tailscale needs updated.

tailscale.plg - 2025.12.17.0420  (Update available: 2026.01.08.0308)

Looks like these have been replaced so you should remove and reinstall them.

dynamix.s3.sleep.plg - 2023.03.23  (Unknown to Community Applications)
unbalance.plg - v2021.04.21  (Unknown to Community Applications)

We will delete docker since it needs to be recreated.

Let's take a look inside both of these, disk3/system/libvirt and disk4/system/libvirt.

disk3 looks empty

disk4 .img is in disk4

Plugins removed.

Delete system folder from disk3.

Set appdata, domains, system shares to

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

Main-Array Operation

Move

Wait for it to complete, then post new Diagnostics

Delete system folder from disk3.

Done

Set appdata, domains, system shares to Primary:cache; Secondary:array; Mover action:array->cache
Done

Running mover. Will post diags when its complete. Back at work so hours all over at the moment.