I’d first see what happens if you remove a few more tracks in the library, as the allocation in the index might not be ‘track for track’ as some tracks metadata may take up more than one slot, plus there is the possibility that some memory storage on any older devices can sometimes have ‘bad’ sectors marked by the OS as being unavailable for storage, that’s if you are perhaps using any old products and nearing storage limits.

No, I don’t think that it’s to too with being too near the limits.

To test it, I deleted the curret lbrary and pointed the sonos to only contemporary music (which is about a third of my Sonos library). No difference after the indexing.

I then added in a download directory and reindexed again. Again, no difference.

When browsing the folders on Sonos, I can see the directory but when I go into it I get ‘unable to browse music’ and no files shown.

Still looking…..

Something to do with the NAS perhaps? I’ll go and re-index my Sonos S1 setup here (25k+ tracks on a Netgear NAS) and let you know if I see any issues.

@amun,

It seems to be working okay here with the Sonos S1 App v11.14 - I re-indexed the local NAS SMBv1 library and it still seems to be working okay - see attached. I can try removing and re-adding the library if you want me to perhaps test that too? (Let me know).

My thoughts are to maybe look to see if anything has perhaps changed on the NAS.

Maybe also try power-cycling the Sonos devices, just as a further thought.

Many thanks for all your help, Ken

I think that the problem was caused by two things.

The first was that the tracks were (somehow) duplicated, so I suspect that the system was finding the first and then ignoring the second - the one that I expected to find.

The other problem was that the three converted files had no tag info at all. Once I copied filename>tag using MP3Tag then Sonos recognised them and indexed them properly.

So, seems to be back to normal now

Ah good to hear you sorted it @amun and thanks for posting the outcome too.