Library Scan Mismatch Between Players

Hello, I hope someone can help me please.

I have a three year old Node 2i and a year old Node N130, both have been operating from a large FLAC collection; approximately 130,000 songs on my HP PR4100 NAS.

This has worked faultlessly for years, however over the last 7-10 days I have a problem rescanning new FLAC additions to my Library. When I rescan my library from the Node 2i all my new additions to my central library are shown, however from the Node N130 nothing new shows up, it’s basically 7-10 days behind.

I have carried out numerous scans same result. Last night I cleared the library from the N130 and rebuilt the library from the Diagnostics menu, after several hours it finished, however the library is exactly the same as before, 7-10 days behind???

As previously mentioned, this is only affecting the Node N130?????

I have checked both units and they’re operating on the latest software release, 4.02.

Can someone kindly help me please?

Carl

Official comment

Bjørn Ulvik

Hi-Res

October 31, 2023 10:42

After rebuilding/reindexing, databases will (should) be replicated between players. I've had that issue once, due to a large library, and the player(s) ran out of internal memory/storage. Indexing went well, but databases could not be replicated.

I could partially fix it by rebooting affected player(s) after indexing. They would then have "enough" memory after a reboot.

I ended up moving a lot of my library to another share.

Help -> Send support request would probably be your best option.

November 01, 2023 17:10

A little update, thanks to BJØRN's post above, I unplugged the Node N130, left it off for a couple of minutes, plugged it back in, carried out a Rebuild Index and we're back to normal.

Library Scan Mismatch Between Players

Comments

Didn't find what you were looking for?