I am setting up a new S2 system in a 2nd home. The system is all connected and working fine and I am trying to attached an established music library on a NAS drive which I used on the S1 system before for years with no problems. It is a big library with over 25,000 songs. When I attach to it I am told that I am connected and that it is scanning the library. After a few minutes it fails with a message that says: “//xxxxxxx/” is no longer available. The device where the music files are stored may not be powered on, or the path may have changed.” … meanwhile I am connected to that file share with no issues from various PC’s on my network. Sometimes it fails in 3-4 minutes, sometimes it runs 20 minutes and fails. The Buffalo NAS drive is always online and connected and has no issues.
I have tried following the ridiculous advice: unplug all sonos devices, the nas and reboot the router and then when the router is back online power up the sonos and NAS devices and try again. It makes NO difference.
Maybe try changing the version of the SMB protocol to v2 (or higher) on the NAS box share. Use the netbios name, or it’s allocated ‘fixed’ IP address in the path and ensure the ‘share’ username and password are correct and see if that perhaps solves the issue.
Try segmenting your library slightly. For example: rather than having one large music folder, break it into smaller folders such as:
You can define up to 16 library segments.
I suspect that there might be a timeout due to the large number of files being processed in one gulp. Breaking the library into smaller pieces will reduce the processing time. The only difference to the system user will be in the Music Library’s Folders View.