Upgrading cahce drive has resulted in appdata on both Disk 1 and Cache

[rajk]

Hi All 

 

i am a new user to unraid and currently runing version 6.9.2. My setup consits of 2 x 4TB Seagate Ironwolf Pro disks ( 1 x data and 1 x parity) and a cahce drive (oringinally HDD but now SSD, please see below)

 

When i first set it up i did not have a SSD for cache so decided to just use  a spare 1TB HDD.  I just bough a SSD today and my intention was to replace the cache HDD with the SSD. I watched a few video on the internet and looked at the Wiki page on how to uprgade your cache drive. It seemed easy enough but i have a minor problem . I have highlighted this with an asterix in the body of the procedure i followed. I wonder if anyone can help

 

I followed the process

 

Stopped the dockers (only one, krusader the file manager) I had running

Stopped the docker and VM service from the settings tab (my cpu does not support virtulisation so did not have any VM's)

Changed the mover settings to monthly (it was on daily)

Changed appdata share settings to 'use cache pool' setting from prefer to yes

Changed domains share settings to 'use cache pool' setting from prefer to yes

Changed system share settings to 'use cache pool' setting from prefer to yes

Started the mover process.

 

* The mover process seemed to take a long time for what seemed a small amount of data on the oringal cache drive (about 22GB). Anyway after it had finished i looked on the oringinal cache drive and there were still some folder for appdata. I tried mover again but some files remained . I looked into the folder and the unraid interface said 0 files too long too list. Anyway i proceeded to the next steps as below

 

 

Stopped array, unassigned the existing Samsung Cache HDD and assigned the new Crucial SSD

Formatted drive

Set all shares to their previous setting of prefer cache (those that had that set to them before the upgrade)

Started mover again 

Enabled the docker service

Changed mover back to daily schedule.

 

* The problem i have is that my only disk in the array still has appdata on it, just like the oringal cache drive had when i wanted the files to move to the array before the disk stop. What is causing this? Why isn't mover moving all the appdata files back to the cache even though i have disabled the docker service? When i look at the files in the appdata folder on the array disk they relate to krusader which i have shutdown and disabled the docker service. Can anyone shed any light on this please?

 

Much appreicated

 

Raji

 

[trurl]

Mover won't move duplicates. If it is only krusader appdata on array, just delete it.

[rajk]

Just now, trurl said:

Mover won't move duplicates. If it is only krusader appdata on array, just delete it.

Thanks when i installed the new SSD cache drive it didnt have anything on it, so there were no duplicates only the files that mover had previously moved to the array. 

 

In terms of just deleting it from disk 1 (my only data dsik) wont this cause a problem with the labels that appdata has. For example if i look at the share appdata and click on the little folder icon it says its in disk1, cache. if i simply delete it form disk 1 wont it get confused. Also how do i delete it from disk 1? If i look at krusader there is no path into disk 1. I am able to access shares, unassigned drives and remotes ( i follwed spaceinvader one process for krusader) but i cant see an entry for /mnt/disk1/.  I can access it from a command line window but im not comfortable just deleting the whole appdata folder as i think it might cause a problem as unraid things its across my cache and disk1! Sorry im just a newb lol. 

 

 

[trurl]

What do you get from the command line with these?

ls -lah /mnt/cache/appdata

ls -lah /mnt/disk1/appdata

 

[rajk]

7 minutes ago, trurl said:

What do you get from the command line with these?

ls -lah /mnt/cache/appdata

ls -lah /mnt/disk1/appdata

 

thanks, this is what i get

 

 

ls -lah /mnt/cache/appdata

total 16K
drwxrwxrwx 1 nobody users 30 Nov 19 13:36 ./
drwxrwxrwx 1 nobody users 40 Nov 21 14:49 ../
drwxrwxr-x 1 nobody users 56 Nov 19 13:39 binhex-krusader/

 

 

ls -lah /mnt/disk1/appdata
total 0
drwxrwxrwx 3 nobody users 29 Nov 19 13:36 ./
drwxrwxrwx 5 nobody users 47 Nov 19 13:04 ../
drwxrwxr-x 3 nobody users 26 Nov 19 13:39 binhex-krusader/

[trurl]

And what do you get with these?

ls -lah /mnt/cache/appdata/binhex-krusader
ls -lah /mnt/disk1/appdata/binhex-krusader

 

[rajk]

ls -lah /mnt/cache/appdata/binhex-krusader
total 240K
drwxrwxr-x 1 nobody users   56 Nov 19 13:39 ./
drwxrwxrwx 1 nobody users   30 Nov 19 13:36 ../
drwxrwxrwx 1 nobody users   52 Nov 19 13:39 home/
-rw-r--r-- 1 root   root   162 Nov 19 13:39 perms.txt
-rwxrwxr-x 1 nobody users 235K Nov 21 17:01 supervisord.log*

 

ls -lah /mnt/disk1/appdata/binhex-krusader
total 0
drwxrwxr-x 3 nobody users 26 Nov 19 13:39 ./
drwxrwxrwx 3 nobody users 29 Nov 19 13:36 ../
drwxrwxrwx 3 nobody users 20 Nov 19 13:39 home/

 

 

[trurl]

OK, nothing in disk1 appdata you need

rm -r /mnt/disk1/appdata

 

[rajk]

Thanks it did the trick and everything else looks okay. i need to get familiar with these command line instructions.