Slow scanning of music files on NAS with Roon Server (ref#T2SFNQ)

What app are you having the slowness issue with?

· Roon

What kind of performance/speed issue are you experiencing?

· Other

Please try to reboot your Roon Server

· No, the issue is still the same even immediately after a reboot

Please try to reboot your networking gear (Router/Switches/etc.)

· No, the issue is still the same even after a reboot

Is there any change in behavior if you try to navigate to Roon Settings -> Library and set both Background and On-Demand Audio Analysis to Throttled or Off?

· No, the issue is still the same

Does the issue happen on multiple Roon Remotes (controllers) or just one?

· Issue happens on multiple remotes

Router Domain Name System (DNS) change

· I was able to change my router's DNS servers but it did not help

What is the operating system of your Roon Server host machine?

· Windows

Describe the issue

My music is stored on a NAS (QNAP TS-451D2, 1 GB NIC) with currently over 300,000 files.

My Roon Server is running under Windows 11 on an HP EliteDesk 800 G4 Mini-PC (Intel Core i5 8500T, 32 GB DDR RAM).
My storage is the music file share on the NAS.
Scanning is extremely slow, it took a week to scan approx. 65 % of the files.

Describe your network setup

ISP: 1&1 (Germany) (250 Mbps Download)
Router: FRITZ!Box 5690 Pro

Hello @Roonee,

Thank you for testing the DNS change. We have requested the diagnostic logs from your Roon Server — please get it back online and we will review the diagnostic.

That said, it is worth noting that 300,000+ files is an exceptionally large library, and the initial scan of a collection this size will naturally take significantly longer than average. We will review the logs and let you know what we find.

Hi @vadim,

the server is online all the time. Is there anything i can do regarding the logs?

Hello @Roonee,

Thank you for keeping the server online - we have reviewed the diagnostic logs and have a clear picture of what is happening.

The logs confirm your Roon Server is healthy and the NAS connection is stable. There are no I/O errors or SMB failures. The slowness is a performance issue, not a fault.


Finding 1 - The NAS directory scan is extremely slow and variable

This is the primary cause of the week-long scan. Every hour, Roon re-enumerates the full \\QNAP\Musik\MP3 tree to detect new or changed files. For a 300,000+ file share over SMB, the logs show this single operation taking anywhere from 21 minutes to 9.4 hours in different runs:

  • 06/07 ~02:00 → scan finished in 9 hours 23 minutes
  • 06/07 ~15:53 → scan finished in 4 hours 22 minutes
  • 06/08 ~06:39 → scan finished in 5 hours 7 minutes
  • 06/08 ~09:53 → scan finished in 27 minutes

Two back-to-back scans of exactly the same data differing by a factor of 12× points directly at the QNAP NAS itself - most likely HDD spindown (drives going to sleep between scans, then needing 10–15 seconds to spin up per directory access across thousands of folders) or the QNAP being busy with its own internal tasks (Cloud Backup, antivirus, File Station indexing, Download Station) competing for disk and CPU.

Action: In QNAP Storage Manager, please disable drive hibernation/sleep for the volume holding your music. Also check whether any QNAP-side tasks (Cloud Backup Station, antivirus, multimedia indexing) overlap with the hours Roon is scanning.


Finding 2 - Audio analysis has a backlog of ~332,000 tracks

At the time of log capture the audio analysis queue contained 332,810 tracks and was draining at approximately 10 tracks per minute. Each track requires Roon to stream the entire audio file from the NAS to compute loudness data:

  • AAC tracks: 18–40 seconds each
  • FLAC 16-bit: 11–44 seconds each
  • WAV/FLAC 24-bit: 28–59 seconds each

Go to Settings → Library → Background Audio Analysis and set it to Fast (not Throttled - Throttled is intentionally slower). This allows analysis to run at full speed across more hours.


Finding 3 — File discovery is already complete

All ~328,000 files were already imported by the time the earliest available log was written (June 7, ~00:30). The “65% scanning” progress you were observing reflects audio analysis completion, not file discovery — the files themselves are all in Roon’s library.

Summary

The QNAP TS-451D2 is powered by an Intel Celeron J4025 launched at Q4’19 — a dual-core entry-level processor running at ~2.0 GHz. At 300,000+ files, the NAS CPU itself becomes the bottleneck: serving SMB directory enumeration at this scale requires processing tens of thousands of metadata requests, which can saturate a Celeron J4025 entirely — especially if QNAP’s own background services (multimedia indexing, Cloud Backup, Download Station) are competing for CPU time at the same moment. This explains why two consecutive scans of identical data can differ by a factor of 12×. I do not see how we can speed up this process from the Roon side.
Please let us know if you have any other questions or concerns regarding this matter.

Thank you very much for your very detailed and professional analysis.

All settings have always been set like you suggested, checked the QNAP tasks okay.

Set it to “Unscheduled - Fast (6 cores)” now.
Server CPU load is good (between 10 and 80 %)

Fully agree. roon is running very smoothly since some days now.

Hello @Roonee,

Great to hear Roon is running smoothly now! With a library of 300,000+ files the initial analysis will always take some time, but it sounds like everything is on track. Feel free to reach out if anything comes up.

Unfortunately it looks like there’s still something wrong.

I thought that after the initial analysis only new files would be scanned and added, but now I see this:

EDIT: I have deactivated the QNAP storage now and will replace it by a USB drive connected to the roon server.

Let me know when I shall activate the QNAP storage again for troubleshooting.

Hi @Roonee,

Sounds good, let us know how things perform via the external drive. Overall, though, I would still consider what @vadim has mentioned above in regard to the CPU power of your NAS and potentially consider a more powerful machine to host your library. :folded_hands:

Hi @benjamin ,

it looks like the external drive is a sufficient solution, and currently I see no need to upgrade the hardware. :slightly_smiling_face:

Hello @Roonee,

That’s great news - thank you for the update.

This outcome makes sense: a USB 3.0 drive attached directly to the Roon Server eliminates the SMB enumeration overhead entirely. Local directory scans that took hours over the network complete in seconds, and audio analysis can stream files at full disk speed instead of being limited by the NAS CPU.

We’ll go ahead and close this thread, but feel free to reach out if anything else comes up. Enjoy the music!