October 23, 20232 yr So, I'm getting this error: Share books references non existent pool cache I followed the link to the forum where this error and a fix are explained. But, what I don't understand is that I've never had this share using any cache pool at all. What is true is that about a week ago I did update all the cache pools by adding an additional cache pool with a pair of nvme's. I'm curious as to what could be causing this because now ALL my shares are reporting the same error, and as with the share above... none of the others except appdata were using the cache. Thanks Edited October 23, 20232 yr by dv310p3r
October 23, 20232 yr Community Expert You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread.
October 23, 20232 yr Community Expert According to your diagnostics that share DOES reference a pool called ‘cache’. I would check through all your shares to make sure they reference the correct pool. There also seem to be a lot of .cfg files in the config/shares folder on the flash drive that reference shares that no longer exist. Deleting these would tidy up the diagnostics by removing irrelevant information.
October 23, 20232 yr Author 43 minutes ago, itimpi said: According to your diagnostics that share DOES reference a pool called ‘cache’. I would check through all your shares to make sure they reference the correct pool. Could there be some kind of issue with configs after upgrading? Or, am I missing something? When I go into the Shares, they are not configured to use a pool, as far as I can tell, below are some screenshots of some of the shares. Also, where can I find the flash drive to remove those files you mentioned? I do most of my file management via ssh and using midnight commander. Edited: found the /boot/ folder... Thanks, Edited October 23, 20232 yr by dv310p3r
October 23, 20232 yr Community Expert The screenshot for the ‘books’ share does not seem to correspond to its .cfg file on the flash drive. Suggest making any change and hitting Apply to cause it to be rewritten.
October 23, 20232 yr Author Ok, yeah. So, somehow what's being shown in the frontend, and what the config file are for the shares are different. When I make a slight change, like the description and then apply with it's current setting, the config file for the share then accurately reflects what's on the UI. So, i guess my next question would be, if the UI is not reflecting what's in the config file, which is reflecting how unraid behaves. Is it whatever is in the UI or is it whatever is in the config file for the share. My gut says config, but what would be odd about that is that I have seen files move onto the array and not into the cache. So I'm not sure.
December 2, 20241 yr I had this issue when i was looking at my shares page tonight as well. Initially i used your solution to describe the share then remove the description, but i noticed that the minimum free space was changing from 0 to 781.2gb. I found if i simply manually enter zero, it fixes the above problem and writes the 781.2gb data field, so no need to edit and undo edit. What i do not understand is why the value, which has always been set to 0, needed changed and where it got 781.2gb for the new minimum.
December 2, 20241 yr Community Expert 11 hours ago, razzellu said: What i do not understand is why the value, which has always been set to 0, needed changed and where it got 781.2gb for the new minimum. For a long time the Minimum Free Space defaulted to 0. In one of the more recent releases (not sure which one) if the value is 0 Unraid now sets it to a value that (I think) is something like 10% of the largest drive used by a share) as this seems a better default for most users. If non-zero it is left alone.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.