Jellyfin only reading some random files

[m0r4a]

Hi!, I usually don't ask for help but I feel very stuck at this moment.

--- Context ---

I used to (two days ago) run my Jellyfin server with this docker-project structure:
- docker-compose-yaml
- media
- - Shows
- - - What do we do in the shadows (2014)
- - - - Season 01
- - Movies
- - - Movie 1, 2,....

Shows and Movies were symlinks to /nvme/media/Shows and movies respectively.

I tried to integrate Sonarr, Radarr and Transmission, Added the libraries to the apps and worked, but Radarr needed the movies to be inside folders so I changed it to be in folders like this:

- - Movies
- - - Movie 1 (Year)
- - - - Movie 1.mkv

And everything started to break, the movies weren't read properly anymore even though I moved them back to be just the files.

As I kept forward I ended up with a structure like this:

- shared
- - media (symlink to /nvme/jellyfin/media)
- - torrents (same for /torrents)

And now nothing worked, even going back to all default settings didn't work

--- Problem ---

Now even if I create a differente docker instance, deleting cache and history data of firefox inside shows Jellyfin only reads one or two episodes randomly, don't load the images but the single episode is playable.

-- Information --

* the nvme drive is mounted in the fstab like this:
UUID=655DE1BC56F708F5 /nvme ntfs defaults 0 0

* Pastebin for jellyfin logs: https://pastebin.com/zmt8vtkt

* Pastebin for how Jellyfin looks in docker-compose.yaml: https://pastebin.com/ADT0s3rK

* Media have 777 permissions

* When executing a shell inside jellyfin image I can see all .mkv files

-- What i've tried --

* Going back to the same old folders and docker-compose setup
* Copying one season with the proper file structure inside the docker project
* changing my mounting in fstab (used to have different options, I tried same thing with both mounting ways)
* starting a new project with new cache and config folders
* adding new content to the media folders

I think is something simmilar to https://forum.jellyfin.org/t-solved-libr...able-media but in my case im running everything in a docker container

[m0r4a]

I would like to add that Movies library is indeed empty

[TheDreadPirate]

What is the output of

Code:

sudo ls -ld /media /media/Movies /media/Shows/ /media/Shows/"What we do in the shadows (2014)"
sudo ls -l /media/Shows/"What we do in the shadows (2014)"

You said that /media has 777 permissions, but we're going to check the full path.

[m0r4a]

With this structure:
- docker_compose.yaml
- shared
- - media

And running the command inside shared, this is the output:

-- First command --

> sudo ls -ld ./media ./media/Movies ./media/Shows/ ./media/Shows/What\ do\ we\ do\ in\ the\ shadows\ \(2014\)
lrwxrwxrwx 1 m0r4a docker 20 Jun 27 17:48 ./media -> /nvme/jellyfin/media
drwxrwxrwx 1 root root 0 Jun 27 17:47 ./media/Movies
drwxrwxrwx 1 root root 0 Jun 27 18:04 ./media/Shows/
drwxrwxrwx 1 root root 0 Jun 27 18:04 './media/Shows/What do we do in the shadows (2014)'

I can't change the user:group value, I think due the mount options in fstab

-- Second command --

> sudo ls -l ./media/Shows/What\ do\ we\ do\ in\ the\ shadows\ \(2014\)/
total 4
drwxrwxrwx 1 root root 4096 Jun 27 18:04 'Season 01'

[TheDreadPirate]

Wait. Hold up. /media is a symlink? What are the permissions on the symlinked directory? The symlink being 777 does not get around the destination's permissions.

Code:

sudo ls -ld /nvme /nvme/jellyfin /nvme/jellyfin/media

[m0r4a]

I changed the target directory in docker_compose.yaml from /shows to /media, literally just a rename and now it's working, I'm legally downloading two movies to check if I rename the /Movies to /media2 does the trick and I can get that up and running, if so I will let you know.

I will edit this post in a few minutes to add the output for the permissions that you asked for

Edit 1:

-- Output for the command ---

drwxrwxrwx 1 root root 4096 Jun 27 18:03 /nvme
drwxrwxrwx 1 root root 0 Jun 27 17:47 /nvme/jellyfin
drwxrwxrwx 1 root root 0 Jun 27 17:47 /nvme/jellyfin/media

-- News --

Apparently renaming the target to /media and /media2 did the trick but I don't understand why

(In docker_compose.yaml)

- type: bind
source: ./shared/media/Shows
target: /media

- type: bind
source: ./shared/media/Movies
target: /media2

Edit 2:

I added a third media source with target name /media3 and still works, added "read_only: true" option and still works, so apparently the naming is the problem?

[TheDreadPirate]

I just remembered something. If you use symlinks in a container and the linked destination path doesn't exist for the container, it will never find them.

Since you didn't mount /nvme in the container, your symlink pointing to it doesn't exist from the container's perspective.