My single BTRFS cache disk got corrupted recently, and I tarred up the contents onto one of the spinning disks while I reformatted the cache as XFS.

 

On restarting, I added the cache and verified it was showing as green, then attempted to write to cache:

 

root@celestia:~# touch /mnt/user/appdata/spoon
touch: cannot touch '/mnt/user/appdata/spoon': No medium found

The appdata share was set to "use cache disk: only". Other shares that had cache enabled but not set to "only" wrote to spinning disks instead of cache.

 

Setting each share to "use cache disk: no", applying, then reverting to the previous setting, does nothing — unRAID still refuses to write to cache.

 

How can I get unRAID to actually write to the cache disk? And shouldn't it handle a reformatted cache disk a bit more gracefully, rather than just refusing to acknowledge it?

 

(Incidentally, getting the popup help on the various options for this setting requires noticing that the mouse pointer has changed to a question mark when you mouse over a bit of blank space that looks like every other bit of blank space — could there perhaps be a '?' button that people can see, instead? It took ages before I noticed there was any help available in unRAID itself…)

 

Thanks

celestia-diagnostics-20171202-1628.zip

Settings -> Global share settings -> Use cache disk:

 

Set to "yes"

37 minutes ago, ElectricBadger said:

could there perhaps be a '?' button that people can see, instead?

 

See Help button at top.

On 02/12/2017 at 5:07 PM, johnnie.black said:

Settings -> Global share settings -> Use cache disk:

 

Set to "yes"

 

Thanks — I'm sure I looked at that page and completely missed the option, as well… Everything is now up and running

 

On 02/12/2017 at 5:10 PM, bonienl said:

 

See Help button at top.

 

Hm, yes — but that expands everything at once. I think it would be useful for the GUI to hint that an area can be clicked to get help for an individual item without having to wave the mouse around to spot it. Not sure how to avoid the ugliness of a page full of question marks, though…