• 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): « Previous 1 2

     
    • 0 Vote(s) - 0 Average

    Jellyfin library empty on Synology NAS

    Efficient_Good_5784
    Offline

    Community Moderator

    Posts: 1,168
    Threads: 3
    Joined: 2023 Jun
    Reputation: 50
    #11
    2024-02-14, 10:51 PM
    Ok, so I think I understand what's going on now.

    You most likely have a shared folder on volume1 named "Media". You now have a shared folder on volume2 named "Media".
    This is what's giving you an error. The GUI that Synology made where you add shared folders doesn't display which folders reside in which volume, so it's a guessing game.

    I would try renaming either of the shared folders so that both are not "Media". Go to the control panel and edit the name of one of these shared folders.
    If you rename the "Media" folder in volume2, just select that new shared folder name in the container manager setup.
    aptmx
    Offline

    Junior Member

    Posts: 6
    Threads: 1
    Joined: 2024 Feb
    Reputation: 0
    Country:United States
    #12
    2024-02-15, 12:21 AM (This post was last modified: 2024-02-15, 12:24 AM by aptmx.)
    (2024-02-14, 10:41 PM)Efficient_Good_5784 Wrote: 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.

    So as a test, I tried copying oner movie file into /Movies (which is on Vol 1) and added that path to the container to allow access.  I made sure permissions had SYSTEM R/W to that folder.  I then went on Jellyfin and added that library using that path and same issue! Completely empty and blank.  I am at a complete loss here.. It just can not access any folder regardless of location.....

    (2024-02-14, 10:51 PM)Efficient_Good_5784 Wrote: Ok, so I think I understand what's going on now.

    You most likely have a shared folder on volume1 named "Media". You now have a shared folder on volume2 named "Media".
    This is what's giving you an error. The GUI that Synology made where you add shared folders doesn't display which folders reside in which volume, so it's a guessing game.

    I would try renaming either of the shared folders so that both are not "Media". Go to the control panel and edit the name of one of these shared folders.
    If you rename the "Media" folder in volume2, just select that new shared folder name in the container manager setup.

    The Media share on exists on Vol 2.  I do not have anything with that name on Vol 1.  I do have a share called Movies which I tried as a test and that did not even work. (my previous post).  Frustrating but I do appreciate your help in trying to figure this out!
    aptmx
    Offline

    Junior Member

    Posts: 6
    Threads: 1
    Joined: 2024 Feb
    Reputation: 0
    Country:United States
    #13
    2024-02-15, 12:35 AM
    So I tried this way of installing Jellyfin : https://nascompares.com/guide/easy-way-t...-nas-2023/

    This way worked perfectly. This was through Synocommunity. I am not sure if this is considered more "risky" that using docker? This saw everything though once I set the permission as described. Working as it should now!
    Cyphersphere
    Offline

    Junior Member

    Posts: 1
    Threads: 0
    Joined: 2024 Jul
    Reputation: 0
    #14
    2024-07-14, 06:10 PM
    I had the same exact problem using NFS. Perms were fine and nothing I did would allow Jellyfin to see the media.

    What worked for me was simply using cifs instead of nfs. I just added a line like this to my /etc/fstab:

    //xxx.xxx.xxx.xxx/Video /media/video cifs username=xxx,password=xxx 0 0
    Pages (2): « Previous 1 2

    « 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