Skip to main content

Hi there, recent issue with my S2 system, after adding a few more albums to my 22K track music library stored on my NAS it continually failed to update throwing the 

 

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

 

error, sometimes immediately sometimes after a few minutes of indexing. Surprisingly my S1 system (on the same LAN) can read and index the NAS share with no issues. My S2 system comprises of a Port (ethernet connection) and a Roam. My S1 consists of a Connect/ZP, a Play 5 and One SL. Sonos have acknowledged there is an issue but cannot advise of a timeline for a fix.

If I create a small library on the same NAS with a few albums the S2 system can index it. I’ve seen some similar posts with the same issue including suggestions of changing the library structure into a number of smaller chunks but this isn’t acceptable for me.

Other suggestions welcome, or keen to hear if others are having the same issue.

After several hours of attempting to move my music library (~ 20K tracks; 1,650 albums; 100GB) to a Buffalo LinkStation LS210D NAS, I have arrived at the following ‘conclusions’:

  1. The error message “// drive name]/music_folder is no longer available.” is non-specific at best, if not completely erroneous.   Upon successfully adding/updating a new, but relatively small, Music Library I can stream tracks from the NAS on my SONOS speakers simultaneously with the SONOS app displaying the error message; of course the music_folder IS available. 
  2. There is some limit:   Current_#_Tracks_In_Library + #_New_Tracks_Added > N that triggers the error message.  Hence, if you attempt to add a large music library at once, you will exceed N immediately.   If you take an incremental approach, example add all albums beginning with the letter A, then B, etc. you will succeed until you get to a point where you exceed N; in my case the letter T. 
  3. Once I have arrived at this threshold N, if I delete a few albums from Music_Folder, SONOS will successfully “Update Music Library Now”.  Yet when I copy the few albums back into Music_Folder, I get the error message again.   I did think it was possibly some syntax bug with a particular album folder, but I ruled that out by repeating the threshold test with various other album folders.
  4. I think the SMB v1 or v2 may be a bona fide issue, however, it is tangential to the main issue here. 

The bottom line is a developer at SONOS should easily be able to troubleshoot and fix this bug as the problem is easy to reproduce, as evidenced by the number of us reporting similar experiences in this forum.

Get the problem to happen, submit a diagnostic, call Sonos support.

Until they get enough interest in a bug it is not bumped up to a high priority for getting fixed.

Terms & ConditionsCookie settings