Having a strange problem and was curious if anybody else experienced this. PMS is running on a dedicated NUC with Ubuntu. I have all my media using NFS shares via Synology NAS. I also have HDHomeRun CONNECT DUO so we can watch/record our local channels. I have noticed if I schedule a new DVR recording when Plex is making the directory in the dvr library the folder has only owner read permissions and thus plex can’t save the recorded file to the folder until I go in and change the permissions. Is there a setting in plex to fix this? Is this a known issue? Am I doing something wrong in maybe my NFS mappings or in the share options on Synology? Once I change the permission on the folder all episodes record fine.
I have checked the permissions and that whole mount is owned by plex.plex. It also does create the folder correctly but when you look at the permissons it only has read for the owner so even though plex owns the directory it can’t copy/move the recorded file over when it finishes. Once I go in and give owner full permissions (rwx) it starts recording the episodes fine. This is what is leading me to believe that plex is not creating that folder correctly.
Given how Synology works (which it does work very well with NFS),
Create a username plex on the Syno even if you don’t run PMS on it.
Now give user plex permission to read & write the appropriate shares (mounted directories).
What happens here is:
NUC sends read/write request as user plex
Syno sees user plex and uses that name for permission validation.
Sees user plex is permitted to read (or write) and completes the request.
Synology creates directories with no permissions by default.
It relies on its proprietary ACL / database mechanism to validate.
On the Syno, NFSD / BIOD runs as root so permission bits & UID/GID do not matter.
IF UID/GID matching is desired:
After creating user plex on the syno, manually edit its /etc/passwd to match
On Linux, mount with sec=sys to enable full UID/GID mode.
Now , as root, on the NUC side, set permissions as you would for any normal linux mount.
If you want to push the performance curve (I have 10 GbE)
Thanks ChuckPa, helpful as always. I was able to get this to work. I had to modify a few things following this guide. But I got everything working now.
Synology GUI:
Create group: plex
Create user: plex
For each share in NFS rule enter following:
Hostname or IP: address of your machine
Privilege: Read/Write
Squash: No mapping
Security: sys
Control Panel > File Services > NFS > Enable NFS > Enable NFSv4.1 support > NFSv4 domain:
If I don’t include the 777 permissions then I have the same issue. I have tried setting user and group read/write permissions for plex user and the plex group for the DVR share using Synology ACL’s. The folder gets created with the correct owner but with no permissions.
Synology doesn’t assign permissions on files or directories by default. that’s how they do it Everything is done through their database (Control Panel - Shared Folders - EDIT the share - Permissions tab)
d-----+ for a directory ------+ for a file
If you want to take over, SETUID & SETGID bit usage is recommended.
by doing so, permissions and user/group are preserved in all subordinate files and directories.
But shouldn’t Plex be setting permissions then? Plex is creating the directory when I schedule a new recording. But because the directory that is created has no perms it will fail to copy the recorded file over to this new folder until I manually change the perms to make it writeable.
I was kinda thinking it might be a umask issue as well. But when I checked the plex user that was created in Ubuntu it has a “/usr/sbin/nologin”. So my understanding is that “should” inherit the default umask. Should I change this account to a normal account so I can try and setup a umask or might that screw up some other things? I can share whatever is needed just let me know what you need to see.
