New album not showing up

[Yayroos]

I've just added a new album to my collection, and I've sorted its metadata and dropped it into the right place, with all the rest of my music under the /artist/album path

as far as i can tell the folder and file permissions are the same as the other albums which are all showing just fine (folders drwxr-xr-x, tracks -rw-r--r--). In the logs it's telling me msg="Scanner: Error loading for. Skipping" error="lstat <path to first track in the folder>: permission denied"

I don't know what I'm doing differently vs last time I added a song, where it showed up just fine.

[rhmatzeka]

lstat only needs search (x) permission on the directories in the path, not read permission on the file itself, so with drwxr-xr-x folders it shouldn't fail on mode bits alone. When it still returns permission denied for one album and not the others, the usual cause is something outside the classic permissions that's different on just those new files:

1. Check as the user Navidrome actually runs as. If it's in Docker, run it inside the container, since the user: / PUID there may not be you:

   docker exec -it navidrome stat "/music/Artist/New Album/01 - Track.flac"

   On the host, namei -l "/path/to/Artist/New Album/01 - Track.flac" shows the owner and mode of every directory along the path, including the artist folder and anything above it.

2. SELinux label (Fedora, RHEL, CentOS, etc.): ls -Z on the new album vs. an album that works. Files that were mv'd from your home directory or Downloads keep their old label (e.g. user_home_t), which a container can't read even though ls -l looks fine. Copying gets a fresh label, which is often why "it worked last time". Relabel with chcon -R -t container_file_t "/path/to/New Album" or add :z to the music volume mount.

3. ACLs: if ls -l shows a + after the permissions, check getfacl on the folder and the files.

After fixing it, run a scan again (or a full scan) and the album should show up.

[Yayroos]

Was the SElinux thing. Confused because I definitely did copy the files in, not move. :z is also already on the mount, but evidently didn't like it

thanks!