January 18, 20251 yr The file above shows the issue with the shares. I've gone through with the upgrade, and when it came back online, these shares came back with the following error: "This share is invalid. It references storage that does not exist." I've seen other people's posts on this issue and I've attempted to make a dummy change to them. However, every time I do, I get the following error: Everything using these drives seem to be working correctly. However, I'd like to get this fixed as I have no idea what it's talking about with a cache drive as I don't have one on my server: Here is my array setup: Any help would be appreciated as I have no idea what it's going to do if I even attempt to update one of my docker containers.
January 18, 20251 yr Community Expert Are you saying you cannot select the 'Array' option as primary storage? Your screenshot suggest you should be able to.
January 18, 20251 yr Author 9 hours ago, itimpi said: Are you saying you cannot select the 'Array' option as primary storage? Your screenshot suggest you should be able to. I definitely can select "array" as the option and it will let me proceed on. However, I am unsure whether or not these Shares should be set to "Array" or if they should be set to "Cache"... I don't remember what it was set to before I did the upgrade cause I thought that would be unaffected. However, now I'm stuck cause I don't know if it was set to cache prior or not (even though I've never had a cache drive in my server).
January 18, 20251 yr Author 10 hours ago, dlandon said: Post diagnostics. Here are my diagnostics. tower-diagnostics-20250118-1640.zip
January 18, 20251 yr Community Expert 53 minutes ago, skillsjr123 said: I definitely can select "array" as the option and it will let me proceed on. However, I am unsure whether or not these Shares should be set to "Array" or if they should be set to "Cache"... I don't remember what it was set to before I did the upgrade cause I thought that would be unaffected. However, now I'm stuck cause I don't know if it was set to cache prior or not (even though I've never had a cache drive in my server). Your screenshot shows you have no cache pool, so the only valid option will be array.
January 18, 20251 yr Solution All you have to do is select 'Array' and save the changes. In an earlier version of Unraid, the 'Cache' pool was presumed to be there, but in 7.0.0, a verification was added to check the Secondary Pool. This situation was ignored is earlier versions of Unraid but now generates an error.
January 19, 20251 yr Author 3 hours ago, itimpi said: Your screenshot shows you have no cache pool, so the only valid option will be array. I only do have the array and don't have a cache. That fixed my issue. Thanks for the help!
January 19, 20251 yr Author 2 hours ago, dlandon said: All you have to do is select 'Array' and save the changes. In an earlier version of Unraid, the 'Cache' pool was presumed to be there, but in 7.0.0, a verification was added to check the Secondary Pool. This situation was ignored is earlier versions of Unraid but now generates an error. Thank worked to solve my problem. Thank you very much for your help!
July 2, 20251 yr On 1/19/2025 at 6:08 AM, dlandon said:All you have to do is select 'Array' and save the changes. In an earlier version of Unraid, the 'Cache' pool was presumed to be there, but in 7.0.0, a verification was added to check the Secondary Pool. This situation was ignored is earlier versions of Unraid but now generates an error.this solves my issue. Thanks.
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.