Upgraded to 6.4.0.rc7a and let the 8TB parity drive do its thing for 15 hours.

Previously on 6.3.5, cache drive was flowing just fine with mover.

Trying to start the mover gives the below log entries:

Aug 14 07:46:55 Tower emhttpd: 
Aug 14 07:46:55 Tower root: mover: cache not enabled, exit

 

There is about 35GB free on 250GB SSD cache drive. appdata is set to use cache: yes.

tower-diagnostics-20170814-0747.zip

Have you got the cache disk enabled under Settings->Global Share Settings?

I will definitely check this when I get home from work.

Thinking the setting did not carry over after the OS upgrade?

@itimpi Yes, cache disk is enabled under global share settings.

Try toggling it off, rebooting, and then setting it on again.    There was another report earlier today where the cache disk setting was showing as on but it was not being used where toggling the setting cleared the issue.

@itimpi You are aaaammmaaazzzing!

Worked like a charm and the mover is movin'!

I had this exact same issue previously with my cache drive on a totally clean install.

 

Guess this might actually be an issue with this build.

Thank you. Worked great on my trial server (running 6.4.0_rc10b).

I can verify this is a bug - new install - use cache disk says enabled - but is disabled.

 

 

Have to stop array and toggle it off/on, restart array and all is well