I am trying to copy a directory to my media share on my unraid server, and getting "Permission Denied"... however I can copy files without issues. I've tried:

 

• Using Docker Safe New Perms to check if the permissions are incorrect
• SSH in to the server and checked the share root permissions.
• I've made sure all plugins, dockers, etc. are updated.

 

I am using Thunar as a file manager, and connecting to the share using built-in network mounting functions (not /etc/fstab as I don't always want it mounted) ... I can open the mount in Nemo file manager as well, same thing happens. I can create a directory in the share using Thunar (just not copy an already existing one), but I can't create a directory if I "Open in terminal" the share using Thunar.

 

It hasn't always done this, so perhaps after the 6.11 update? I think it has something to do with samba being updated but couldn't find much about that.

 

https://imgur.com/a/VZRYSVD  -  Shows images of settings, permissions, and permission denied on copying folder

 

Any suggestions would be very helpful, thank you very much for your time! I can provide any logs, images, or information as needed, I'm just not sure what all might be needed to start with.

 

Share settings:

 

Media share permissions:

 

 

Drag and drop copy of file in thunar permission denied, but file copy works fine.

 

 

Attempting to mkdir by right click in share on thunar > open in terminal > permission denied

 

 

However I can right click > create folder just fine:

 

 

Directory created, but if I need to copy directories with many recursive elements, it would take forever manually.

 

Edited October 10, 20223 yr by MadMikeG
Images and info

You should attach the images in the post, most people don't want to follow links to external websites.

Fixed, thank you.

Not sure if diagnostics file will help, attaching anyways.

tower-diagnostics-20221010-1407.zip

Windows 10 mounted share works fine so I guess it’s actually something to do with the way my file managers are mounting the share? 

I suppose something or some package updated and now everything works fine. For anyone who finds this later with the same problems, check for package updates on the computer connecting to the share. Maybe check version compatibility.