SOLVED: One of my libraries was suddenly emptied out

[nothingveryobvious]

Jellyfin 10.8.10 running via Docker on M1 Mac Mini.

Hello. I would really appreciate any help.

I have a handful of libraries, like TV Shows, Anime, Movies, Music Videos, etc. After over a year of everything being fine, suddenly my TV Shows library was just emptied out, as in there's nothing there. The files are still on my hard drives, and no folders were renamed or anything. That library consists of 2 folders from separate hard drives and none of the content is showing up.

I've tried testing playing content from my Anime library, which also consists of 2 folders from separate hard drives, and those are just fine. I also tried playing content from my Movies and Music Videos libraries and they're fine.

I tried rescanning the whole library and nothing happened. I tried deleting the TV Shows library and adding it back but nothing happened. When re-adding the folders to the library, the subfolders containing the individual shows indeed show up after I type in the folder path. So Jellyfin does seem to see them.

I tried pressing "Update all" on Sonarr (also running through Docker) just to see if it still scans my files, and it does just fine. It's reporting the correct episodes missing. It still sees all my files.

I'm not sure where to go from here. I'd appreciate any help you can provide. Thank you!

EDIT: Updated to Jellyfin 10.8.11 and removed the library and re-added it. The problem persists. Tried removing it then re-adding the library with a different name. The problem persists.

EDIT 2: I just noticed it's actually a few of my libraries that are emptied out, but not all of them. I don't understand. Could it be that Jellyfin doesn't have access to the files? I haven't changed anything about the folders that the libraries are directed to. I did update Docker a day or two ago but I doubt that could be the reason all this is happening. Again, Sonarr seems to read all my files just fine.

EDIT 3: It seems it is in access issue. I don't know what could have caused this, though, as I haven't changed anything except updated Docker. See relevant log below.

System.UnauthorizedAccessException: Access to the path '/media/file-name-here.mkv' is denied.

[TheDreadPirate]

If you have any of the *arrs running, maybe one of those changed permissions?

[nothingveryobvious]

@TheDreadPirate

That's certainly possible.

I redid the command below to all of my media, across 2 hard drives, but Jellyfin still won't scan all of them, even upon restarting Jellyfin. I also want to reiterate that I can see and play media from my Anime, Movies, Sports, Documentaries, and Music Videos libraries just fine. The Anime library is across 2 hard drives and shows up and plays fine, but my TV Shows library is across 2 hard drives and nothing is showing up.

Code:

sudo chmod -R 0777 /path/to/stuff

Any advice? Please and thank you.

[TheDreadPirate]

Can you trigger a scan, wait a bit, then upload your jellyfin log to https://sourceb.in/.

[nothingveryobvious]

@TheDreadPirate

I had to use Pastebin because I kept getting an error on Sourcebin but here you go, it's just part of it because it's all the same thing.

Interestingly, I used Ctrl+F to find some mkv files that had the access denied error, then I tried to play them on Jellyfin, and they worked just fine. Also this scan seems to mostly contain stuff from my Anime library, which seems to work just fine. Other parts of the log (not included in the Pastebin) include media from my TV Shows library, which is one of the libraries that is empty on Jellyfin. Here's another Pastebin which is the result of Ctrl+F-ing the term "TV Shows."

[use7]

