Rclone Mount-Atypicial Samba/Plex Permission Issue

[ClintSouthwood]

Hello fellow unRAIDers,

 

I'm humbly asking for help from the gurus here.  I've spent several days trying to solve this one but have come up empty.  Any help would be greatly appreciated!  

I've been using a few rClone mounts for around a year, happily serving up files from gDrive to Plex and to a SMB share without issue.  A couple days ago I decided to finally set up Intel AMT in the server's BIOS to allow me to control it over the LAN.  Upon rebooting, my trusty rClone mounts were no longer accessible over SMB or from within Plex.  Windows now complains about permissions and can't access the shares.  Plex also cannot see the shares - when attempting to add a new library, the shares are shown but they are greyed-out and have a document icon next to them.  Research on the web about the greyed-out shares turns up a freenas user who had the same issue and fixed it by changing the permissions of the Samba share from within Windows.  This obviously won't work for me as Windows can't access it.

 

My rClone mounts were located under user shares.  Now, when I first set these up I didn't know about the issues with mounting shares under /mnt/user but after reading a lot and trying to solve my issue I now know that this is bad form and many people advise against it.  I think that I understand the potential issues that can arise from mounting in /mnt/user but I fail to see how it could adversely affect me in this situation.  Could this somehow be the root of my permission issues?  

 

I've since changed the mount target to be under /mnt/disks but have had the same issues  no matter where it is located.  I've also updated my rClone plugin and discovered that there are many new options since I originally started using it, including ways to change ownership and permissions using the --uid, --guid, and --umask flags.  I've tried to use these in my mounts to make them appear to be owned by nobody/users with max perms but Windows still fails complaining about perms and Plex still shows the shares as greyed-out.  The console reflects the ownership/perm changes from these flags when doing a directory listing, so it does appear that the flags are being applied.  I've also tried using chown and chmod to change the ownership and perms of the parent directories from root:root to nobody:users without success. 

 

The funny thing is that shares and the files within them can be listed and manipulated via the console (as root) without issue.  Furthermore, Plex can see the shares ONLY if the docker is run as root (uid=0 guid=0 umask=000) and Windows can access the share only if force user = root and force group = root exist in samba conf.  These clues lead me to believe that the rClone flags are just not working properly even though a ls -l in the console shows the mounts owned by nobody/users with full perms.

 

I'm out of ideas on how to fix this issue.  It's very odd because there was no clear cause for this issue.  My last ditch effort is to try and restore my appdata and even perhaps flash data from a backup created before this issue occurred but I have doubts that will do much.  And, I've never used the CA backup/restore plugin so I'm a bit reluctant to try this before asking for help.  I can provide additional info such as rClone mount flags and/or SMB params but none are particularly exotic and this was all working flawlessly for many months so I doubt it's a simple config issue.  I haven't been able to find any reports on the web of similar issues where rClone fails to properly spoof these parameters so I'm wondering if it may be unRAID specific.

 

Thanks in advance!

 

 

Edited July 27, 2020 by clintSoutwood
grammar