Issue with Music Library update in latest software update?

I too are having a similar problem with my Buffalo LS420D7D6 NAS.

After the upgrade in November indexing started to fail. I could still delete the Library details and re-enter them OK and the the library was created though.

My NAS was set to SMB v2 and therefore it defaulted to using SMB v1 to allow access. With the change to support v2 it must have started using that. Switching the SMB v2 support off on the NAS allowed the Indexing to complete without error. 

I think this s a problem with the SMB v2/3 integration in the controller software. Possibly a timing issue during re-indexing.

Think SONOS need to take a look at this!

Any news on a fix for this indexing issue?

I have the same problem with my WD NAS, existing music plays but can't update the library. In trying to troubleshoot i managed to stop everything working and ended up going though a factory reset of all devices. 8 eventually managed to get the system back up running and the library updated with existing and new tracks. It all looked good and the tried adding some new music a couple of weeks later and the same problem is back. I could I guess try another factory reset but I shouldn't need to because Sonos have now had this problem for 3 months and still no fix. I did think this was great kit but I'm now starting to have my doubts. 

Just as a reminder, if you’re using the Sonos operating system called S1, you should still use using SMB v1 and NTML v1.

If you’re using the Sonos S2 operating system, you can update your NAS settings to accept connections across higher versions of SMB and NTML.

I dug out my old ASUS RT-N66U Merlin Firmware router and using his version of SMB1 I was able to index the large library. Having purchased two ASUS XT8 as a major upgrade my only idea was to front end these two with a three band AiMesh router that could have Merlin's Firmware loaded so I have coughed up £400 for a GT-AX11000 and sure enough with standard firmware no indexing. Loaded the Merlin Firmware and I now have a system that works with the XT8s as AiMesh nodes.

It is obvious from these posts that the Sonos SMB1 implementation is not wholly compatible with a lot of systems.

I have asked Merlin what the difference is between his modified and ASUS SMB1 versions is but as yet have had no reply. 

Sonos support staff although helpful have not been able to resolve this issue for me and it looks like others.

To me this is just another example of Sonos leaving behind and losing the plot with their old customer base in the pursuit of endless streaming applications including their own.

When you take an honest look at the Controller Software it is just a clunky mess. Works yes - but a mess nevertheless!

The simple fact remains that there isn’t enough available memory on the hardware to update S1 with the Linux kernel that allows anything higher than SMB v1. Not sure that this is a ‘choice’ as much as a forced circumstance by older hardware that has restricted RAM and CPU. But then again, I don’t expect my ‘386 to be able to run Windows 11, either. 

No that’s not the case. SMB1 has not been an issue, it’s more the case that the S2 App now supports upto SMB v3. SMB1 works on all, but is known for its vulnerability issues.

Sonos can’t implement higher versions of SMB on an S1 system because the Linux kernel on the ‘old’ players apparently does not support the higher versions, plus Sonos have mostly put the S1 system into ‘maintenance mode’, with just security updates and to try to keep the streaming services running on that system.

It is the S2 app I am referring to. Maybe it does work fine on SMB2 or 3 but it is no longer happy with SMB1.

I just want something that used to work perfectly but no longer does. If it was just me I could accept that but from the posts others are having issues and not just with Synology NAS but the much simpler connecting a hard drive to an appropriate router that supports SMB1.

I use a Netgear NAS that supports the following versions of SMB:

I have tried each SMB version listed with the Sonos S2 App and all work fine up-to version v3.0 - that includes SMB v1, so not sure why SMB v1 is not working on other devices? However…

Some NAS box SMB shares have other settings such as ‘Oplocks’ or Write options… ‘Preallocate/Strict Sync’, or even security settings such as ‘Restricting Anonymous’, ‘SMB Signing’ or ‘SMB Encryption’ - some of those settings may need to be disabled for SMB v1 to work on the share - so perhaps check any other settings that relate to the implementation of SMB on the storage device.