I had a similar issue once where I accidently put a ".ignore" file into my library's folder. I don't know if any of the other programs you have accessing those dirs. added anything named .ignore (or sim) but you could look. When I did that I had to remove the file, then remove the library from JF and readd it for JF to look in the directory again. Other than that my guess would be the docker setup not having the directories bound (though if it just suddenly happened before a docker update I'd be suprised if this was the case).

[nothingveryobvious]

I tried downgrading Docker to the version I was using before but the problem persists.

I tried deleting my "jellyfin" folder for Docker, starting a brand new instance of Jellyfin 10.8.11 via Docker, and adding both my TV Shows and Anime libraries, but it won't scan them. My libraries are empty. I keep getting these access denied errors even though I already did the sudo chmod -R 0777 command.

I tried installing Jellyfin 10.8.11 for Mac instead, and this actually reads my Anime and TV Shows directories, but it crashes on scan, so for now it's unusable to me. However this does provide more evidence that there is something wrong with Jellyfin via Docker being able to see the files.

@use7 I looked for a .ignore file in the problematic folders and couldn't find anything. Thank you, though.

[bitmap]

So what user are you running Sonarr as? What user are you running Jellyfin as? Which one grabs your images? Check the ownership of the files and see if that makes a difference. Also, if you're using compose, posting your (redacted, if necessary) compose file might be helpful, both for Sonarr and for Jellyfin.

[nothingveryobvious]

@bitmap

Hey. Both Sonarr and Jellyfin are running with PUID and PGID of 1000. Jellyfin grabs my images.

Code:

---
version: "2.1"
services:
  jellyfin:
    image: lscr.io/linuxserver/jellyfin:10.8.11
    container_name: jellyfin
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/Los_Angeles
    volumes:
      - /Users/name/Docker/jellyfin/config:/config
      - /Users/name/Docker/jellyfin/cache:/cache
      - /Volumes/hd1/jellyfin-hd1:/media/jellyfin-hd1
      - /Volumes/hd2/jellyfin-hd2:/media/jellyfin-hd2
    ports:
      - 8096:8096
      - 8920:8920 #optional
      - 7359:7359/udp #optional
      - 1900:1900/udp #optional
    restart: unless-stopped

Code:

sonarr:
    image: lscr.io/linuxserver/sonarr:latest
    container_name: sonarr
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/Los_Angeles
    volumes:
      - /Users/name/Docker/sonarr/config:/config
      - /Volumes/hd1/jellyfin-hd1/TV Shows:/tv-shows
      - /Volumes/hd2/jellyfin-hd2/TV Shows:/tv-shows-2
      - /Volumes/hd1/jellyfin-hd1/Anime:/anime
      - /Volumes/hd1/jellyfin-hd1/K-Dramas:/k-dramas
    ports:
      - 8989:8989
    restart: unless-stopped
    labels:
      - "com.centurylinklabs.watchtower.enable=true"

[bitmap]

Okay, before I start down this path, how about doing the maintenance that I like to do with every single time I stop/upgrade a container? First, make sure you have your persistent data saved. I see you have config and cache in there, so you should be good.

Code:

docker compose stop jellyfin && docker compose rm -f jellyfin && docker compose up -d jellyfin

Stop the container, remove it (the force flag just skips "Do you really want to do that?!") and bring it back up. You have your config and cache saved, you'll be fine. Start here, it's the beauty of containers. You can also -- between docker compose rm -f jellyfin and bringing it back up -- prune your volumes, which will remove any docker volumes that might be holding on to data that you don't need. Note that if you don't have things configured properly, you will lose data, period. You're removing volumes that docker uses to dynamically store data with pruning, but it is essentially deleting the docker cache.

Code:

docker volume prune --force --all

Again, --force just skips "OMG SERIOUSLY?!" and --all removes unused volumes, not just restricting the command to anonymous volumes that are not attached to a particular container. Jellyfin doesn't create volumes by default unless you don't specify where to store data, but this is a good step in clearing out the clutter and can make a difference. After the docker maintenance (whatever parts you choose to follow), proceed to what I actually typed up before I went down this rabbit hole...

What does ls -l look like for /Volumes/hdX/jellyfin-hdX? I'm only interested in permissions and whether any ACLs have been set, so just that line for each.

You could run (requires super user, but type that on your own):

Code:

chown -R 1000:1000 /Volumes/hd1/jellyfin-hd1

And not bother with the ls command, which would just recursively set ownership of the files to your 1000 user and group, but I don't know what else you have poking around in those files so I hesitate to even recommend it. Way safer than chmod 777, though. The ls command would help you check for the next part -->

You should absolutely double check that Jellyfin has execute perms on the parent directories, which could present issues. At minimum the top-level directories, but you could incorporate a troubleshooting step of running chmod +x on UID 1000.