Sonarr Library Empty or Won't Scan? Fix the Path Mismatch

Your TV shows are on disk, Sonarr says it downloaded and imported them, but the library tab is blank, episodes show as missing, or a manual scan finds nothing. Nine times out of ten this isn't a Sonarr bug, it's a mismatch between the folder path Sonarr thinks it's using and the folder path its container can actually see.

Rather not chase down volume mappings by hand? SparkBox wires Sonarr, Radarr, and Jellyfin to one shared media path automatically, so this class of "container can't see the file" bug can't happen in the first place. See the walkthrough →

Why this happens

Docker containers don't see your host's file system directly. A docker-compose.yml volume line like ./tv:/data/TV tells Docker "take the host folder ./tv and make it appear at /data/TV inside the container." Sonarr's root folder setting only cares about the second half of that, the path inside the container. If that inside path doesn't match what you typed into Sonarr's UI, or doesn't match what a different service (like Jellyfin) is using for the same physical files, you get a library that looks empty, imports that silently fail, or a root folder that Sonarr flags as unhealthy.

This shows up in two common flavors:

• The arr containers' bind mount is missing a segment. For example, the compose file mounts MEDIA_ROOT:/data, but Sonarr's root folder is set to /media/TV, a path that was never created inside that container. Sonarr can't see it, so the library stays empty even though the host folder is full of episodes.
• Jellyfin (or another media server) is bound to a different path than the arr stack. If Sonarr writes files to /data/TV inside its container, but Jellyfin's compose file binds the same host folder to something like /media/tv, Jellyfin either can't find the new episodes or Sonarr can't hardlink into Jellyfin's library folder at all, forcing slow full copies instead of instant hardlinks (or failing outright).

Step 1: Confirm the symptom is really a path mismatch

1. Open Sonarr, go to Settings → Media Management → Root Folders, and note the exact path shown (e.g. /data/TV or /media/TV).
2. Check whether Sonarr shows a warning icon next to that root folder. A warning here usually means the path doesn't exist inside the container, or exists but is empty.
3. Open a shell inside the Sonarr container and list that exact path.

docker exec -it sonarr ls -la /data/TV

If that command returns "No such file or directory," or returns an empty folder while you know episodes exist on the host, you've confirmed the mismatch. The path saved in Sonarr's settings and the path your container actually has mounted are two different things.

Step 2: Check your docker-compose volume bindings

Open the compose file for your arr stack and look at the volume lines for Sonarr (and Radarr, if you run it). You're looking for the host path (left of the colon) and the container path (right of the colon).

volumes:
  - ${MEDIA_ROOT}:/data

Then compare that to what Sonarr's root folder is set to. If the compose file binds to /data but Sonarr's root folder says /media/TV, that's the bug: nothing inside the container's mount ever created a /media path, so Sonarr is pointed at nothing.

Step 3: Align everything to one canonical bind path

The fix that actually holds up long-term is to stop letting each service invent its own internal path for the same physical folder. Pick one canonical bind, for example MEDIA_ROOT:/data, and use it everywhere: Sonarr, Radarr, and your media server.

1. In your .env or compose variables, set MEDIA_ROOT to the actual host folder containing your media (e.g. /mnt/storage/media).
2. Update every arr service's volume line to bind ${MEDIA_ROOT}:/data, not a hardcoded path and not a different segment like /media.
3. Inside Sonarr, set the root folder to /data/TV (and for Radarr, /data/Movies). These are the paths that should now genuinely exist inside the container, because they're subfolders of the MEDIA_ROOT you just bound to /data.
4. If a bootstrap or setup script on your system is responsible for creating and registering root folders automatically, make sure it uses the MEDIA_ROOT variable directly rather than a hardcoded default, so this still works if you've customized where your media lives on the host.

docker exec -it sonarr ls -la /data/Movies /data/TV

Both should now list your actual media files. If they do, Sonarr's root folder health check should clear on its own the next time you open Settings → Media Management.

Step 4: Fix Jellyfin's (or your media server's) volume binding too

This is the step people miss. Even after Sonarr's own path is fixed, if your media server's compose file still binds the same host folder to a different internal path, you'll get a second version of the same bug: Sonarr imports the episode fine, but your media server never sees it, or Sonarr can't hardlink the file into the library at all because the two containers disagree about where it lives.

1. Open the compose file for your media server (Jellyfin or otherwise).
2. Change its volume binding for the media library to the same host path and, ideally, the same internal container path as your arr stack, e.g. ${MEDIA_ROOT}:/data.
3. Recreate the container so the new binding takes effect.
4. Point your media server's library folder to /data/Movies and /data/TV to match.

docker compose up -d jellyfin

Step 5: Trigger a rescan, don't re-download

Once every container agrees on the same path, you don't need to touch your downloads again.

1. In Sonarr, go to your root folder and click Rescan (or rescan an individual series if only one show is affected).
2. Confirm the root folder's health warning is gone in Settings → Media Management.
3. Refresh your media server's library so it picks up the same files at the newly-aligned path.

If files still don't appear after a rescan, double-check permissions on the host folder, an unreadable folder inside a correctly-bound container produces the same symptom as a wrong path.

Frequently asked

Why does Sonarr's library show no episodes even though the files are on disk?

Sonarr can only see what's inside its own container. If the host folder holding your TV shows is mounted to a different path than the one saved as Sonarr's root folder, the app is looking at an empty or wrong directory even though the real files exist on your host machine.

Why did this break after I set up Jellyfin?

It's common for the *arr stack and the media server to be mounted with different bind paths in their docker-compose files. When Sonarr imports a file at one path and Jellyfin looks for it at another, Jellyfin won't show the episode, or Sonarr can't hardlink into Jellyfin's folder at all.

Do I need to re-import my whole TV library after fixing this?

No. Once the root folder path matches the container's real mount, a manual library scan (or Sonarr's "Rescan" on the series/root folder) will pick the existing files back up without re-downloading anything.

What is MEDIA_ROOT and why does it matter?

MEDIA_ROOT is the single host folder that everything, Sonarr, Radarr, and Jellyfin, should be pointed at. When every container binds MEDIA_ROOT to the same internal path (like /data), there's no room for the containers to disagree about where a file actually lives.