[Solved] - Mover is trying to move missing "file or directory".

[ThorThe1]

Hello everyone,

If someone can help me out, I would be so thankful!

 

Below is a screen shot of the mover trying to move files/folder from a location that it says does not exist.

I've deactivated docker and VMs.

 

system log

 

Cache

 

Disk 10

 

User

 

Shares

Edited June 20, 2022 by ThorThe1
Issue has been resolved

[ThorThe1]

Hoping to find someone that would help me figure out why the mover is saying there are no files in the location it's trying to move.

[itimpi]

What do you have for the Use Cache setting on the ‘System’ share?   Looks like it may be set to Yes which is NOT what you want.

 

You should attach your system’s diagnostics zip file to your next post so we can see exactly how you have things configured. 

[ThorThe1]

thetower-diagnostics-20220616-2308.zipHere it is. I've tried "YES" and "PREFER" and had the dockers, and vms disabled before invoking the mover and it still never moves the files.

 

[ChatNoir]

4 hours ago, ThorThe1 said:

had the dockers, and vms disabled

the containers and VMs individually or the services in settings ?

[itimpi]

Do you have docker set to use a docker.img file or a folder?   The diagnostics suggest you have it configured to use docker.img but the files that mover is complaining about look like what you get when you select a folder.   Did you have that configured in the past?   It might be best to disable the docker service; delete all the docker related files in the ‘system’ share; and then re-enable docker.    You can then use Apps->Previous Apps to get the binaries for all your docker containers reinstalled with their settings intact and the files will be placed according to the Use Cache settings for the system share.
 

Most the other shares look to have their files where you would expect according to their share settings.    

appdata                           shareUseCache="prefer"  Exists on cache-main
A---y                             shareUseCache="yes"     Exists on disk3
domains                           shareUseCache="prefer"  Exists on v------s, v-----s
G----------s                      shareUseCache="yes"     Exists on disk3, disk4, disk6, disk7, disk9, disk10
g-------e                         shareUseCache="yes"     Exists on disk9
isos                              shareUseCache="prefer"  Exists on cache-main, v-----s
M------------e                    shareUseCache="yes"     Exists on disk1, disk2, disk3, disk4, disk5, disk6, disk7, disk8, disk9, disk10, disk11
n-------d                         shareUseCache="yes"     Exists on disk3, disk4, disk6, disk9
S---------y                       shareUseCache="yes"     Exists on disk3, disk4, disk6, disk7, disk9, disk10, disk11
system                            shareUseCache="yes"     Exists on cache-main, disk10
T----------e                      shareUseCache="yes"     Exists on disk3, disk7, disk9
T----------e (1)                  shareUseCache="yes"     Exists on disk3, disk6, disk7, disk9
T-------------r                   shareUseCache="yes"     Exists on disk1, disk2, disk3, disk4, disk6, disk7, disk8, disk9, disk10, disk11

you seem to have 2 pools related (I think running VMs since they are ‘vm_ssd’ and ‘vm3_ssd’ with the domains share existing on both of them.   Is this intentional?   Since mover never moves files between pools you would have to do this manually if the files are not where you want them.
 

The other one that looks a little odd is the ‘isos’ share which is configured to use the ‘cache-main’ pool but seems to also have files on a ssd pool.   Again you would have to move files manually to tidy this up.   In fact since isos are often only required when initially setting up a VM you may decide to hold them instead on the array to free up pool space.

[ThorThe1]

On 6/17/2022 at 3:27 AM, ChatNoir said:

the containers and VMs individually or the services in settings?

 

It was the services.

[ThorThe1]

On 6/17/2022 at 5:52 AM, itimpi said:

Do you have docker set to use a docker.img file or a folder?   The diagnostics suggest you have it configured to use docker.img but the files that mover is complaining about look like what you get when you select a folder.   Did you have that configured in the past?   It might be best to disable the docker service; delete all the docker related files in the ‘system’ share; and then re-enable docker.    You can then use Apps->Previous Apps to get the binaries for all your docker containers reinstalled with their settings intact and the files will be placed according to the Use Cache settings for the system share.
 

Most the other shares look to have their files where you would expect according to their share settings.    

appdata                           shareUseCache="prefer"  Exists on cache-main
A---y                             shareUseCache="yes"     Exists on disk3
domains                           shareUseCache="prefer"  Exists on v------s, v-----s
G----------s                      shareUseCache="yes"     Exists on disk3, disk4, disk6, disk7, disk9, disk10
g-------e                         shareUseCache="yes"     Exists on disk9
isos                              shareUseCache="prefer"  Exists on cache-main, v-----s
M------------e                    shareUseCache="yes"     Exists on disk1, disk2, disk3, disk4, disk5, disk6, disk7, disk8, disk9, disk10, disk11
n-------d                         shareUseCache="yes"     Exists on disk3, disk4, disk6, disk9
S---------y                       shareUseCache="yes"     Exists on disk3, disk4, disk6, disk7, disk9, disk10, disk11
system                            shareUseCache="yes"     Exists on cache-main, disk10
T----------e                      shareUseCache="yes"     Exists on disk3, disk7, disk9
T----------e (1)                  shareUseCache="yes"     Exists on disk3, disk6, disk7, disk9
T-------------r                   shareUseCache="yes"     Exists on disk1, disk2, disk3, disk4, disk6, disk7, disk8, disk9, disk10, disk11

you seem to have 2 pools related (I think running VMs since they are ‘vm_ssd’ and ‘vm3_ssd’ with the domains share existing on both of them.   Is this intentional?   Since mover never moves files between pools you would have to do this manually if the files are not where you want them.
 

The other one that looks a little odd is the ‘isos’ share which is configured to use the ‘cache-main’ pool but seems to also have files on a ssd pool.   Again you would have to move files manually to tidy this up.   In fact since isos are often only required when initially setting up a VM you may decide to hold them instead on the array to free up pool space.

 

• I had no idea what I had for the docker container (folder or img file). I ended up deleting the docker img through the docker menu settings but that did not remove the files off of disk 10 which the mover tried to move, but also said it didn't exist. 

 

• The 2 pools that I had for VMs I was misusing. I was not understanding the difference between the pools/cache to hold the VM vs using unassigned devices to store the OS/VM on the drives directly. *** That's why the domains and isos folder was also configured wrong.

 

*What I did to correct everything was:

1. Delete all the files from Disk 10 that the mover was trying to move. I read some user forums and found out how to delete files without using an application/docker program.
   1. In terminal: 

      rm -rf /path/to/dir

         
      1.  Example:

         rm -rf /mnt/user/system/libvirt

2. Moved all the files that the mover would not move from the domain and isos shares. I read that you should only move/copy files and folders from user share to user share OR disk to disk. 
   1. In terminal: 

      mv /path/to/dir /path/to/dir 

       
      1.  Example: 

         mv /mnt/cache-main/domain /mnt/disk12/

          

After all that I was able to clean up how the cache drive acted, and I moved my VMs to run on the storage device directly (through unassigned devices).

Thank you all for the help!!