Using wired 1GB Ethernet
Netgear GS108 Switch
Linksys 1900ACSv2 Router
Library
The Library is connected over SMB protocol
The SMB Server is a Linux machine serving drives over SAMBA
Connected Audio Devices
Raspberry Pi 4 running Ropieee XL
Connected over TPLink Powerline Ethernet Extender
ifi ZEN DAC
Number of Tracks in Library
68,480 Tracks
Description of Issue
I had a database crash and had to restore from an older backup.
After restoring from the backup of course Roon had to re-analyze about 6 months of additions.
When starting up the storage scan runs to completion.
In the Library section there are clearly one or more tracks stuck in analysis. It stays at the same number and spins forever making no progress.
I have attempted to read the Roon logs to figure out what is stuck but I can’t figure it out from the log.
Please help me determine which files are causing the analysis to be stuck and spinning forever.
Are you still seeing this issue at the present time? I’ve enabled diagnostics for your account, but it looks like your Roon Core is not communicating with our diagnostics servers at the moment, can you please use the Roon Core for at least a few minutes when you have a chance and let us know once you’ve done so? Thanks!
It was not running, I started it back up last night so should be talking to your back end now.
Under settings → Library → Background audio analysis it says “Analyzing: 155/288” and just spinning there with no progress. So yes, still seem to have the problem with something in my library.
I have the same issue. When I stop and start audio analyse it’s solved. But as soon as I add new music the analyse starts again and stuck about 6-10 tracks before the end.
I’m running RoonOs 1.0(256) and Roon 2.0 (1182) on a i5 Nuc, 8Gb, 40.000 tracks library.
Found this in my log at the moment the Analyse stucks. Maybe it has something to do with it? How can I find out what track belongs to trackid=20723506 ??
12/31 07:51:25 Warn: [analysis] failed to get filekey for librarytrack with trackid=20723506
Apologies for the slow response here. I just re-checked your logs and I am not seeing any analysis failures, it looks like the Core is stable to me, have you had any more of the analysis issues appear in the Roon UI? I also noticed that your Core is running an older Roon build, I highly suggest going to Roon Settings → About to update and ensure you have the latest bug fixes.
@Ron_Witkamp - Are you still seeing this error as well? I activated diagnostics for your core too, but also not seeing any abnormal analysis errors. Do let me know if this is resolved, thanks!
