Jellyfin Forum
Media library on second volume - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Media library on second volume (/t-media-library-on-second-volume)



Media library on second volume - JYabs - 2024-06-29

I'm completely new to jellyfin, the lightweight no ads etc is what caught my attention. I'm coming from a Synology NAS initially which had a very friendly UI for dumb people like me. Unfortunately my model wasn't compatible with jellyfin so I "upgraded" to an Asustor nimbustor 2. 

My plan, which I don't see why it wouldn't be an option is to have my media library on a second drive, separating my media for jellyfin from my personal files. Currently, this is done. Volume 1 is my personal files. Volume 2 is all of my media i want accessible in jellyfin.

From the stock asustor UI...App central > download docker > download jellyfin.

I run jellyfin and complete the initial set up. No problems. 

Add library, nothing. If I put a media file in any other folder it'll find it, but anything from volume 2 it can't find. I've clicked all the "permissions" i could find, even allowing anonymous access. I've verified the folder location, i've changed the permissions in windows, there has to be something i'm missing and i would appreciate someone with patience to explain it. Any of the googling i do only goes over permissions if the folder is on the same volume. What do I do when the media is on a separate volume? I don't see why this wouldnt be possible but here we are.

What am I missing?


RE: Media library on second volume - Efficient_Good_5784 - 2024-06-29

How did you deploy the Jellyfin container? Could you share the compose file or screenshots of how you set up the host mounts?

Maybe you just need to host mount the volume 2 directories.


RE: Media library on second volume - dukemockingbird - 2024-09-08

EDIT: Not anymore. Not sure what happened. Maybe it was upgrading to 10.9.10.r01 today. The world may never know.

Did you ever find a solution to this problem? I'm experiencing the same thing.