Hi! What’s not quite right with Roon?
· None of the above quite fits
None of the above quite fits
· App interface looks or behaves oddly
Tell us what's going on
· Roon stuck scanning library
Tell us about your home network
· LAN
How large is your library, and how long has it been scanning? This process identifies music files and then analyses them, which can take a while.
Also, check Settings → Library for skipped files.
Hi Dexter_prog,
Thanks for the logs. The scan is hitting a couple of problem files on each pass, which causes it to abort and restart repeatedly.
Please try the following:
- Go to Settings > Library > Skipped Files and note what is listed there.
- Locate and remove (or move out of your watched folder) these two files:
D:\Desktop\Mp3\The Absence\Mp3\Albums\2007 - Riders Of The Plague\The Absence - 07. (Untitled).mp3- Roon reports this as a corrupt file and cannot read it.D:\Desktop\Mp3\October Tide\Albums\1997 - Rain Without End\00-october_tide-rain_without_end-repack-cd-flac-1997.log.jpg- this appears to be a.logfile with a.jpgextension that Roon cannot load as album art.
- After removing those files, go to Settings > Library > Clean up Library, then force a rescan via Settings > Storage, click the three dots next to your watched folder, and choose Force Rescan.
Thanks, I did all of that (now no more skipped files), cleaned up library. However I can’t force a rescan as it is greyed out ( the sync circle keeps spinning)
Pa: library is about 32k files.
Hello @Dexter_prog,
Since the Force Rescan option is greyed out and the scan is still spinning, please try restarting the Roon Server:
- Locate the Roon icon in the system tray (near the clock in the bottom-right corner of your taskbar)
- Right-click it and select Quit
- Start the Roon server again from the start menu.
Once it comes back up, the scan should resume cleanly with the problem files removed. With a 32k library it may take a little while to complete, so please allow it some time before checking the result.
Let us know how it goes!
I’ve unfortunately already tried that a couple of times, even rebooting my PC (the server). But the behavior is the same. My computer runs 24/7, so I can confirm this scanning is not ending since I opened this thread
Hey @Dexter_prog,
Thanks for the update!
It currently looks like our severs haven’t seen your machine in a day or so. If you could, please bring your Roon Server back online and we’ll enable diagnostic mode for further analysis.
Let us know when your Server is back online and connected, thank you!
sorry, had rebooted the PC and didn’t use Roon yet. Back online now
Hi @Dexter_prog,
Thanks for the update! We were able to review a fresh diagnostic report from your Roon Server, and can see the local scan does finish each time (e.g. “initial scan of D:\Desktop\Mp3 took: 8236 ms”), so this is not what’s leaving the spinner up.
What we do see is, across the entire week the logs show, every 5 minutes:
[identification] scheduler tick: processing queue (count=259) → retry queue has 259 albums but none ready for retry yet
The queue sat at 257 albums on 06/13 and 259 on 06/21, it has not drained a single item in over a week. There is not one identification success anywhere in the logs. As long as that queue is non-empty, Roon shows the spinning “scanning” indicator and greys out Force Rescan, which is exactly the user’s symptom. Removing the corrupt files cleared Skipped Files but had nothing to do with this queue.
The albums in that queue are streaming-service albums (the 166:0: / 121:0: IDs all map to “My Tidal Library” and Qobuz, not local files). Roon can’t finalize them because its calls to its own metadata/identification cloud are intermittently failing:
At least 93 unique TIDAL albums return status code: 404 from Roon’s metadata service (558 total 404 hits), meaning those albums have been pulled from TIDAL’s catalog and no longer exist to be identified.
Let’s see if the following help:
Have the user check Settings > Library > Skipped files and see if it shows the exact “X albums need identification” / unidentified count. If it’s ~259 and they’re mostly TIDAL albums, that confirms it directly.
- Refresh the TIDAL favourites: in TIDAL, the dead (greyed-out / unavailable) favourited albums should be removed and, where possible, re-added from a current catalog entry. Those 404 albums will never identify as-is. You can filter your albums by ‘Unidentified’ to help with this.
- The fix that's most likely to clear the spinner: since the stuck items are streaming-library residue, force a TIDAL library resync (Settings > Services > TIDAL, or toggling the TIDAL storage backend)
- VPN: still worth noting the NordVPN tunnel is in the path and caused the earlier dropouts, but it is not the current blocker.
Hi sorry, where do I find this? “Have the user check Settings > Library and report the exact “X albums need identification” / unidentified count. If it’s ~259 and they’re mostly TIDAL albums, that confirms it directly.”
REgarding Tidal, I noticed sync is successfull in that section. I even clicked the “sync” button and it finalized in less than 1 second.
PS: NordVPN has only been installed a few days ago and not being used most of the time
edit: Tidal shows no unidentified albums to me:
Hi @Dexter_prog,
Could you do a quick test: in Roon, browse to any TIDAL album you don’t already have saved and add it to your library (click the heart/+ icon). Then wait a minute or two.
We found in your logs that Roon has 259 TIDAL albums stuck in an identification queue, and it’s getting 404 errors back from TIDAL for many of them — meaning those albums have been removed from TIDAL’s catalogue and can no longer be identified. Adding a new TIDAL album will trigger a fresh sync, which will help us confirm Roon is picking up changes and point us toward clearing that stuck queue.
Let us know once you’ve done it!
I had actually just done that - Bon Jovi - Slippery When Wet, but the behavior didn’t change
Hello @Dexter_prog
Thanks for testing that. Could you confirm one more thing: did the Slippery When Wet album actually appear in your Roon library after adding it (visible in Albums view), or did it fail to show up at all?
Also, to help us dig into the stuck identification queue, could you export a database backup and upload it to our WorkDrive folder? Steps: Settings > General > Backups > Backup Now (or use your most recent automatic backup), then upload the resulting zip file here: https://workdrive.zohoexternal.com/collection/nocvrfc5b2ddab55140af8640f1d7ce13291e/external. That’ll let us inspect the queue directly and see why those 259 albums aren’t clearing.
the added album shows.
I will upload the backup, however it is 9 gb big. Is that correct?
edit: I have uploaded it
Thank you @Dexter_prog! We’ll have our team take a look.
My apologies, I was referring to the ‘Skipped Files’ section, but actually, there is a different process to obtain this view.
Please navigate to My Tracks, and then filter by ‘available’ :
Then, click the ‘+’ to reverse the filter to ‘unavailable’:
And let us know if all the albums are indeed from Tidal and or Qobuz. Thank you!
there were indeed some tracks (not full albums), from 3 albums. I would say about 20 tracks. I removed those albums completely. However the spinning loading circle is still there
I believe there’s definitely something going on between Roon and Tidal. This might be unrelated to my issue, but flagging just in case:
I was notified in the Home page of a new Deftones album, called Eros (PS: this is not a new album apparently as it was never ever released). I clicked on the first one that was suggested in the Home page for me and for all tracks I got “this track is not available in Tidal”. Then looked at versions and there’s like 10 versions (all probably duplicates/nonexistent) in Roon:
I think I solved by clearing Roon’s image cache:
%localappdata%\RoonServer
deleted:
httpcache_2
images