I've been adding one HDD at a time to my first unRAID setup over the last 6 days, while I transfer the files from my old PC to the new server (transfer files from old to new to free up drives, add to new server, pre-clear, add more capacity, repeat).  While I've been transferring files I've setup up all my Dockers and a test VM to play with.

 

I finished the last HDD transfer this evening and the disk is pre-clearing now which will be my parity drive.  I also pre-cleared my old SSD which I will use as a cache while I wait for the SM961 M.2 drive to be released in the UK.

 

The problem I seem to be having is the shares that I adjusted to use Cache either 'yes' or 'only' don't seem to be transferring to the cache, which has stuck at 15.8GB when it should hit over 100GB (system 22.5GB +Domains 20.9GB + appdata 67.6GB).

 

How do I get the array to move files over to the new cache?

 

Edit: Forgot to add I've stopped Docker and VM as it seemed a good idea to not have new writes on the array for the shares I'm trying to move to the new cache

The problem I seem to be having is the shares that I adjusted to use Cache either 'yes' or 'only' don't seem to be transferring to the cache, which has stuck at 15.8GB when it should hit over 100GB (system 22.5GB +Domains 20.9GB + appdata 67.6GB).

 

How do I get the array to move files over to the new cache?

unRAID will not automatically move existing files to the cache with these settings.  You may well need to do manual moves to get the results you want.

 

With the value set to Yes then NEW files will be written to the cache, and later moved to the array when mover runs (by default set to run overnight).

 

With the value set to No then this simply means that NEW files are written directly to the array drives.  Existing files on the cache will not be moved to the array when mover runs, and manual moves are required if you want to do this.   

 

With the value set to Only then NEW files are written to the cache and are not moved to the data drives to the array when mover runs.  Existing files on the array are not moved to the cache.

 

With the 6.2 release there is a new value for shares of Prefer.    What this means is if you do not have a cache drive then do nothing.    If you DO have a cache drive (or add one) then the next time Mover runs any files for the share on the data drives will be moved to the cache drive.

Thanks - I worked out that it wouldn't move files automatically last night and I've used MC to move the directories from each disk to the cache drive.

 

However, for appdata and system Fix Common Problems is saying that files still reside on the array, but I can't see any of those shares when I browse via MC or when I browse via the Main tab.  Am I missing some hidden files somewhere, need to reboot or is Fix Common Problems wrong?

Thanks - I worked out that it wouldn't move files automatically last night and I've used MC to move the directories from each disk to the cache drive.

 

However, for appdata and system Fix Common Problems is saying that files still reside on the array, but I can't see any of those shares when I browse via MC or when I browse via the Main tab.  Am I missing some hidden files somewhere, need to reboot or is Fix Common Problems wrong?

Have you tried browsing from the 'Shares' tab.  Going that route should show the  locations where any particular folder/file resides.

 

Have you tried browsing from the 'Shares' tab.  Going that route should show the  locations where any particular folder/file resides.

 

Ahh didn't realise you could browse that way (Day 7 of my trial) - it says all on cache, so I think Fix Common Problems is wrong - probably will catchup in a while or when reboot.

 

Thanks