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

One of my personal shares has stopped allowing saves or creation of folders. It gives the following message when trying to create a folder anywhere on the share: I can Create a new Share with a different name and move all files over physically & things work just fine. I can RENAME the original Share and things work just fine. But if I rename a new Share to be the same "old" name, I again get the listed error. I feel it is a corruption linked to the original Share and some unresolved issue, but I am not versed enough in Linux to figure out what to do. I'd like to get back to my old name of the Share due to links to it on other machines. Any help is appreciated.

Big thanks...the down-up grading worked. I will now go to 7.01 and see how that executes. I appreciate it.

plugin: run failed: 'upgradepkg --install-new' returned 127 trying to update to 2.25 running 7.0 using the install from the Apps tab. Advice?

You are absolutely correct...my bad for not looking hard enough at the connections first. But I think either is good in its own right for unraid connectivity and controlling SATA. Yes?

Can someone use this: IO CREST SI-PEX40138 Internal 4 Port Non-Raid SATA III 6GB/S with M.2 B-Key 22x42 Pci-E X4 Controller Card for Desktop PC Support SSD and HDD with Low Profile Bracket. JMB585 Chipset with this and get 9 ports??? IO CREST Internal 5 Port Non-Raid SATA III 6GB/s M.2 B+M Key Adapter Card for Desktop PC Support SSD and HDD. JMB585 Chipset

diggin the SuperMicro's for almost 3yrs now.