Array permissions set to 'Nobody' after re-flashing USB from backup.

[amateur_wizard]

My array now has all the permissions of the files set to nobody. I have tried the usual methods of setting new permissions. Setting up the windows credentials again. 'Docker Safe new Permissions' isn't showing up where I'm pretty sure it should. 

Long story short I can't write to any of the drives. Any help would be appreciated. I'm hoping it's an easy fix that I've overlooked.

[Squid]

New Permissions (or Docker Safe) is within Tools.  Docker Safe only shows up if you have FCP installed

 

But, ownership of the files is supposed to be nobody.

 

Posting your diagnostics might help

[amateur_wizard]

arctvrvs-diagnostics-20210429-1250.zip Here you go. The only way I could write was setting the Shares to Public.

[Squid]

Do you have multiple users on the server?  Windows has a "feature" (or bug depending upon how you look at it) where it caches the credentials used to connect to a remote share.  If userA was used to connect to shareA on Windows (and doesn't have rights to shareB), then Windows won't ask you for credentials to access shareB (which userB has rights to)

[amateur_wizard]

I didn't know it did that but no it's just me. However I do have a separate account to the root which I use for daily tasks, which has full permissions to everything.

[Frank1940]

I observed that you have shares with permissions in all three categories---  Private, Secure, and Public.  Many times this presents a problem.  SMB (basically) only allows a single SMB login from each Windows client computer.  You can read about it here:

 

https://forums.unraid.net/topic/25064-user-share-problem/?tab=comments#comment-228392

 

Be sure to read not only this post but the next several that follow it.  What you really want to do to to  make sure that your first login to your Unraid server from a client computer to a Private share to which the client has access privileges.  As @Squid mention, Windows can (and will) store login information.  You can find these and manage them  in the 'Credential Manager'--  Type it in the search box on the Taskbar.  (When things get screwed up with the Credential Manager, it is often best to delete every credential that is related to the server in question.)

[Frank1940]

3 minutes ago, amateur_wizard said:

However I do have a separate account to the root

 

I am confused by this statement.  The Linux user---  root --- is not permitted as a SMB user!  This is for security purposes.  (It prevents an attack on the underlying Linux system through SMB access!)

[amateur_wizard]

Thanks for all the information guys, I'm gonna wipe the old credential, make new ones set all the shares back to private, and give it another go. I have to go take care of some business before I can troubleshoot some more.

[amateur_wizard]

Thanks guys, I read the linked forum posts, set them as you asked and it worked. 

 

I would like to say that the problem that stemmed it has been bothering me intermittently for months. The server will work fine for ages then crash is strange ways. In recent times the OS would crash with the docker container still running. Then there was frequent times when the docker image would become corrupted. I ended up getting FS errors from BTRFS.

 

I'll post with diagnostics if it crashes again. Thanks again, I appreciate it.