File permissions & users on Arch

[Guest deleteduser0341]

I'm setting up a server on Arch (installed via aur) and I'm having some issues with file permissions so I'm troubleshooting. I've mounted the NAS drives via cifs and I have full permissions to them. I understand Emby runs under the user 'emby' so I was planning on adding this user to my group, however, this user does not seem to exist. Do I need to create it manually?

[mastrmind11 722]

11 minutes ago, MeltNvy said:

I'm setting up a server on Arch (installed via aur) and I'm having some issues with file permissions so I'm troubleshooting. I've mounted the NAS drives via cifs and I have full permissions to them. I understand Emby runs under the user 'emby' so I was planning on adding this user to my group, however, this user does not seem to exist. Do I need to create it manually?

weird, emby should be a system user (ie, no home directory).  but i'm guessing that since your cifs you need to adjust your fstab file with appropriate permissions.  as a test, and i'm in no way saying leave it this way, just give everyone full access to your mount in fstab and see if it works (after a remount/reboot).  this is a pretty vanilla setup so i'm not sure where you it went awry...  

as an aside, what does id emby say?  

[Guest deleteduser0341]

id emby returned

uid=64552(emby) gid=64552(emby) groups=64552(emby),1001(okita)

so I suppose it does exist. My fstab looks like this:

//192.168.1.59/disk1/ /mnt/MB/D1 cifs x-systemd.automount,x-systemd.idle-timeout=1min,rw,uid=okita,gid=okita,credentials=/etc/samba/private/server.cred,iocharset=utf8,vers=2.0 0 0

//192.168.1.59/disk1/ /mnt/MB/D1 cifs x-systemd.automount,x-systemd.idle-timeout=1min,rw,uid=okita,gid=okita,credentials=/etc/samba/private/server.cred,iocharset=utf8,vers=2.0 0 0

As of now, Emby can see the files but not delete them (so no write permission). I've added 'emby' to the group 'okita' which should have full permissions? Adding file_mode=0664,dir_mode=0775 in fstab leaves Emby with no read permission.

I'm not an expert at this stuff so I'm sure I've done something wrong.

Edited February 8, 2021 by deleteduser0341

[mastrmind11 722]

yeah CIFS kinds sucks, might consider moving over to NFS if you have a rainy day.  you seem to have a lot of fluff in that command line that you likely dont need or even know what it means (I don't).   anyway check this out https://unix.stackexchange.com/questions/98707/how-do-i-mount-a-cifs-share-so-i-can-fully-control-the-mounted-volume-on-the-cli

as a starting point just do the full access to user/group by following that suggestion, then we can trim it back from there.

[Guest deleteduser0341]

file_mode=0777,dir_mode=0777

With this added Emby has read and write permissions.

Edited February 9, 2021 by deleteduser0341

[Guest deleteduser0341]

From my understanding file_mode=0666 should be sufficient for read write permissions (0777 would be execute). Despite this it seems Emby isn't allowed to write to the disks according to the log I uploaded in this thread.

As of now the fstab entries look like this:

//192.168.1.59/disk1/ /mnt/MB/D1 cifs x-systemd.automount,x-systemd.idle-timeout=1min,rw,uid=okita,gid=okita,file_mode=0666,dir_mode=0777,credentials=/etc/samba/private/server.cred,iocharset=utf8,vers=2.0 0 0

It is mounted under my user/group (okita) and 'groups emby' returns 'okita emby'. Does this not mean Emby should inherit read/write permissions? What more do I need to do?

[Luke 42078]

Did you take a look at this?

https://wiki.archlinux.org/index.php/Emby