Unable to Edit Files

[PapaZurc]

I recently updated my home server from FreeNAS to TrueNAS Scale. I didn't have any issues, but just wanted to get the latest and greatest. We'll see if this was a mistake. It seemed to be working fine as all my files were present and the server was working as usual, until I attempted to edit some of the files. I keep getting the "You require permission from Unix User/bin to make changes to this file". I have searched and fiddled with settings for several days with no success. Any help would be greatly appreciated.

 

[LarsR]

Did you follow the official Upgrade path ? So freenas to core to scale?

 

[PapaZurc]

Did you follow the official Upgrade path ? So freenas to core to scale?

Yes I did.

 

[LarsR]

Have you edited the acl's on the Dataset so your user has the correct permissions?

 

[anodos]

Before touching permissions, it might be a good idea to investigate how these files are currently owned and what the ACL set on them currently is. Things being owned by UID 2 (bin) is unusual to say the least.

If dataset has been migrated from Core, then correct tool to view permissions of file is nfs4xdr_getfacl.

 

[PapaZurc]

These are the dataset permissions.
@anodos "Things being owned by UID 2 (bin) is unusual to say the least."
I changed the owner to root with no success, so I put it back to where it was so you can see it.

 

[anodos]

I changed the owner to root with no success, so I put it back to where it was so you can see it.

Hmm... well, that was touching permissions :)

What is output of following commands:

Code:

nfs4xdr_getfacl /mnt/SamuelPool
nfs4xdr_getfacl /mnt/SamuelPool/Embymediafiles

 

[PapaZurc]

Hmm... well, that was touching permissions :)

Hehehe. I'm sorry. And I hope I didn't do any more damage.
However, @anodos, thanks to you I believe the problem is fixed. "bin" shouldn't have been the owner. I changed the user and group to embyuser gave new permissions and I had some success. After figuring out to use the same credentials on the NAS and PC and allowing permissions there as well, that seemed to fix the problem.
Thank you all for your help. I am truly grateful for your patience and willingness to help.