Bert08 3 Posted April 2, 2020 Posted April 2, 2020 I have my Emby server installed on a Raspbian system. My files are stored on a Synolgy NAS shared over network. Where do I have to set the folders permission for proper file access and data saving? On Raspbian or on Synology? And what's the name of the user I must grant permission to? Thanks
mastrmind11 722 Posted April 2, 2020 Posted April 2, 2020 well, your emby server needs proper r/w access to the folders mounted on the server, and your NAS needs to allow the folders r/w mount access. the user emby will need the access.
JaScoMa 34 Posted April 2, 2020 Posted April 2, 2020 You should be able to configured NFS on your Synology then configure Raspbian to connect to the Synology via NFS. This way, the share permissions are configured on your NAS via IP address. Plus, NFS has less overhead on Raspbian than installing and running Samba.
Bert08 3 Posted April 2, 2020 Author Posted April 2, 2020 Hey everyone, thanks for your help. I used autonfs to connect RB to NAS and I set the NSF permissions for the RB IP in the Synology. Is that a correct way? If that's correct I'm missing something because i still have write permissions issues on Emby server (read works fine) Should I add to the library on Emby using nfs://192.168...?
mastrmind11 722 Posted April 2, 2020 Posted April 2, 2020 I have no idea how synology works, but generally speaking with NFS shares on normal linux, both client and server have to give access to the same user on each system (and uid/gid need to match between systems).
Solution Bert08 3 Posted April 6, 2020 Author Solution Posted April 6, 2020 Hey everyone, after a lot of trial and error I solved my problems. If anyone as the same configuration as me (Linux/Raspberry server with SYnology storage) here's what I did: - set NFS Permissions on the Synology for the shared folder with media on it (pointing to the server IP) - mounted the shared folder on the Pi using autofs - added on Emby the library using the local mounted directory (/mnt/[...]) plus the network path (\\192.168...). So I didn't use any smb: or nfs: prefix - everything works! This way I solved all my problems regarding playback and subtitles. I'm very satisfied now! 2
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now