Roon unable to find music files after Qnap version 2.65 update (ref#ATHS4Q)

[Marcos_Oliveira]

Hi! What’s not quite right with Roon?

· Music won’t play or issues with my library

Music won’t play or issues with my library

· Local files won't import or appear

Tell us what's going on

· Roon unable to find my music files after installing version 2.65 on a Qnap TVS-882

Tell us about your home network

· Ethernet using Cisco switches. Cat-6 cables. Wi-fi with Ubiquit UniFi.

[BlackJack]

It is unlikely that your music is stored in /container/... unless you copied it there recently. If not, either copy your music where Roon looks for it or recreate the Docker Application with corrected paths pointing at where your music actually exists.

[Marcos_Oliveira]

[Marcos_Oliveira]

[Marcos_Oliveira]

[Marcos_Oliveira]

Thanks for your help. But what would be the right volume mapping? I assume that on the left side I have to write the host name of the folder, shall I use NAS…/FLAC fora… or DataVol2/FLAC fora…?

[yo3fxy]

if you want to be able to filter your music by storage location, than you will need to add them manually and delete the pre-defined /Music location; alternatively, instead of /Music prefix use something like /myMusic and don’t even define a /Music volume mapping

/share/Container/roon → /Roon
/share/Container/roon-backups → /RoonBackups

/share/Flac fora do Sooloos → /Music/fora-do-Soolos
/share/Sooloos → /Music/Sooloos

[Marcos_Oliveira]

Thanks. I tried as you suggested, but it still cannot find my files.

[BlackJack]

You could try "/DataVol2/FLAC fora do Sooloos:/Music" or "/share/DataVol2/FLAC fora do Sooloos:/Music" in the Docker Compose. But this is all just guessing on our part, you’re the one sitting in front of your NAS holding your music. So you’re in the best position to lookup the correct path information. See also:

https://forum.qnap.com/viewtopic.php?t=133951

[yo3fxy]

“minor” typo in the “.. fora do Sooloos” volume mapping, if you didn’t spot it already - it should be FLAC (all capital letters) not Flac; sorry about that

/share/FLAC fora do Sooloos → /Music/fora-do-Sooloos

[connor]

Hi @Marcos_Oliveira,

Our diagnostics servers show a network share associated with your most recently active Roon Server; from a glance, it matches the location described in this thread.

Are we correct in assuming that you’ve successfully mapped this file location to the containerized server now? Please reach out if we can assist further. Thank you!

[Marcos_Oliveira]

I tried everything and nothing worked. Here are the last event log

oonserver | Roon Docker image 1.0.6 starting.
roonserver | No existing RoonServer install found under /Roon/app/RoonServer.
roonserver | Resolved ROON_INSTALL_BRANCH=‘production’.
roonserver | No install present; installing branch ‘production’.
roonserver | Downloading from https://download.roonlabs.net/builds/production/RoonServer_linuxx64.tar.bz2…
#=#=# # #### ####### ########## ############# ################ ################## ####################### ########################## ############################# ################################# #################################### ####################################### ########################################### ############################################### ################################################## ###################################################### ######################################################### ############################################################ ################################################################ #################################################################### ############################################################################################################################################# 100.0%
roonserver | Extracting to /Roon/app…
roonserver | RoonServer installed successfully.
roonserver | Image: 1.0.6
roonserver | Branch: production
roonserver | Roon: 2.65 (build 1653) production
roonserver | 00:00:00.000 Info: get lock file path: /tmp/.rnsgem0-
roonserver | 00:00:00.002 Info: GetLockFile, fd: 74
roonserver | 00:00:00.002 Info: GetLockFile, res: 0
roonserver | 00:00:00.003 Trace: Nope, we are the only one running
roonserver | Initializing
roonserver | Started
roonserver | [Sentry] Initialized for RoonServer (appliance), release: roonserver@206501653+production
roonserver | aac_fixed decoder found, checking libavcodec version…
roonserver | has mp3float: 1, aac_fixed: 1
roonserver | Running
roonserver | System.Net.Sockets.SocketException (104): Connection reset by peer
roonserver | at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
roonserver | at System.Threading.Tasks.ValueTask`1.ValueTaskSourceAsTask.<>c.<.cctor>b__4_0(Object state)
roonserver | — End of stack trace from previous location —
roonserver | at Sooloos.RnetJsonClient.<>c__DisplayClass65_0.<_BeginRead>b__0(IAsyncResult ar)

[vadim]

Hello @Marcos_Oliveira,

I understand how frustrating this volume mapping process in Docker can be.

Let’s clear up how QNAP structures its folders so you can find the exact path you need.

How QNAP Folder Paths Work

Behind the scenes, QNAP uses a Linux operating system. In this system, all of your top-level shared folders live under a master directory called /share/.

When you create a shared folder (like your FLAC fora do Sooloos folder), QNAP places it on a specific hard drive volume (like CACHEDEV1_DATA, DataVol1, or DataVol2) and links it inside that /share/ directory. Because Docker is isolated from the rest of your NAS, it cannot use network names; it requires the absolute, physical path starting from /share/.

How to Find Your Exact Absolute Path

Instead of guessing, you can ask QNAP to tell you exactly what the path is:

1. Open your QNAP Control Panel.
2. Navigate to Privilege > Shared Folders.
3. Locate your FLAC fora do Sooloos folder in the list.
4. Click the Edit Properties icon (it looks like a piece of paper and a pencil) under the “Action” column for that folder.
5. In the properties window, look at the Volume and the Path information.

Your absolute path combines these elements. Depending on your specific QNAP configuration, it will look like one of these two formats:

• - /share/DataVol2/FLAC fora do Sooloos:/FLAC fora do Sooloos
• - /share/FLAC fora do Sooloos:/Music

Updating Your Docker Configuration

Once you have the exact absolute path from the Shared Folders properties, edit your Container Station configuration YAML

1. Go to the volumes: section of your configuration.
2. Replace the generic music path with your exact path. Make sure there are no typos, and remember that Linux is completely case-sensitive (so FLAC is different from Flac).
3. Save the changes and recreate/restart the container.

Once the container boots up with the correct absolute path, you will be able to go into Roon Settings > Storage, add the /FLAC fora do Sooloos folder, and Roon will instantly see all of your files.

[Marcos_Oliveira]

Thank you. But it didn’t work either. Please, check what is my mistake.

Here you have the screens from my Control Panel

Now, you have the docker configuration

services:
roonserver:
image: Package roonserver · GitHub
container_name: roonserver
network_mode: host
environment:

• ROON_INSTALL_BRANCH=production
• TZ=America/Sao_Paulo
  volumes:
• /share/Container/roon:/Roon
• “/share/DataVol2/FLAC fora do Solos/FLAC fora do Solos:/Music”
• /share/Container/roon-backups:/RoonBackups
• /share/DataVol2/Sooloos:/music
  restart: unless-stopped
  logging:
  driver: local

What correction do I need to make?

[Marcos_Oliveira]

I corrected a typo “Solos” instead of “Sooloos” and the problem remains the same.

[Arindal]

@Marcos_Oliveira

• /share/Container/roon:/Roon
• “/share/DataVol2/FLAC fora do Solos/FLAC fora do Solos:/Music”
• /share/Container/roon-backups:/RoonBackups
• /share/DataVol2/Sooloos:/music

Potential sources of errors:

• the alias names for the 2 folders inside the container are set to /Music and /music - I would avoid this. Call one /Music (the main one) and the other /Music2 or something like that
• try the same path, but leave out the /DataVol2 logical volume name as a folder name
• correct the syntax of the share path for the main /Music folder, the /FLAC fora do Sooloos part exists twofold

So I would try, without the volume´s logical name in the path (as it seems to work with /Container already):

/share/Container/roon:/Roon
/share/FLAC fora do Sooloos:/Music
/share/Container/roon-backups:/RoonBackups
/share/Sooloos:/Music2

If this does not help, you might need to add the volume name as used on system level, for example:

/share/Container/roon:/Roon
/share/CACHEDEV2_DATA/FLAC fora do Sooloos:/Music
/share/Container/roon-backups:/RoonBackups
/share/CACHEDEV2_DATA/Sooloos:/Music2

CACHEDEV2_DATA is just a wild guess from my side. It might well be CACHEDEV1_DATA - you need to figure that out.

Good luck!

[Marcos_Oliveira]

Thank you very much. Problem solved.

One final remark for the Roon team. I lost all editing that I had done on my album database;

[Arindal]

@Marcos_Oliveira Pleasure!

@Marcos_Oliveira

I lost all editing that I had done on my album database;

Did you restore a previous backup? You need to copy the backup data folder from your previous roon installation to the new folder /Container/roon-backups and then run Settings > Backup > Find a Backup > Restore

[Marcos_Oliveira]

Thank you. Problem solved