Hi - Recently when I do a forced rescan, Roon seems to take forever. It seems to get stuck at a particular file e.g., 9005 files scanned. Normally I would think that all files have been scanned but the little thing that goes round and round at the top is still rotating. I don't know if this is relevant but it started about the time I began looking for missing Cover Art and adding them to the album folder. I am running off a NAS (always have) and this is the first time I have encountered this issue. Thanks.
Describe your network setup
I have a tp-link router and a ASUSTOR NAS. I have about 70,000 audio files on this NAS. In fact the line above "9009 files scanned" is "70909 files imported".
When a forced rescan appears to stall on a specific file count, it can indicate that Roon is waiting on a delayed response from the NAS or encountering a file that takes unusually long to process.
To rule out a temporary indexing hang, could you please try the following:
Restart your Roon Server
This clears the current scanning pipeline and resets the import process.
After the restart, perform another forced rescan
Let us know whether it still pauses around the same file number or if the scan completes normally.
If the issue repeats, we’ll take a deeper look into the diagnostic data.
Sorry, I forgot to mention - even after rebooting the computer, the force rescan starts automatically (it is greyed out). Maybe you meant something else when you said "“Restart your Roon Server”.
Thanks for the update! From a fresh diagnostic report, we’re seeing a few hiccups around the following files:
URL Z:\AURENDER\Various Artists\2xHD Hi Res System set-up [192kHz · 24bit]\05-Audiophile Hi-Res System setup-Voice & Jazz group - Studio Recording.wav: other error
Unexpected Failure While Opening Sound: Z:\AURENDER\Various Artists\2xHD Hi Res System set-up [192kHz · 24bit]\06-Audiophile Hi-Res System setup-Harp, Ref_ Timbre - Vintage Concert Hall.wav: System.Exception: failed to open location 'Z:\AURENDER\Various Artists\2xHD Hi Res System set-up [192kHz · 24bit]\06-Audiophile Hi-Res System setup-Harp, Ref_ Timbre - Vintage Concert Hall.wav': FileNotFound
Warn: [zoneplayer] couldn't play URL Z:\AURENDER\Various Artists\2xHD Hi Res System set-up [192kHz · 24bit]\03-Audiophile Hi-Res System setup-12 guitars.wav: other error
Warn: [zoneplayer] couldn't play URL Z:\AURENDER\Various Artists\2xHD Hi Res System set-up [192kHz · 24bit]\01-Audiophile Hi-Res System setup-Presentation.wav: other error
If you could, I would try temporarily removing all our Audiophile and Various Artists folders from your watched folders temporarily, and see if Roon still gets stuck analyzing.
It may be worth having your files’ health analyzed using a third-party program - many Roon users enjoy using dbpoweramp for such tasks.
Yes, I’d try temporarily relocating the entire subfolders containing these albums to a location not being watched with Roon, and see if you experience the same issue.
You can always re-add each album back in one by one to test if/when it gets hung up as well.
The latest logs to reach our server indicate that RoonServer/RAATServer don’t have access to the location hosting these files at the moment playback begins:
12/07 16:38:36 Error: [zoneplayer] Unexpected Failure While Opening Sound: Z:\AURENDER\Various Artists\2xHD Hi Res System set-up [192kHz · 24bit]\04-Audiophile Hi-Res System setup-Percussion 1, Ref_ Voice & Bass - Concert hall.wav: System.Exception: failed to open location 'Z:\AURENDER\Various Artists\2xHD Hi Res System set-up [192kHz · 24bit]\04-Audiophile Hi-Res System setup-Percussion 1, Ref_ Voice & Bass - Concert hall.wav': FileNotFound
at Sooloos.Audio.MediaDecoderAudioSignal..ctor(String location, CacheHints cachehints)
at Sooloos.Broker.Transport.AudioSignalFactory.<>c__DisplayClass0_0.b__0(CallingThread cx)
It’s worth noting that this failure originates with the operating system - Windows was unable to access that filepath when RoonServer requested it. Roon and Windows otherwise accessed this filepath reliably, which means this is an intermittent issue.
This occurs most commonly in this setup because 1) the storage is mapped as a drive letter (less stable than UNC) or 2) was briefly unavailable due to power-saving features, permissions, security features, etc.
Since you mentioned you’re testing, we’ll watch for your response, but hopefully the above is helpful.
Hi - I think I understand the issue (but not the cause). Roon seems to have a problem when I mass change the meta data on EXISTING files.
I have been trying to standardize the meta data and have added Cover Art to hundreds of existing albums. Similarly, I have changed filenames to <Track #> - -
There is a new album on my NAS but Roon has not picked it up after about 15 minutes. The Storage section under Settings says “Watching for new files in real time. 70,790 tracks imported”. Is there a time for Roon to detect new files? I would hate to Force Rescan every time I have a new album. This feature used to work once upon a time with my NAS. Thanks.
OK, maybe I solved it. Even after I exit Roon, it appears I need to also quit the Roon Server from the System Tray. I never realized it was still running. After I quit, waited a few seconds and restarted the app, it imported the new album. Fingers crossed.
Still don’t know what to do about the fact that Roon seems to have a problem when I mass change the meta data on EXISTING files (see above). Thanks!
The 5-hour import time is healthy. For larger edits across tens of thousands of tracks, it’s best to temporarily disable your watched folder - Perform all metadata + rename operations (let the NAS sit for a few, then reboot as well , that may help with speed) - then reenable your watched folder in Roon.
Glad to hear you’re back up and running. Happy listening!
