Roon Server stuck on rescan 1/173

Hi! What’s not quite right with Roon?

· Stuck on rescanning

Issues with my library

· Local files won't complete import

Tell us what's going on

· Hi Roon Support team,

I am experiencing an issue where my Roon Server is permanently stuck on the message Rescanning files: 1/173. "Adding music to library" shows as Complete.

This issue originally appeared on my previous dedicated NUC running Roon ROCK. I recently migrated my Core to a Docker container on my QNAP NAS by restoring a database backup, and the exact same issue carried over to the new setup. This leads me to believe it is an issue with specific files in my library or a persistent database glitch, rather than an OS or hardware issue.

My current setup:

Core Machine: QNAP TVS-872XT

OS: Roon Server running in Docker (Official ghcr.io/roonlabs/roonserver:latest image)

Specs: 64GB RAM

Database storage: M.2 NVMe SSD

Music storage: Local NAS drives (mapped as volumes in Docker)

Library size: ~350,500 tracks / ~21,500 albums / 5,000 artists

Troubleshooting steps already taken:

Restarted Roon Server multiple times.

Fully migrated to a completely new hardware architecture and OS (from ROCK to QNAP Docker), but the issue persists after restoring the database.

The system is incredibly fast and responsive otherwise, it's just this background process that never completes.

Could you please help me identify which files are causing the scanner to hang, or advise on how to clear this stuck scanning state? If you need me to upload logs, please let me know.

Thank you,
Baard

Tell us about your home network

· Ubiquiti UniFi UCG-Fiber

Hey @Baard_Ole_Grotta,

Thanks for writing in and for sharing your report! A few next steps to try:

  1. In Roon Settings → Storage, note the watched folder path
  2. Temporarily disable that storage location and re-enable it — this forces a fresh scan queue rebuild
  3. If it still sticks at 1/173, try removing the storage location and re-adding it (your library metadata stays in the DB; Roon just re-links files)

In addition to this, we noticed a handful of corrupt files from a fresh Roon Server diagnostic report. If you navigate to Roon Settings > Library > Clean up Library, do you see any errors across your files?

It may be worth reviewing your skipped files as well. Here is an example:

Warn: [storage] [directory] Failed to extract audio format from '/Musikk_Arkiv/M/Maria Solheim/(2002) Behind Closed Doors/08 - Maria Solheim - Richard - Behind Closed Doors.mp3': CorruptFile 

It may be worth removing or reparing any corrupt files to see if that may help.

Thank you!

Hi again,

Some additional troubleshooting information:

  • Clean Library: I ran the “Clean Library” function in Settings, and it reported absolutely zero errors.

  • File Integrity: I have spot-checked files directly outside of Roon to ensure they aren’t corrupted. For instance, playing a Maria Solheim track directly from the source file works perfectly fine without any issues.

Given that the library is clean according to Roon’s own maintenance tools and the files themselves are healthy, it really seems like the scanner is just getting tripped up on something very specific in the background.

Hi @Baard_Ole_Grotta,

Thank you for your post and for the clarification.

Can you share a screenshot of your Settings → Library page? It could also mean that Roon’s struggling to ingest artwork, analyze waveforms, or work through some custom file tags. There’s a /variousartists folder in logs that appears to host a compilation album named Britpop, The Greatest Anthems that Roon is repeatedly analyzing.

Try turning On-Demand Audio Analysis to “Off,” Background Audio Analysis to “scheduled,” and then restarting RoonServer. Do you still see this rescanning occurring after startup?

After changing the settings you recommended and removing the Britpop album, the rescanning still continues. Now 1/149.

Hey @Baard_Ole_Grotta,

Thanks for the update, and I’m sorry to hear the scanning is still ongoing. The good news is that a fresh diagnostic report are clean of any CorruptFile or Failed to extract audio format errors, so no files need to be removed or repaired.

It does appear that the updatemetadata queue may be stuck. Every few minutes, the log shows:

[updatemetadata] Flush: pending adds=72052, pending removes=0, current q size=0
[updatemetadata] _ReadyForFullRefresh: time_past_due=-3.11:xx:xx, is_within_window=False, should_update=False
[updatemetadata] Flush: not ready for full refresh (is_ready=False), keeping 72052 queue additions...

It seems 72,052 pending metadata additions are frozen in the queue. The system is repeatedly checking whether it’s ready to flush them to Roon’s metadata service, and repeatedly deciding “not yet.” The time_past_due value is negative (meaning the 7-day refresh window hasn’t yet elapsed since the last update on 05/04/2026). So the queue just sits there.

As a small side test to troubleshoot - head to Settings → Library → Clear Cached Images and then restart Roon.

It very well may resolve itself if you keep your server running over the next few days and see if it clears itself over the next flush, which is around Monday or so.

Let us know how things look over the weekend and into early next week. :folded_hands:

Seems to be gone now.