Fixing Media Path Mounts When Aurral Cannot See Your Music

Two independent things that people assume are one

The Lidarr integration has two halves. Aurral connects to the Lidarr API, and Aurral reads the files at the paths Lidarr reports. The API half can succeed completely while the file half fails, and the symptom looks like a broken install rather than a mount problem.

That split is why an empty library with a green connection status is a completely normal state, and why checking the connection tells you nothing useful here.

Rule one: same host path, same container path

Both containers must mount the same host directory at the same container path. The recommended layout is /data in both, with a Lidarr root folder like /data/music.

If Aurral mounts /srv/media as /data but Lidarr mounts it as /music, Lidarr reports paths that do not exist inside Aurral and nothing can be indexed.

Diagnosing it in the right order

Run the storage checks before changing anything. They check storage, downloads, Lidarr files, path mappings and playback in one pass and report the exact path that failed, which saves guessing.

The Lidarr library section of that check reads a track from an artist inside a root folder. If no artist sits inside any root folder, it reads a track from an artist outside them and reports that a root folder change left that artist behind.

1. Open settings and run the storage checks.
2. Read the failing section rather than the summary.
3. For a Lidarr failure, compare the path Lidarr reports with the path inside Aurral.
4. For a permissions failure, check PUID and PGID against the host user.
5. Fix, then run Refresh in the library and wait for the scan to finish.

Remote path mappings, and their limit

A remote path mapping tells Aurral that the path Lidarr reports corresponds to a different path inside Aurral. Set Applies to Lidarr. This is the fix for Windows hosts and for mismatched container layouts.

It only helps Aurral read the files. Navidrome still has to scan the same folder itself, otherwise Flow playlists exist but their tracks resolve as unavailable.

When a track shows as unavailable instead of missing

A track with no file stays in the list but cannot play, and missing album tracks appear dimmed. That distinction is deliberate: the metadata exists, the file does not.

If a whole album shows 0 available tracks while its artist page lists every release correctly, Show available music only is on in Lidarr settings. Turning it off lists the whole discography with availability counts.