ClawSS

Always remember to reboot BEFORE calling support.

This issue has resolved itself following the set to Public...reboot server...set to Private & set the SMB user access again. I had previously been unable to reboot the server due to kicking off the Parity check, but once I was able to do so, it appears back to functioning as expected. Thanks to everyone for helping. I truly appreciate it. Now to move on to another issue plaguing my Cache drive which is an empty folder not wanting to delete.

Nothing changes in regards to the error generated. I unmapped and remapped after changing that setting.

Private

If it was permission related, I doubt I could rename and it work and change back and fail. The permission would not change nor would it change back after an un-rename. Right?

What would that data tell you besides the names of the owners of the shares? Why share this on a forum?

I am renaming using the GUI. There are no files giving me errors. I cannot create a file or move one to the Share. All of the files I have looked at on the share will open in windows fine. I just cannot update and resave them to that Share. If I create a new Share and physically move existing files to it, I can access and create files and folders fine. I have no problem deleting the old share at that point. But if I rename the new share to the name of the old one or create a new share with the original name…I cannot write to the share any longer.

I renamed and found that I could do what I needed. I changed it back and again couldn’t. I thought that was a clue when just by renaming the top level folder allowed the cache to work without any other changes to the setup of the share.

That’s the thing…I’m not wanting to change the share name. It just now decided to not let me create into it giving the initial error. Rename activity is only a test mechanism.

I tried the New Permissions earlier, but will again just on that Share. I attempted to write again this morning and captured a new diag. file here. tower-diagnostics-20260404-0815.zip

Do I need to add a new diag. file? I have put the share names back to where they were prior to my testing.

Yes Chris_Share was a rename. The error is from Windows when the share was Chris and I was attempting to create a new folder in file explorer.

If I rename the share and keep all settings the same, I am able to write to the share. If I change the share to write directly to the array, then I am also able to write to the share.

Ok, it was set to 42 GB, and I lowered it to 20 GB. Same result. I then raised it to 50 GB and again same result.

"Chris" is the name of the Share. tower-diagnostics-20260403-1609.zip