Hi! I have set up my Jellyfin with NFS Shares from another Server. Jellyfin is able to acces those paths since it I saw it writing .nfo files in the directories of the episodes and Movies.

The movies and series are recognised correctly, but when I open said movies or series, i cant see the episodes and i am unable to start playing them.

It was able to find all epsidoes of like two series. When you open one of those two, you are able to see the episodes but cant play them. If you do, an error about unsupported formats pops up.

ffmpeg is installed in the directory that jellyfin expects it, so i dont have any idea why this is also failing.

Does this sound familiar to any of you fellas? If so, could you give me a hint or a link that helps me with this anomaly? Thx in advance!

top 5 comments

sorted by: hot top controversial new old

[–] jubilationtcornpone 3 points 1 year ago (1 children)

What OS is your Jellyfin server and the file server running? Are you running Jellyfin w/ Docker or natively?

Also, have you checked the Jellyfin logs for any errors?

[–] [email protected] -1 points 1 year ago (1 children)

Running it on Debian. Filesystem - no clue. All i know is that its running on an encrypted LVM Volume. Didn't care enough to fiddle with the filesystem tbh.

And no, I didn't have time to check the logs yet. Its running since a few days and I didn't have much time to troubleshoot it. I know, always check the logs first... I hoped someone here alread had this issue and could pinpoint what was their solution ^^

[–] jubilationtcornpone 1 points 1 year ago

Not much else you can do without checking the Jellyfin logs. It could be a transcoding issue. Could also be permissions or something else altogether.

[–] [email protected] 1 points 1 year ago (1 children)

When you set up your libraries, it's important that you point the path at the root folder, jellyfin expects a fairly specific naming convention.
Here's how it is suggested to setup your tv shows for instance: https://jellyfin.org/docs/general/server/media/shows

Simplistically, lets say you have 2 shows called "Friends" and "The Witcher", each with multiple seasons, and your NFS mount is /mnt/media.
You'd create something like: /mnt/media/tv
That's where you'd point your tv library, at that "tv" directory. It doesn't actually matter what the directory is called, but the library should be of type "shows".
Under that /mnt/media/tv directory, you would create a directory for each show, and it would be the name of that show, so you'd get: /mnt/media/tv/Friends/ and /mnt/media/tv/The Witcher/
Then under those directories you would create seasons, to put your episodes in, ie /mnt/media/tv/The Witcher/Season 01/The Witcher - 01x01 - The End's Beginning.avi
/mnt/media/tv/The Witcher/Season 01/The Witcher - 01x02 - Four Marks.avi

If you pointed the root of your library at /mnt/media/tv/The Witcher/Season 01/, it would probably fail to parse the episodes.
If you create your library as /mnt/media/allmystuff/ and just ram everything in there, it's unlikely to find anything.
This may all seem a bit complicated, but there's lots of tools that are useful to automate this process.
I personally recommend https://sonarr.tv/

If you are doing all of the above correctly, we'll have to dig a bit deeper for more details.

As for "unsupported formats", that most commonly happens when you have enabled hardware acceleration and it's not working properly.
Whilst there's several reasons why it may not be working, to rule it out, try temporarily disabling Hardware Acceleration under Dashboard -> Playback -> Transcoding.
The system should fall back to CPU transcoding which may be slow (hardware dependent), but at least it should function.

[–] [email protected] 2 points 1 year ago

Thanks a lot for the detailed reply! I will check the scheme in wich all my media is stored and the hardware accelerated setting. I appreciate your comment a lot. Thank you mate!