I just installed unraid on a ryzen 5 2600 with 16 gb of ram 3 3tb red hard drive and 1 500 gb m2 cache drive well. I cant get the move now button to move my files from my m2 ssd to my hard drives. when I hit it it just dose nothing. I only made one share made it my name Adam and installed plex. even when I stop plex it still wont move anything. I hit it and it just re load the same web page and the button stays clickable the move now button at the bottom of the main page.  any help please 

 

 

 

update helps if ya read what it say fully in unraid I figured it out I had my shares set to prefer instead of yes use cache drive. Prefer just moves files from hardrives to ssd hece why it was not doing anything since ssd was full.

Edited July 29, 20196 yr by Adamwilkerson
figured it out

Go to Tools-diagnostics and attach the complete Diagnostics zip file to your next post. 

thanks i figured it out i had my shares set to prefer instead of yes use cache drive. prefer just moves files from hardrives to ssd hece why it was not doing anything since ssd was full i feel dumb helps if ya read.

Don't feel bad. The cache settings have evolved over the years as functionality was added, but the settings haven't been renamed to make things intuitive.

 

When the cache drive was first introduced, it was simple. cache yes, use the cache for new files. If the cache was full, write directly to the array. Move any files on the cache to the array on schedule. cache no, don't put new files on the cache drive, so no move action needed. Straight forward, to the point.

 

As unraid evolved, it became clear that other scenarios were desirable, so the option to put new files on the cache drive and leave them there was introduced, and logically called cache only. Also, no move action needed.

 

Things got more complicated when it became clear that an option was needed for new files to be written to the cache, but allow overflow to the array if the cache was full. When the mover runs, any files in those shares should be moved to the cache if there is room. Cache prefer describes that adequately enough IF you know the history of the cache drive.

 

Cache prefer also describes exactly what is wanted for shares that really SHOULD be on the cache drive, like system and domains, but if the user doesn't have a cache drive, they can live on the array until a cache drive is installed. Then, as soon as a cache drive is available, they will be transferred there.

 

Problem is, yes no only and prefer are not particularly clear when viewed in isolation. They only make sense after you know the history of the cache drive.

 

@Adamwilkerson, since you just got bit by the non-intuitive nature of the settings, can you suggest better one word terms to describe each one?