Hello,

Since migrating to internal boot I have been getting the error "Share mnt is an implied array-only share, but files / folders exist on the cache".

The guidance seems to be to set "use cache" to yes but this no longer seems to be a option. My mnt share is set to only use the cache.

If someone can help me fix this that would be amazing, I want it all to be working properly and the error to stop because it is fixed

tower-diagnostics-20260813-0013.zip

I have split your post into its own thread. First post in Fix Common Problems thread says:

On 5/8/2016 at 4:01 PM, Squid said:

Any support for problems this plugin finds, should be posted in the General v6 section of these forums.  Problems relating to false positives, suggestions for more checks, why I made the decisions I did, wording mistakes in suggestions, etc. should be posted here.

Since your problem is not with the FCP plugin itself, but with a problem FCP found, it doesn't belong in the FCP thread.

I don't recommend naming a user share 'mnt'. All mount points in Unraid (the paths to actual storage) are /mnt/... User shares in particular have the path /mnt/user/..., so your user share named 'mnt' is at /mnt/user/mnt. Seems like a good way to get things confused. I'm somewhat surprised that 'mnt' isn't a reserved word that is not allowed.

According to your diagnostics, the user share named 'mnt' doesn't actually have any settings. Maybe it isn't allowed and so you can't make settings for it. But since it does have files it is actually a user share. The default for any share that doesn't have settings is to not use cache, so that is why it is being flagged by FCP.

I recommend creating another share with a better name, making settings for it, and moving all the files for 'mnt' to that new share.

2 minutes ago, trurl said:

Maybe it isn't allowed

I just tried on my server and it will let me create a share named 'mnt' and I can set it to primary:cache; secondary:none so not clear what your problem is. I still don't recommend naming a share 'mnt' though.

If you insist, see if you can set it to Primary storage:cache; Secondary storage:none if that is what you want. If that doesn't work for some reason post a screenshot showing how it isn't working.

Since your share named 'mnt' doesn't actually have any settings, I have to wonder how you created it in the first place. A likely cause would be some confusion when specifying a Host path for a docker, such as /mnt/cache/mnt.

What are you using that share for anyway?

Hey,

Thank you separating it out as its own post and for taking a look/ testing some things.

I honestly had no idea its not a default share/ can't remember purposefully setting it up for anything. The data in it is a great question, it's got an old appdata in it so maybe as you say one of my paths somewhere is wrong.

I can probably just delete it and check my paths everywhere. Thanks so much for you're help, I clearly probably should have done some more investigation myself/ thought about it differently!

Deleted it and re-scanned, no problems! Double checked my paths of my containers and can't see anything obvious.

Curious on the settings thing, it seemed quite happy from the GUI but clearly got potentially got itself into a mess. Thanks again!