• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support Troubleshooting Media Scanning & Identification Jellyfin library empty on Synology NAS

    Pages (2): 1 2 Next »

     
    • 0 Vote(s) - 0 Average

    Jellyfin library empty on Synology NAS

    aptmx
    Offline

    Junior Member

    Posts: 6
    Threads: 1
    Joined: 2024 Feb
    Reputation: 0
    Country:United States
    #1
    2024-02-14, 03:19 PM
    New to Jellyfin, and tried setting it up on Synology NAS using Docker.  I followed this guide: https://mariushosting.com/how-to-install...ology-nas/

    I made sure my GID and UID were correct. The NAS has two volumes (docker folder is on Vol 1 and media library is on Vol 2).  I created the correct folders in the docker folder (on vol 1).  My Media folder (on vol 2) contains about 6 various folders of movies and tv shows (comedies, tv shows, action, etc.) 

    This was the script I used:  

    docker run -d --name=jellyfin \
    -v /volume1/docker/jellyfin/configConfused-faceconfig \
    -v /volume1/docker/jellyfin/cacheConfused-facecache \
    -v /volume2/MediaConfused-facemedia \
    --user 1026:100 \
    --net=host \
    --restart always \
    jellyfin/jellyfin

    When trying to add my library, I see /media but the library is empty after I select it.  I also don't see how to add more libraries based on the folders I have within my media folder.  I had read giving it access to the /volume2/Media folder should allow access to the main 6 folders within that.  I also made sure that the media folder had SYSYTEM read/write permissions as mentioned towards the bottom of the article so that docker has access to that folder.  Any idea why Jellyfin will show empty libraries still?  I am at a loss.  Thanks


    Attached Files Thumbnail(s)
               
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2024-02-14, 06:46 PM
    Not entirely sure how permissions work with Synology. Are the permissions you set on the share recursive?
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    Efficient_Good_5784
    Offline

    Community Moderator

    Posts: 1,168
    Threads: 3
    Joined: 2023 Jun
    Reputation: 50
    #3
    2024-02-14, 07:02 PM (This post was last modified: 2024-02-14, 07:10 PM by Efficient_Good_5784. Edited 2 times in total.)
    My bet is that it's the user you're running it under.
    Just in case (since you state you have the correct UID + GID), your provided example has "--user 1026:100" which is the same one as in the guide. You probably copied this over from that and probably isn't linked to any user in your actual server.

    You can try:
    • Changing the UID+GID to the correct user on your NAS
    • Change the UID+GID to root (to see if this is the issue)
    • Remove the "--user #:#" line to have Jellyfin run as root anyway
    ------------------------------------------------
    Edit:

    Looking at the picture of your container's volume settings, you linked the folder wrong.
    You have it linked to the directory "/Media".
    Turn off the container, then edit the path to be "/volume2/Media/".

    Can you post the actual docker run command that you used?
    aptmx
    Offline

    Junior Member

    Posts: 6
    Threads: 1
    Joined: 2024 Feb
    Reputation: 0
    Country:United States
    #4
    2024-02-14, 07:55 PM
    (2024-02-14, 07:02 PM)Efficient_Good_5784 Wrote: My bet is that it's the user you're running it under.
    Just in case (since you state you have the correct UID + GID), your provided example has "--user 1026:100" which is the same one as in the guide. You probably copied this over from that and probably isn't linked to any user in your actual server.

    You can try:
    • Changing the UID+GID to the correct user on your NAS
    • Change the UID+GID to root (to see if this is the issue)
    • Remove the "--user #:#" line to have Jellyfin run as root anyway
    ------------------------------------------------
    Edit:

    Looking at the picture of your container's volume settings, you linked the folder wrong.
    You have it linked to the directory "/Media".
    Turn off the container, then edit the path to be "/volume2/Media/".

    Can you post the actual docker run command that you used?

    Hi.  I did get my actual user UID + GID.  It just happened to match the one in the guide.  I will try removing the user line like you stated.  The actual run command is what I did post.  (it is from the guide with my specific settings modified).  I will also try editing the container with that correct path.  Thanks for the advice and I will report back.
    aptmx
    Offline

    Junior Member

    Posts: 6
    Threads: 1
    Joined: 2024 Feb
    Reputation: 0
    Country:United States
    #5
    2024-02-14, 08:08 PM
    (2024-02-14, 07:55 PM)aptmx Wrote:
    (2024-02-14, 07:02 PM)Efficient_Good_5784 Wrote: My bet is that it's the user you're running it under.
    Just in case (since you state you have the correct UID + GID), your provided example has "--user 1026:100" which is the same one as in the guide. You probably copied this over from that and probably isn't linked to any user in your actual server.

    You can try:
    • Changing the UID+GID to the correct user on your NAS
    • Change the UID+GID to root (to see if this is the issue)
    • Remove the "--user #:#" line to have Jellyfin run as root anyway
    ------------------------------------------------
    Edit:

    Looking at the picture of your container's volume settings, you linked the folder wrong.
    You have it linked to the directory "/Media".
    Turn off the container, then edit the path to be "/volume2/Media/".

    Can you post the actual docker run command that you used?

    Hi.  I did get my actual user UID + GID.  It just happened to match the one in the guide.  I will try removing the user line like you stated.  The actual run command is what I did post.  (it is from the guide with my specific settings modified).  I will also try editing the container with that correct path.  Thanks for the advice and I will report back.


    No luck.  I uploaded pictures of what I tried and Jellyfin still does not see anything.  When I click add folder in the container settings and select my media folder, it just shows up as /Media regardless.  I tried adding /volume2/Media/ to the text box next it and re-adding the library but it still sees nothing.  Not sure how to get root UID and GID and if I remove the line entirely, I have to create the entire container again?


    Attached Files Thumbnail(s)
           
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #6
    2024-02-14, 08:14 PM
    This is what it should look like, I think.

       
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    2
    tmsrxzar
    Offline

    Senior Member

    Posts: 755
    Threads: 6
    Joined: 2023 Nov
    Reputation: 20
    #7
    2024-02-14, 08:36 PM
    (2024-02-14, 08:08 PM)aptmx Wrote: No luck.  I uploaded pictures of what I tried and Jellyfin still does not see anything.  When I click add folder in the container settings and select my media folder, it just shows up as /Media regardless.  I tried adding /volume2/Media/ to the text box next it and re-adding the library but it still sees nothing.  Not sure how to get root UID and GID and if I remove the line entirely, I have to create the entire container again?

    you're looking at it backwards, the left side is the volume on Synology, the right side is the path in the docker where Jellyfin will access it

    look at TDPs screenshot above
    1
    Efficient_Good_5784
    Offline

    Community Moderator

    Posts: 1,168
    Threads: 3
    Joined: 2023 Jun
    Reputation: 50
    #8
    2024-02-14, 09:12 PM (This post was last modified: 2024-02-14, 09:13 PM by Efficient_Good_5784. Edited 1 time in total.)
    Yeah, delete the current reference to "/Media", then relink the correct one. The Correct mount path will still be "/media".

    Also make sure to edit your script correctly because that will probably rewrite this change the next time you run it.
    aptmx
    Offline

    Junior Member

    Posts: 6
    Threads: 1
    Joined: 2024 Feb
    Reputation: 0
    Country:United States
    #9
    2024-02-14, 09:51 PM (This post was last modified: 2024-02-14, 09:55 PM by aptmx.)
    (2024-02-14, 08:36 PM)tmsrxzar Wrote:
    (2024-02-14, 08:08 PM)aptmx Wrote: No luck.  I uploaded pictures of what I tried and Jellyfin still does not see anything.  When I click add folder in the container settings and select my media folder, it just shows up as /Media regardless.  I tried adding /volume2/Media/ to the text box next it and re-adding the library but it still sees nothing.  Not sure how to get root UID and GID and if I remove the line entirely, I have to create the entire container again?

    you're looking at it backwards, the left side is the volume on Synology, the right side is the path in the docker where Jellyfin will access it

    look at TDPs screenshot above

    I am not able to make it look like that though?  When I click add folder, it just lets me choose a shared folder and when I click Media, it just shows up as /Media. There is no way that I see to specify volume2 anywhere.  It just automatically chooses Media and is displayed as /Media.  See attached screenshot.

    Even though the Media folder is on Volume2, the NAS does not see that when trying to map this in the volume settings within the container. It only sees the Root folders regardless of what volume they are on....


    Attached Files Thumbnail(s)
       
    Efficient_Good_5784
    Offline

    Community Moderator

    Posts: 1,168
    Threads: 3
    Joined: 2023 Jun
    Reputation: 50
    #10
    2024-02-14, 10:41 PM
    I tried googling how Synology handles showing you multiple volumes and the best I found is this: https://www.reddit.com/r/synology/commen...t/cyf41tt/

    On my Synology NAS, I only have one volume, but I'm thinking that if you scroll down that list of folders when you try and add them, you will find another "Media" folder that will actually be on volume2.

    I don't understand why Synology can't show which volume you're actually using.
    Pages (2): 1 2 Next »

    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode