dkrysak 0 Posted February 24, 2019 Share Posted February 24, 2019 Hi there, Are there any limitations to using an external drive mounted via SMB or NFS? For some reason my TV library will show, but my movie library will not. It is so odd. If I put htemovies on a local drive -works without issue. Same permissions (user and octal), etc. I'm using the docker container and mounting the same base media folder (movies and tv are subfolders) - so the same mount point is used by both. I just updated the docker container (latest) - an there is no change there. Ideas? docker version Client: Version: 18.06.1-ce API version: 1.38 Go version: go1.10.4 Git commit: e68fc7a Built: Fri Jan 25 14:33:54 2019 OS/Arch: linux/amd64 Experimental: false Server: Engine: Version: 18.06.1-ce API version: 1.38 (minimum version 1.12) Go version: go1.10.4 Git commit: e68fc7a Built: Thu Jan 24 10:56:33 2019 OS/Arch: linux/amd64 Experimental: false cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS" Version 4.0.2.0 Emby Server is up to date Link to comment Share on other sites More sharing options...
dkrysak 0 Posted February 24, 2019 Author Share Posted February 24, 2019 Oh, adn this is how I am launching the container: cat run-emby.sh #!/bin/bash sudo docker run --name emby-server -d --volume /home/media/docker/emby:/config --volume /NFS/media:/mnt/media --volume /home/media/out:/mnt/out --device /dev/dri/renderD128 --publish 8096:8096 --publish 8920:8920 --env UID=112 --env GID=119 --env GIDLIST=44,122,124 emby/embyserver:latest exit 0 Link to comment Share on other sites More sharing options...
Luke 37251 Posted February 25, 2019 Share Posted February 25, 2019 hi, what are the mounted paths to your movie and tv folders? Link to comment Share on other sites More sharing options...
dkrysak 0 Posted February 25, 2019 Author Share Posted February 25, 2019 hi, what are the mounted paths to your movie and tv folders? In the docker command I pass through: -volume /NFS/media:/mnt/media --volume /home/media/out:/mnt/out And within Emby I have: /mnt/media/Movies /mnt/out/Movies Then on the host the file system has: > tree -L 1 . ├── Movies ├── Recycle Bin └── TV Shows And now from within my container: # ls /mnt/ media out # ls /mnt/out Movies TV Shows tmp # ls /mnt/media/ Movies Recycle Bin TV Shows Link to comment Share on other sites More sharing options...
Luke 37251 Posted February 26, 2019 Share Posted February 26, 2019 Can you run a library scan and then attach an emby server log? thanks. Link to comment Share on other sites More sharing options...
dkrysak 0 Posted February 26, 2019 Author Share Posted February 26, 2019 Can you run a library scan and then attach an emby server log? thanks. Here we go! embyserver.txt Link to comment Share on other sites More sharing options...
Luke 37251 Posted February 28, 2019 Share Posted February 28, 2019 I don't see anything here. Is it possible that Emby server just doesn't have permissions to the folder? That's my best guess at this point. Link to comment Share on other sites More sharing options...
dkrysak 0 Posted February 28, 2019 Author Share Posted February 28, 2019 Well, I use the same user for my Plex install, and they are running side by side. So I suspect the permissions are not the issue. I also just double checked, and the group had full access. I also double checked the UID, and GUID that I launch the container with... Also matches. I then compared the permissions on the movie folder on the internal drive vs the Nas drive... Identical. If I copy the files back to the internal drive, they show and operate as expected. Link to comment Share on other sites More sharing options...
Luke 37251 Posted March 1, 2019 Share Posted March 1, 2019 The server sets up a system user called Emby. Did you check permissions for that user? Link to comment Share on other sites More sharing options...
Damien_ 27 Posted March 1, 2019 Share Posted March 1, 2019 (edited) I ran into A similar issue on unraid with my other mounted network drives. I was ready to pull my hair out. One library could see the entire path and the other couldn’t. It made zero sense. My issue had to do with the where I started my /Mnt path. It was very weird like I couldn’t start mapping the path from the very beginning at /, I had to start at /mnt (or the other way around). It didnt make any sense as they theoretically should’ve been going to the same place but it wouldnt whatever reason. If it sounds like a similar problem/it’s in the ballpark of your issue let me know and I’ll take screen shots and post specifics when I’m at my desk tomorrow morning. Edited March 1, 2019 by meatball Link to comment Share on other sites More sharing options...
Luke 37251 Posted March 1, 2019 Share Posted March 1, 2019 Thanks for the info ! 1 Link to comment Share on other sites More sharing options...
dkrysak 0 Posted March 2, 2019 Author Share Posted March 2, 2019 I ran into A similar issue on unraid with my other mounted network drives. I was ready to pull my hair out. One library could see the entire path and the other couldn’t. It made zero sense. My issue had to do with the where I started my /Mnt path. It was very weird like I couldn’t start mapping the path from the very beginning at /, I had to start at /mnt (or the other way around). It didnt make any sense as they theoretically should’ve been going to the same place but it wouldnt whatever reason. If it sounds like a similar problem/it’s in the ballpark of your issue let me know and I’ll take screen shots and post specifics when I’m at my desk tomorrow morning. @@meatball It might be helpful to see the screenshots. I don't quite follow the changes you made. So you see anything of with my mounts that match you scenario... Link to comment Share on other sites More sharing options...
Damien_ 27 Posted March 2, 2019 Share Posted March 2, 2019 (edited) So I have a Synology NAS on my network that I need to access from unraid where Emby is running. The Synology drive is always mounted via SMB on unraid. The path to access it is /mnt/disks/DISKSTATION_Plex_Media/Movies (if I'm mapping to movies) If I start to map the drive in emby starting at "/" in the path (shown below) , then proceed to choose /mnt then /Plex_Media; I can click through to movies as you would expect. However if I back up one folder to the very beginning with no "/" already in the path and start the mapping with /mnt (shown below), I'll be able to get to the drive, however I won't be able to click through to movies, the mapping will stop at /mnt/disks/Plex_Media and the media wont be accessible on Emby. It doesn't make a ton of sense as it should ultimately go to the same place. More frustrating is this issue isn't consistent, sometimes it works as expected and sometimes I have to be aware of where I start mapping the drive. Not sure if this is helpful or not but this is what I ran into. Hopefully you've got the issue resolved. Edited March 2, 2019 by meatball Link to comment Share on other sites More sharing options...
dkrysak 0 Posted March 3, 2019 Author Share Posted March 3, 2019 The server sets up a system user called Emby. Did you check permissions for that user? That user is a member of the `plex` group (since I am currently running side by side as I test emby). ``` emby:x:999:plex ``` And the permissions on the folder (and the files in) are: ``` drwxrwxr-x+ 150 media plex 0 Feb 24 13:10 Movies/ ``` Link to comment Share on other sites More sharing options...
dkrysak 0 Posted March 3, 2019 Author Share Posted March 3, 2019 And for confirmation, I am also launching the container with the UID and GID of the plex user. ``` $ id plexuid=112(plex) gid=119(plex) ``` ``` $ cat run-emby.sh #!/bin/bashsudo docker run --name emby-server -d --volume /home/media/docker/emby:/config --volume /NFS/media:/mnt/media --volume /home/media/out:/mnt/out --device /dev/dri/renderD128 --publish 8096:8096 --publish 8920:8920 --env UID=112 --env GID=119 --env GIDLIST=44,122,124 emby/embyserver:latestexit 0 ``` On a hail mary I just added the GID of emby to the GIDLIST, which made no difference. Link to comment Share on other sites More sharing options...
dkrysak 0 Posted March 3, 2019 Author Share Posted March 3, 2019 So I have a Synology NAS on my network that I need to access from unraid where Emby is running. The Synology drive is always mounted via SMB on unraid. The path to access it is /mnt/disks/DISKSTATION_Plex_Media/Movies (if I'm mapping to movies) If I start to map the drive in emby starting at "/" in the path (shown below) , then proceed to choose /mnt then /Plex_Media; I can click through to movies as you would expect. However if I back up one folder to the very beginning with no "/" already in the path and start the mapping with /mnt (shown below), I'll be able to get to the drive, however I won't be able to click through to movies, the mapping will stop at /mnt/disks/Plex_Media and the media wont be accessible on Emby. It doesn't make a ton of sense as it should ultimately go to the same place. More frustrating is this issue isn't consistent, sometimes it works as expected and sometimes I have to be aware of where I start mapping the drive. Not sure if this is helpful or not but this is what I ran into. Hopefully you've got the issue resolved. Thanks for the screenshots. I really appreciate it. Unfortunately, this did not work for me. Link to comment Share on other sites More sharing options...
dkrysak 0 Posted March 3, 2019 Author Share Posted March 3, 2019 Ok - one step further. I even created a new user on the NAS and set the UID to match the media server user. I had suspected that the login user for the share could be an issue. But no go. (PLus plex can access without issue. ) Link to comment Share on other sites More sharing options...
dkrysak 0 Posted March 3, 2019 Author Share Posted March 3, 2019 Just to confirm there is not some Docker behavior that I may not be aware of, I have a posted on the Docker community to rule out Docker cfg issues. https://forums.docker.com/t/volume-with-a-smb-share/70320 Link to comment Share on other sites More sharing options...
Damien_ 27 Posted March 6, 2019 Share Posted March 6, 2019 Thanks for the screenshots. I really appreciate it. Unfortunately, this did not work for me. Sorry it didnt help. I spoke to soon, I'm still having issues as well https://emby.media/community/index.php?/topic/71043-mapped-network-drive-content-not-available-on-emby/ Link to comment Share on other sites More sharing options...
dkrysak 0 Posted March 7, 2019 Author Share Posted March 7, 2019 Sorry it didnt help. I spoke to soon, I'm still having issues as well https://emby.media/community/index.php?/topic/71043-mapped-network-drive-content-not-available-on-emby/ Don't sweat it. I'm thinking it is a limitation of docker - or rather there is a certain way you need to mount the volume vs the way the docker instructions state. Link to comment Share on other sites More sharing options...
dkrysak 0 Posted March 19, 2019 Author Share Posted March 19, 2019 Ok. I have been all over this. THe current status is that Emby cannot see the data (post scan). I have taken this into the docker community as well, and the only thing they suggested was to mount the volume using the CIFS driver. SO I had done this: ``` #!/bin/bash# Create a docker volume that allows SMB access.# - Pulled from:# German: https://nerdblog.steinkopf.net/2017/12/persistente-docker-volumes-mit-nfs-und-cifs/# English: https://translate.google.com/translate?hl=de&sl=auto&tl=en&u=https%3A%2F%2Fnerdblog.steinkopf.net%2F2017%2F12%2Fpersistente-docker-volumes-mit-nfs-und-cifs%2F# NFS Example#docker volume create \# --driver local \# --opt type=nfs \# --opt o=addr=172.30.1.1,rw \# --opt device=:/export/dockervolumes/xxtestvolumepath \# xxtestvolumedocker volume create \ --driver local \ --opt type=cifs \ --opt o=addr=172.30.1.1,rw \ --opt device=//172.30.1.1/media \ --opt o=uid=0,username=SMBUSERID,password=SMBUSERPASS,nounix,file_mode=0770,dir_mode=0775 \ smbmediavolsudo docker run \ --name emby-server \ -d \ --volume /home/media/docker/emby:/config \ --volume smbmediavol:/mnt/media \ --volume /home/media/out:/mnt/out \ --device /dev/dri/renderD128 \ --publish 8096:8096 \ --publish 8920:8920 \ --env UID=112 \ --env GID=119 \ --env GIDLIST=44,122,124 \ emby/embyserver:latestexit 0 ``` Other Things Tried matched up the UID that the NAS, Emby and the mount user have. tried mounting with the above docker volume method Reset all permissions using the UID/GID (vs user names) Within the docker container (running) I can interact without issue on the file system. I'm really at my wits end here. I cannot be the only person using the docker container with a remote file share.... Link to comment Share on other sites More sharing options...
dkrysak 0 Posted March 19, 2019 Author Share Posted March 19, 2019 Alright - I went a step further. I spun up a plex docker container, and mounted my SMB data just using a traditional --volume (not a docker volume), and it worked immediately. No issues. I thus far only have this issue with Emby regardless of using the traditiona; `--volume` mount, or using the Docker volume itself with the CIFS drivers. Link to comment Share on other sites More sharing options...
dkrysak 0 Posted March 19, 2019 Author Share Posted March 19, 2019 OK - here is another thing I just noticed - TV Shows work on the external mount (same mount!). Just not movies.... Link to comment Share on other sites More sharing options...
Luke 37251 Posted March 19, 2019 Share Posted March 19, 2019 can you try the beta server and see how that compares? thanks. Link to comment Share on other sites More sharing options...
dkrysak 0 Posted March 19, 2019 Author Share Posted March 19, 2019 can you try the beta server and see how that compares? thanks. Hi Luke - same behavior. I tried mapping the volume with the two previously described volume methods. I created a new "Movies" folder in the NAS (was hoping that since TV was working...), and moved in a single test Movie. Link to comment Share on other sites More sharing options...
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