Issue with Music Library update in latest software update?

hi @133133 just like to remind you that my Synology NAS configuration (see this post here) works well - today I upgraded also my SONOS App to version 14.0 - note that also the Sonos S1 Controller has been updated to version 11.3 - hope this helps

Another with this problem.

I have two Western Digital MyBookLive NAS units installed similarly in two locations. As of several months ago, I am no longer able to index the library for both. The error message: “The [drive name] is no longer available.” On one, I deleted the music library hoping I could add it back in, and am unable to do so, displaying the same error message.  On the other, I am able to run my FLAC files with no problem, but cannot index.The firmware has not changed for the NAS since 2015. I’m running S2 at both locations. 

Sonos tech support has not been able to resolve --- they are still working on it.

I have a similar problem using a 3 TB Airport drive. The airport is in bridge mode and has been that way for 4 years. All has worked fine for my song library of >10,000 songs. Recently e.g. since January, my update process seems to run, but not update my list. I deleted the share, put it back in and ran indexing for about 8 hours. When it completed only about 25% of the files were indexed. All of the files are accessible from the MacBook Pro.

I’ve rebooted the drive, and my machine….no luck.

I remember reading somewhere that SONOS is sensitive to caps or characters in the share name. Renamed….still no joy.

I tried this based upon a prior suggestion, but could not see the data

http://xxx.xxx.xxx.xxx:1400/status/tracks_summary

https://xxx.xxx.xxx.xx1443/support/review produced  a lot of information and a colorful signal strength chart, but nothing obvious for this issue.

Any suggestions?

Thanks!

Update:

I deleted the old share with the name TimeCapsule etc, with Timecapsule….90% of my files indexed overnight. I think there is some issue with using caps in the name other than the first letter.

Or maybe this is a giant coincidence after 3 days of trying..The difference in my previous attempts was to delete the share TimeCapsule first, then rename drive, then run again.

I think part of this issue is when I changed to a new router, I had to reenter the drive name and I introduced a capital letter in the middle of the name.

Hope this helps.

I have the same issue as described here. I have an asus zenwifi router with a seagate harddrive attached. My music library is no longer being found after updating sonos to v14.2. I get the “<path> not available” error, even though I can connect to the drive as before via SMB from my computer. Removing the library didn’t help; I can’t add it back at all now. 

I deleted my old share and am now not able to index my 40k tracks without an error message saying "the drive has disconnected" or some such message. I spent two hours yesterday with support and they were unable to resolve it. I can select from the same network drive a folder that has 3.5k tracks and that has been indexed ok. I tried an old Synology Nas with SMB2 enabled and a duplicate of the 40k tracks and got the same error. 

These 40k tracks have remained unchanged as far as metadata is concerned.

Prior to my deleting and re indexing my share I was getting all sorts of weird behaviour like tracks jumping and playing the next one for a few seconds before finally playing a track all the way through and then continuing the playlist.

Something is broken in this latest update.

My case number was 03743480

Try just selecting a single folder from your networked drive and I suspect it will index ok and work.

This is the same way I have used my Sonos system for the last ten years, first with a ASUS n66 then XT8 Mesh (using Boost and therefore Sonosnet) with a simple WD 1gb Passport drive. This has been without issue up until now and a terrific way of using the Sonos system. I have changed nothing and now it does not work properly. I would suggest something is wrong in the Samba Share part of Sonos software.

Try just selecting a single folder from your networked drive and I suspect it will index ok and work.

This is correct. I just tried adding a small subset of songs from a directory on the same network hard drive (same volume, etc). They were added without any problem and I can play them on my sonos. I am still getting the “not available” error when I try adding all ~10,000 songs in my library.

Before updating the sonos software, I had no problems indexing the same files from the same harddrive. Something is wrong with the sonos software such that it drops the SMB connection when adding lots of files. 

The threshold for me seems to be about 1,100 files. When I add more than that to the directory, I get the “not available” error. When I delete back to that level, it works again. 

Probably good to contact Sonos with that info as a way of escalating "our" problem. Your right the Sonos software appears to  disconnect the drive at a certain point in the indexing process when the track count is high. 

I used a 128 GB USB drive with 3500 tracks and it indexed ok.

Windows Explorer can browse to the Network Location with the 1tb drive connected and I can play any of the 40k files locally on my PC using Foobar2000.

Anyone who only streams music would never see this issue.

Something is definitely broken.