· Roon version: 2.62 build 1641 Core running on NAS Search intermittently fails daily within minutes Artist pages slow Artist images missing Playback from Qobuz unaffected if the album is already added to library NAS reboot did not resolve issue All clients affected (Mac + iPad)
Tell us about your home network
· Roon Server running on QNAP, Wired directly into router, Roon control via MacBook Pro over wifi.
Having a library of nearly 190,000 tracks is an impressive achievement, but it puts your QNAP in the “High Density” category for Roon. This essentially means your NAS is working overtime to manage the sheer volume of metadata and search indexing required for a collection of this size.
Based on your current setup and the symptoms described, we are seeing a “perfect storm” of two specific factors:
The RAM-to-Library Ratio
Your QNAP currently has 8GB of RAM. While this is great for standard NAS tasks, it is the absolute bare minimum for a Roon library approaching 200,000 tracks.
Roon keeps a significant portion of its database in the system memory (RAM) to ensure that search results and artist pages appear instantly. When the library outgrows the available “breathing room” in the RAM, the system starts swapping data to the hard drives, which results in the intermittent search failures and missing images you are experiencing.
Known Memory Consumption Bug
Our R&D team is currently finalizing a fix where Roon is consuming more memory than intended. This bug hits large libraries particularly hard.
To get your performance back to where it should be, you have two primary options:
Hardware Upgrade (Recommended): If your QNAP model allows for it, increasing your RAM to 16GB or 32GB would be the single most effective way to stabilize your experience. This provides the physical space Roon needs to manage your large database regardless of any software bugs.
Wait for the Optimization Patch: We are working on a software update specifically designed to optimize memory management on Linux-based cores. While this will definitely help, 8GB will likely remain a bottleneck for a library of your size even after the fix.
Add 32GB of RAM and the same search issues remains. FYI I have not added significantly more titles to my music collection via mu library or the Qobuz service I use. So is the outcome wait for the patch?
Thanks for the update! From your account admin, we can see about 156k tracks identified, with a total number of tracks in your library being ~189k. That leaves around 30k tracks unidentified within Roon, which is quite a large number.
I’d try to edit some of the file metadata to see if you’re able to get them properly identified. Otherwise, we are confident that our work around memory management should help.
After a full clean reinstall (all data/cache removed, recycle cleared) and upgrading to 32GB RAM, the issue persists.
Search and metadata work briefly (~5 minutes), then fail with “Can’t connect to Roon Search,” and new albums (e.g., 7 tracks) remain at 0 identified. This occurs both before and after restoring from backup.
Roon Server works correctly on another machine on the same network, so this appears specific to the QNAP environment.
Would the connection instability (search/metadata failing after initial success) be related to the known memory bug you mentioned, or is this likely a separate issue?
Just checking in on your setup, are you using multiple network interfaces on your QNAP? I wonder if a network interface goes down and can cause such symptoms, considering the other PC on the network doesn’t experience this issue.
@benjamin
I disconnected Qobuz and closed the roon remote app.
Then stopped the roon server on the QNAP.
I started the roon remote app, followed by starting the roon server on the QNAP.
Eventually the roon app connected. Upon the connection the “Adding music to Library” was spinning. Now 80 tracks, 80 added 0 identified.
Been spinning for 20 minutes and nothing has been added.
Sorry to hear you’re still having issues. We’d be happy to take another look, if you could please use the directions found here and send over a set of fresh Roon Serverlogs to our File Uploader? Once logs have been uploaded, please let us know so that we can check the server for your files, thanks!
Hi @benjamin
The log fils have been uploaded. Please note I uploaded twice. The first is from following the overview steps, and the second is using the “Ambulance” button on the QNAP server.
Since clients on the same local network can access these services without issue, the router and ISP are routing traffic correctly. The blockage is localized to the QNAP’s adapter or virtual software.
A few next areas to check/troubleshoot:
If Jumbo Frames are enabled, the network adapter can send packets that are too large for the external internet to handle without fragmentation. This often results in local traffic working perfectly while secure outbound HTTPS connections (like Roon’s metadata APIs) time out completely.
Open Network & Virtual Switch on the QNAP.
Go to Interfaces and check the physical adapter being used.
Ensure the MTU is set to the standard value of 1500 (not 9000).
By default, the QNAP likely uses the local router's IP address to resolve domain names. If the router's DNS cache becomes overwhelmed or has slow response times for heavy API traffic, requests will fail.
In Network & Virtual Switch, find the active interface.
Edit the configuration to use manual DNS rather than acquiring it automatically.
Set the Primary DNS to 1.1.1.1 (Cloudflare) and the Secondary DNS to 8.8.8.8 (Google).
In some network configurations, Linux-based systems attempt to route API traffic over IPv6. If the local network or ISP does not fully or properly support IPv6, it causes long connection hangups before the system falls back to IPv4.
Go to Network & Virtual Switch > Interfaces.
Locate the active adapter and find the IPv6 tab or settings section.
Turn IPv6 off entirely so the system only utilizes IPv4.
Lastly, built-in security software can sometimes actively inspect or throttle high-frequency HTTPS calls.
Check if apps like QuFirewall, Malware Remover, or QVPN are running.
Temporarily disable them to see if the metadata begins populating and searches complete. If performance recovers, exceptions will need to be added for the Roon application or its required domains.
@benjamin
Thank you for these trouble shooting steps. Most I have covered before reaching out to roon support.
After the RAM upgrade the performance of roon remains slow. Especially once Qobuz is added to roon.
Searches are faster without Qobuz, but the playback between tracks in my library (not Qobuz) have an extensive delay between them. Trying to play an album for the first time can take nearly 45+ seconds before it even begins to play and the time between track average 10+ seconds before the next track starts.
Once Qobuz is added to roon searches take longer, meaning the preview can take up to 45+ seconds if it works. This is for a known album on Qobuz but not in my library or liked in Qobuz.
If it is something with the router it was something done with a router update as I have not changed any router settings before the issue initially started.
