New library folder does not get scanned

New library folder does not get scanned - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+---- Forum: Media Scanning & Identification (https://forum.jellyfin.org/f-media-scanning-identification)
+---- Thread: New library folder does not get scanned (/t-new-library-folder-does-not-get-scanned)

New library folder does not get scanned - NeoCortex - 2025-03-15

First of all: I love Jellyfin! Thanks to everyone putting love, sweat and work into this!

So I added a new Harddrive to my setup.
And added two folders (Filme2 and Serien2) of that drive to my allready existing library like this:

Realtime scanning is also enabled for that library:

But Jellyfin wont automaticly scan that folder for new entrys.
Whenever i restart Jellyfin and have a look at the log it also only talks about /data/Filme and /data/Serien which are the folders I allready had, but not the new one /data/Filme2 and /data/Serien2.

It feels like the LibraryMonitor is just not adding these folders to his "watchlist"(?).

I'm running Jellyfin in Docker. Here's my compose file:

Code:
services:

  jellyfin:

    image: lscr.io/linuxserver/jellyfin:latest

    container_name: jellyfin

    environment:

      - PUID=1000 # user 1000

      - PGID=100 # gruppe "users"

      - TZ=Europe/Berlin

      - DOCKER_MODS=ghcr.io/jumoog/intro-skipper

    devices:

      - /dev/dri:/dev/dri # hardware acceleration intel quicksync

    volumes:

      - /srv/dev-disk-by-uuid-78adfa63-048a-4cc8-ae8e-017cab31c2a2/jellyfin_config:/config #wd1

      - /srv/dev-disk-by-uuid-78adfa63-048a-4cc8-ae8e-017cab31c2a2/Filme:/data/Filme #wd1

      - /srv/dev-disk-by-uuid-22e05994-fd8f-4d68-aa0c-35a3ab147b25/Filme2:/data/Filme2 #wd3

      - /srv/dev-disk-by-uuid-78adfa63-048a-4cc8-ae8e-017cab31c2a2/Serien:/data/Serien #wd1

      - /srv/dev-disk-by-uuid-22e05994-fd8f-4d68-aa0c-35a3ab147b25/Serien2:/data/Serien2 #wd3

    ports:

      - 8096:8096

      - 7359:7359/udp #optional discover for clients

      - 1900:1900/udp #optional discover for DLNA

    restart: unless-stopped

    networks:

      - portainer_default

networks:

  portainer_default:

    external: true

This is "ls -la" on bare metal:

And this is "ls -la" inside of the docker container:

My Versions are:
Servername
JellyFinNeo
Server-Version
10.10.6
Web-Version
10.10.6 (c335a3024)
Build-Version
10.10.6

Thanks again to everyone!

RE: New library folder does not get scanned - NeoCortex - 2025-03-15

Short update: I fixed the problem with a strange workaround. Here's what I did:

• Add the new folder /data/Filme2 to my allready existing library. (Jellyfin did not scan that new folder, this is the original issue)
• Create a new library with only the folder /data/Filme2. Jellyfin will now scan that folder for new entrys.
• Delete that new library (remember the path still exists in the first/original library). Jellyfin will continue to scan that folder (as it is supposed to).

Problem solved.

My guess is there is a bug where the emby LibraryMonitor will not add a path for watching if it is a second or third path added to an allready existing library.

Sorry for my strange english, it's not my native language.