Hello, after a system hang and a forced reboot, my Cache share is missing. The cache drive(s) are still present and the data is still there, and the data is still accessible. However Fix Common Problems is throwing out warnings:

 

Share Cache is an implied array-only share, but files / folders exist on the cache (when I click Cache Settings it says "Share Cache has been deleted")

Share appdata set to cache-only, but files / folders exist on the array

Share system set to not use the cache, but files / folders exist on the cache drive

 

Any idea how I screwed up and how I can fix it?

 

System log is attached for good measure.

syslog.txt

I hope that you do not really have a share called ‘Cache’ - this could cause problems with the ‘cache’ share as Linux is case significant at the file system level!

 

You need to provide the full system diagnostics zip file (obtained via Tools->Diagnostics) as providing just the syslog (which is only part of the full diagnostics) does not provide enough information for properly informed advice.

tortuga-diagnostics-20190524-0601.zip

It definitely looks as though you have a share called 'Cache' (with a capital C) that is interfering with the system share called 'cache' (with a lower case 'c').     For some reason the files share.cfg which would have allowed us to see if you had disk shares configured was missing from the diagnostics - not sure what can cause that

 

Since all top level folders are treated as User Shares, creating a share called 'Cache'   can happen if you accidentally create a folder called 'Cache' on any of your array drives or on the cache drive.   Since case is significant in Linux file systems this can happen if you are manually copying files or if you have a docker misconfigured to do so.   You need to look at each of your drives to see if they contain a folder called 'Cache' and if they do rename it to something else as the first start of getting things back into order.

 

The FCP plugin is also issuing warnings about the 'appdata' share being set as 'cache-only' but having files on the array.  The easiest way to fix this will be to change the setting for that share to 'Use cache'=Prefer; turn of the docker service; and then run mover manually from the Main tab.  when that completes you can restart docker.

 

FCP is also warning you that you have several dockers configured to use an Unassigned Device, but have not correctly specified that they should use the slave option.  To fix this you need to go into the settings for the dockers and for any such drive being passed through and click the Edit option to change the mode to be either RW:Slave or RO:Slave as appropriate.