I believe the two shares are actually a case issue and I am trying to figure out where there is a reference to an uppercase version.  However these were both fine until I ran the latest update and now it is reporting this?

 

 

This is what I see in share settings:

 

 

As far as I can tell these shares are not set to go to cache?

odin-diagnostics-20241201-0917.zip

Click on the shares, do a dummy change and click apply.

I have the same issue, tried the dummy change suggestion, did not work, error persists

Attach Diagnostics to your NEXT post in this thread. 

I had this same issue. Making a random change (I changed the description slightly) and APPLYing semed to fix it. 

I just added a new share and this same error showed up on a few of my already-in-place shares. Dummy editing fixed it, but WTH.

Same issue. A dummy change save did not resolve. This is a brand new install with one Array and the auto-created "appdata" & "system" shares. These 2 shares have the warning.

 

I did create an additional new Share, and this new share does not have the warning.

Edited December 6, 20241 yr by kevev

On 12/3/2024 at 5:50 AM, trurl said:

Attach Diagnostics to your NEXT post in this thread. 

 

I seem to face a similar issue. Also likely since the 6.12.14 update.

 

Some of my "user shares" show as "This share is invalid, it references storage that does not exist". Storage shows as "cache", which doesn't even exist. When I select the user share, it shows all the files, which are on a different storage. So, I am not sure whether this issue impacts in any way or is just a UI issue?

 

Maybe related is that my Unraid storage no longer shows on my network share in Windows. I can still access it via the IP. Also sees to be the issue since the latest 6.12.14 update.

On 12/3/2024 at 10:23 AM, usbrit said:

I have the same issue, tried the dummy change suggestion, did not work, error persists

Diagnostics attached, having issues with some dockers since 6.12.14, so I'm going to downgrade to 6.12.13 to see if everything workstower-diagnostics-20241207_0839.zip

33 minutes ago, usbrit said:

Diagnostics attached

Which share(s) show invalid?

3 hours ago, usbrit said:

Diagnostics attached, having issues with some dockers since 6.12.14, so I'm going to downgrade to 6.12.13 to see if everything workstower-diagnostics-20241207_0839.zip

On downgrading to .13 everything now back to normal

Same issue here. The storage names were old and have not been used in a while but after the upgrade they reappeared. I did make a dummy change to each share using the Minimum free space setting and that seems to resolved it. They are now showing the correct storage (Array).

eos-diagnostics-20241207-1011.zip

54 minutes ago, MikeC said:

The storage names were old and have not been used in a while but after the upgrade they reappeared. I did make a dummy change to each share using the Minimum free space setting and that seems to resolved it. They are now showing the correct storage (Array).

This means the old share cfg files were still referencing the old pool, and by making the dummy changes it's now fixed.

Thanks JorgeB for the feedback. I can confirm that looking at a backup I do in fact see shareCachePool="cache" in some of the share cfg files.

On 12/7/2024 at 6:29 PM, JorgeB said:

This means the old share cfg files were still referencing the old pool, and by making the dummy changes it's now fixed.

The dummy changes did not fix my issue.

58 minutes ago, usbrit said:

The dummy changes did not fix my issue.

Post the diags and the affect share name(s)

@JorgeB - thanks for the assist.  I had that same weird problem, but your "dummy change" recommendation did the trick (unraid 6.12.14)

Dummy Change fixed it for me..... just added a word in the share description and applied.  

Problem appears to be a blank minimum free space section. Any change to the settings, auto populates the minimum space and removes the warning.

Edited January 6, 20251 yr by dojesus

I have many shares like this after a new config parity rebuild.
Quickest way to fix this if you have many shares, is to copy the minimum space value that the system creates, paste and apply to all your shares

This happened to every share except my appdata, domains, isos and system (the ones where the shares' mover action is set from secondary to primary storage.) Did @dojesus' suggestion of copying the free space value so a very many shares and that seems to resolve it. 

This should no longer happen with v7.0.0

Also occurs for 6.12.15

 

Flagged all my Array shares with this error.

 

As suggested dummy change fixes it.

Edited January 23, 20251 yr by Distorter

On 1/12/2025 at 2:32 AM, JorgeB said:

This should no longer happen with v7.0.0

Happens to me on 7.0.1.

 

Tried a dummy change, but got this:

 

Diagnostic attached.

tower-diagnostics-20250411-1242.zip.crdownload