So in the middle of a listening session Roon flashed a message about a library update and proceeded to rescan my entire library. The rescan took a while but after it was done everything seems to be working properly. This has never happened before outside a version update. Has this happened to anybody else? I’m on V 2.0, Build 1311.
Sounds very odd. Some system details might help but my money would be on possible database corruption or the start of a failing boot SSD or the music storage media. Power interruption seems to be a common cause of this.
Roon would need to review your logs to see if anything is indicated there. Library updates only happen when required by an update, not at any other time.
Hmm, interesting.
I’m on earlyaccess and this happened to me yesterday, although I didn’t get a message and it did not appear to be a rescan of my whole library, somewhere around 600 tracks.
I thought it weird at the time.
It is quite possible then that this happened to many people that have their cores on 24/7 but weren’t using Roon at the time so didn’t notice?
1 Like
My core is on a NUC Rock with music on internal SSD. This setup is only about three months old and it’s working perfectly today. I don’t think anything is failing. I used to be on early access, but I thought I got off. What version is early access using? Just checked, looks like the current early access version is 1321. I have the regular 1311 version.
Mine did a rescan yesterday of about 1200 tracks out of 60k.
Apart from the build number, next to it it says clearly “earlyaccess” or “production”, respectively
Huh, I just changed the identification of one album as described here and suddenly it started rescanning my library as well:
and still counting up …
(I have 45K tracks in total). On Early Access B1321, ROCK.
Edit: And a minute after posting this it stopped at probably approx. 3.5K