On the web admin page (http://localhost:8096/web/library.html) where you add the 'media library' it has a note at the top which says,
For Linux on Arch Linux, CentOS, Debian, Fedora, OpenSuse, or Ubuntu, you must grant the Emby system user at least read access to your storage locations.
So I wasn't expecting my permissions to be a problem until I got that error. I have a generally okay understanding of permissions in Linux. But I tried your suggestion and set permissions to 777 in the fstab.
Side note: Since the entire drive is media only, the 'problem' of the filesystem being NTFS is a lesser one yes? Although, I confess, even setting it as I originally had it felt a bit 'open'. However, I agree... I sort of wish I had gone with ext4 or ZFS. At the time, I wasn't able to predict the number of linux based devices joining the household.
After reboot and permissions now showing as drwxrwxrwx (or -rwxrwxrwx) everywhere on that drive I went to add the media library again.
And the error message is the same.
There was an error adding the media path. Please ensure the path is valid and the Emby Server process has access to that location.
And then I realized that I'm a big liar! Although, that has been media only for years, I recently moved my home directory to that drive (thinking that then I could reformat/reinstall other o/s flavours at will). So I uninstalled/reinstalled emby-server (thinking that perhaps config had failed to be written properly).
But no, that makes no difference. (sigh)
For completeness I tried:
(incidentally... which one is appropriate?)
I have tried this in firefox and chrome (not chromium) with equivalent results.
So I'm still at a loss. And even more of a loss. The location definitely exists. The permissions are now wide open.
Edited by bric, 29 October 2016 - 03:10 PM.