Hey all, had a weird issue occur at some point recently (I can't pin-point the day) where I got this weird message when trying to view a share.

 

Not quite sure how or why this happened, and it's the only share that I have with this message. I can't seem to find much information regarding this error on the forums, or a solution for that matter. It's still accessible on my computers as a mapped drive, which has me very confused as to what this error is and what it means. I did try to restart the system a few times, but no luck getting rid of that message.

Thanks in advance for any help, and let me know what other information might be needed.
 

ethan-unraid-diagnostics-20220429-0821.zip

Edited May 2, 20224 yr by Squeeth
Additional Info

Friendly bump in hopes to get help resolving.

I took a look on my Unraid flash drive to verify the share still exists, and sure enough it still does. I cross checked the .cfg file of this share with my other shares in /boot/config/shares and sure enough everything is the same. Quite boggled by this one.

1 hour ago, Squeeth said:

took a look on my Unraid flash drive to verify the share still exists

A share only exists if it has folders or files, share .cfg files on flash are not removed when a share is removed. And a share can exist even if there is no .cfg file for it. Any folder at the top level of array or pools is automatically a share with default settings unless you set them.

 

So, looking at flash contents doesn't really tell if a share exists or not.

 

Your diagnostics shows a share anonymized as 'L--------------------s' which has files on many disks, but that one appears to have too many characters for the share you are having issues with.

 

What is the actual name of the .cfg file for that share on flash?

 

2 hours ago, trurl said:

A share only exists if it has folders or files, share .cfg files on flash are not removed when a share is removed. And a share can exist even if there is no .cfg file for it. Any folder at the top level of array or pools is automatically a share with default settings unless you set them.

 

So, looking at flash contents doesn't really tell if a share exists or not.

 

Your diagnostics shows a share anonymized as 'L--------------------s' which has files on many disks, but that one appears to have too many characters for the share you are having issues with.

 

What is the actual name of the .cfg file for that share on flash?

 

Thanks for the response trurl! The share .cfg file is named "Launchbox ROMS & ISO's.cfg", and matches the same (I can assume) in the Shares tab by showing "Launchbox... ISO's". The confusion continues with the fact that when I click the link for that share in the Shares tab, it shows the screenshot in my original post with the name "Launchbox ROMS".

If I go to any computer in my home network and type in my Unraid systems IP address, it does show the full share name "Launchbox ROMS & ISO's" (matching the shares .cfg) with all the folders and files present inside of the share.

7 minutes ago, Squeeth said:

&

This character could cause issues

28 minutes ago, JorgeB said:

This character could cause issues

Thanks for the reply JorgeB! I wonder if it's something to do with the most recent versions of Unraid? I never had it showing the deleted status previously; however while I can't pin point the time it started saying deleted, I do know it happened at some point after updating to rc4 (maybe even 6.10)

If that character could possibly be the cause of the issues, what would the process be to rename it without that character and still maintain functionality of the share without interrupting any of the mappings I have set on devices? Or would I just need to remap devices as needed after creating a new share and moving all the data?

Thanks in advance for the all help and input!

3 minutes ago, Squeeth said:

Or would I just need to remap devices as needed after creating a new share and moving all the data?

You'd need to remap de devices, but don't need to mode the data, just rename the share on the disk(s) it currently exists, Unraid will create a new share.cfg with the default settings, you can then adjust.

3 minutes ago, JorgeB said:

You'd need to remap de devices, but don't need to mode the data, just rename the share on the disk(s) it currently exists, Unraid will create a new share.cfg with the default settings, you can then adjust.

Thanks for the response! I'll give the rename a go, hopefully it plays out well after renaming the share on disks 1-14 😅

Thanks to the suggestion made by @JorgeB to rename the folders on the disks, it now works! I used Krusader to browse and rename on the disks, and afterwards confirmed that once adding in the "&" character, the share went back to "deleted" again. Interesting!

Thanks again for the help!