Issue with Music Library update in latest software update?

hi @SD6UnderCover I suggest to review your music library settings and check if the folders paths are still valid - if necessary you should remove the existing (i.e. invalid path) and add a new path - before adding the path, check it on your Mac or PC and make sure you have an account with read access to the music tracks 

Folder paths are still valid - I can still browse and play music from the network drive, it’s just saying it isn’t there when I try to update the library

Are you using the latest Sonos App version (13.4.1) and can you disclose which NAS you are using?

I would take the plunge and remove the library and re-add it again as you have nothing to lose, if it isn’t working for you anyway.

Maybe also power off/on the speaker/device shown as the ‘associated product’ in your Sonos App about box before doing the indexing.

Am on 13.4.1 throughout, and I’m using an old WD MyBookLive for NAS

I removed the network share and tried to add it back in - the Controller accepts the ‘new’ connection, start to index the Library, but then errors after a few seconds saying it no longer exists, which it does

What version of SMB is the library share running on and is the share password protected? Check your NAS settings and set the credentials to the same username/password when you add the Shared library to the Sonos system. Did you restart the ‘associated player’ after removing the share earlier? Maybe try a different device too (just power off the current associated player temporarily). See if that sorts it.

Hi, I have exactly the  same issue as you. My Sonos5 has worked perfectly fine with my ancient WDMyBookLive for 12 months and then last week suddenly stopped updating the library. Like you I was able to play the music already in my library but not add new music. In desperation I deleted the path to my shared folder on the NAS. I then lost my library on my Sonas app S2. I wasn’t too concerned as my music was still in my public shared music folder. I kept typing the path to my NAS music folder in the Sonos App Music Library Setup field, but just kept getting a message that the folder was ‘no longer avaiable’. I now had no music available in my Sonos app library. I phoned Sonos support, and spoke to a couple of very helpful people who remotely accessed my PC to gain access to my MyBookLive settings. After about 2 hours in my PC and the MyBookLive they were unable to resolve theissue as the options available via the WD interface are so limited. They advised me to contact WD support. I’ve sent them an e-mail but had no response so far.

I still had no music. I then went into the MyBookLive user interface, and in the ‘shares’ section set up a new folder called music and put a few traxks in it. I typed the pathway into to my Sonos app and clicked the update music index now, and hurrah, the music in the new folder was indexed to my Sonos. I was euphoric. Today, added some new music to the new music folder, and clicked the update music index now in the Sonos app AND…… ‘folder is no longer available’!!!!!!!!! I could pull my hair out!

I’ve given up. I have a couple of hundred tracks in my new NAS folder but can’t add anymore. I can listen to some music on Sonos radio. I’m now trying to figure out which replacement NAS to buy. 

It’s just spooky that both our MyBookLives have suddenly stopped living with our Sonos devices. 

Same problem here, but my music library is on an external drive connected to my Netgear router by USB. To see if this was a wi-fi issue I tried plugging a Sonos device directly into the router and creating a Sonos net. No difference. This problem was caused by the most recent software update. Please fix this, Sonos.

Did you try removing the library completely from within the Sonos App and then setting up the share again via the router interface, perhaps this time using SMBv2 or higher, (if supported by the router) and then try linking the Sonos App back to the shared library path again (after a router reboot) - I’m just wondering if doing that might fix things?

I suspect something rotten with 13.4.1,