"//{nas path}/Folder/" is no longer available

bit worried that this has been an issue for a number of months, the post below looks to be 9 months old

can’t understand why more people aren’t complaining about this, is local (large) music library access a thing of the past? I thought that was really one of the big selling points for Sonos (at least in the beginning), perhaps now they’re more focused on streaming and soundbars.

I’ll admit that I don’t run S1 anymore….but I’ve had zero issues with S2 and my WD MyCloud, using SMB 3

Create the problem and send in a diagnostic, then contact Sonos to have it looked at.

Sonos have admitted via email (after a lengthy remote session where they took control of my windows PC) that there is “an issue” but there is no “committed date” for a fix on their side. They have a workaround of limiting the upper SMB version to 1 which is pretty poor. An alternate way I’ve figured out to mitigate this is to limit the amount of changes in the library between index scans. I don’t know what the upper limit is but I’ve completed a lengthy experiment this evening where I rebuilt my library from scratch adding 20-30 albums at a time. The S2 has managed to index the lot without erroring. I’ll monitor it for a period and see how it behaves. My concern is if you ever see the dreaded “share unreachable” error it seems the only way to recover is to delete the library and start again from scratch adding it back in small chunks. Doing a 300GB library takes an entire evening.

Try a different approach. Break your library into multiple shares. For example:

\\drive\music\classical
\\drive\music\jazz
\\drive\music\pop

etc.

You can use up to 16 shares.

My thought is that a large share (many tracks) will use too much memory while building the index. Smaller shares (fewer tracks) require less memory during the index build. Using shorter file names will help too. Some rippers throw a lot of junk into the file names. While not ideal for the human, SONOS would be happy with file names 00001.flac --> 65000.flac all in a single folder. I store each CD in its own folder and include the track number in the file name. For example: TRK01.flac. File size does not matter.

Thanks for your input @buzz unfortunately restructuring my library as you suggest isn’t an option for me (and shouldn’t be necessary). Also using meta data (ie Genre as you suggest) as a directory structure will likely lead me to confusion. A lot of tracks in my library have more than one genre tag. I suppose alphabetical folders might have been an option but as I say shouldn’t be necessary.

I received a Sonos update this morning, I think it was both a controller and firmware update. After completing that update I had another shot at adding back in my 300Gb library in one go. This time it worked. No idea if the recent update sorted it or whether it was something else. Will update this thread in future if it goes south again.

My folder structure does not interact with the metadata, but it will impact Folders view of the library.

actually it’s still broken, yesterday was a one-off working scenario, the dreaded “folder no longer available” error is back….very disappointing

So after a few days of monitoring this it seems that things are perhaps a little better than they were pre the latest Sono update (earlier in April) but things are still far from ideal.

After rebuilding my library for the second time Sonos was able to finally index the whole 22K tracks (~300GB) however large playlists still give it problems. If I load up an (imported) playlist of say 500 tracks or more it will throw the “can’t find track/file” error for the first few tracks until it settles down.

I’m paranoid about adding any more CD rips to the library since it would appear that once you get the “NAS isn’t there” error the only way to fix it (and it’s not really a fix) is to rebuild the full library one slow chunk at a time.

After a recent S2 Sonos update (about a week ago) I thought that this issue had been addressed since I was no longer seeing the “NAS not available error” during a Music Library update. What seems to be happening now is although the error doesn’t get thrown a number of albums simply don’t get added to the library. If you browse the Music Library using “folder view” Sonos simply omits the folders/albums it’s not managed to index (I have about 1000 folders in the main music share, one folder per CD/album).

As ever S1 continues to work without flaws on the same network using the same NAS share for Music Library. Very disappointing.