Music library not reacheable because of SMB1

I’m using Synology and S2. I have no issues accessing my library and I can casually flip the Synology between SMB1-2-3 while music is playing.

At other homes I have seen issues with the SONOS controller not being able to setup the library shares due to a Windows setting. Make sure that the library share is marked as “Public” and that SONOS has the correct access credentials.

The indexer might crash if it encounters a stray character in the track metadata. 

Finally, one of the SONOS players will be in charge of building the index. If this player doesn’t have enough free space, the indexer might terminate in mid run. The solution is to break the library into smaller segments, perhaps having separate shares for Classical, Pop, and Seasonal. You can also reduce the size of the meta data. For example, some rippers insist on pushing the whole first stanza of an opera track into the file name and track title. This is unnecessary. A very manageable scheme for the human is to keep each CD in a separate folder and simply use the track number or similar for each file name. My file names are simply TRK001.flac, etc.

So, just double-double checking, if completely migrated to S2 the idea is to set a Synology NAS to;

• Maximum SMB protocol: SMB3
• Minimum SMB protocol: SMB2

(i.e. so no SMB1)

☝🏻 Anyone?

Hi @Sup4rfu8e 

Yes.

I’m having similar issues with my S2 system, I have ~300GB library with around 22K tracks. If I add a large amount of new stuff in one go my S2 system can’t index it and throws the “share unreachable error” The only way to “fix it” is to trash the library and rebuild it around 20-30 albums at a time. Totally unacceptable. My S1 system doesn’t have this issue and runs on the same LAN using the same NAS.

Hi @groove_regulator 

I recommend you get in touch with our technical support team, who have tools at their disposal that will allow them to give you advice specific to your Sonos system and what it reports.

Thanks Corry we've had lengthy remote sessions and your technical team have concluded that this is a bug on your side but with no timeline to fix 😭

I see that this thread has a few different issues being discussed but from my perspective I can report since the Sonos update this morning (02/Apr/23) (think it was both a controller and firmware update) I’m able to re-add my entire 300GB library in one chunk without the S2 platform throwing an error. Since I also run an S1 platform the QNAP NAS still has the option to support SMB1 enabled. It’s a shame S1 can’t be upgraded to read SMB2 or 3.

Yes, it is indeed a shame that there’s not enough memory available to add SMB v2 or above to the linux kernel that is S1, and put it on older devices that also don’t have available memory space for it. I’d guess that might have been one of the substantial reasons why Sonos had to move to S2 for support of higher versions of SMB.  

Just to add I still get library errors, when loading a large playlist (say 800 tracks) I will get "track not found errors" for the first few items, but it eventually settles down. Still far from acceptable for me since local library access is the main reason I bought into sonos more than a decade ago. There are several cheaper alternatives if streaming is all that's required. I really hope they sort this out else I'll need to move to bluesound.