Skip to main content

 

I’ve spent several days trying to build a music library, and this message keeps popping up. “Algol” is the name of the server and “all” is the share. All checks out well on the host side. 

This message occurs 5-10-15 minutes into the Library refresh. I’ve been able to get most of the library built by starting with a small number of files in the share, refreshing the library, adding more, refresh, repeat. Having smaller updates seems to suit Sonos better. But now that the library has grown to 38,000 or so files, I can’t get any further. 

I suspect what is happening is that Sonos is timing out on reading the share folders and building its database. It interprets a timeout as the share going away -- unpowered, changed path, whatever, none of which is definitely not the case. 

I don’t have reason to suspect the environment. The music host is wired to the main household router via Ethernet. It’s running macOS Big Sur (older 2013 model). For that part of the library already built, I can play those files directly and via playlist. Samba version is 3.

Questions -

Is there a hard limit on number of files in the Music library? Can I see how many I have at the moment? As mentioned, I am about 38K and holding. 

Is there a debugger or log info I can open up to see if there is anything helpful there?

Are there network parameters that can be tweaked if in fact it’s timing out? (though I am unsure why it would be timing out….)

Thanks in advance! :) 

Seeing internal Sonos errors needs the assistance of Sonos Support staff. Generate the error, submit a diagnostic within a couple minutes and then contact Support (not here) with the number and your issue.

Seeing internal Sonos errors needs the assistance of Sonos Support staff. Generate the error, submit a diagnostic within a couple minutes and then contact Support (not here) with the number and your issue.

 

…. sigh … Ok thanks, will do. 

For anyone reading this … I never managed to solve the problem directly. After two hours on the phone w/ Sonos (thanks Kristin), we gave up because the library builds were taking too long. 

I suspected an issue with timeouts and still believe this to be the case. The way I got it working was to start with a clean slate and an empty music library; add parts back a bit at a time; resync the library. After the last bit was restored, I did one more sync and it held. 

I also took the Connect:AMP off of wired internet and put it on wireless; now all of the Sonos devices in this setup are wireless (Amp, Roam, Play 1). Could this have made a difference? Who knows ….

Potentially, especially if there was anything slowing down the connection to the speaker ‘managing’ the library build/scan, with wifi interference , or even a potential duplicate IP address issue blocking the connection. Speed is of the essence in that process, if you can’t wire a Sonos device, I would try to initiate the process with the Roam being the primary, as it has the most memory and best CPU in it, being the newest device. The CONNECT:AMP likely has the slowest CPU and smallest amount of onboard RAM, but I don’t recall offhand how it compares to the PLAY:1. 

Potentially, especially if there was anything slowing down the connection to the speaker ‘managing’ the library build/scan, with wifi interference , or even a potential duplicate IP address issue blocking the connection. Speed is of the essence in that process, if you can’t wire a Sonos device, I would try to initiate the process with the Roam being the primary, as it has the most memory and best CPU in it, being the newest device. The CONNECT:AMP likely has the slowest CPU and smallest amount of onboard RAM, but I don’t recall offhand how it compares to the PLAY:1. 

Fascinating … that never occurred to me. I will try it that way. 

Yes the Amp is the grandpappy here but it powers my floor speakers nicely. I always looked at the system as that being the starting point. 

Thanks!

 

The old app would try to move library updates to a more powerful Sonos device, no clue if this is in the new app or firmware.

It did help a lot for folks with old gear.

Reply


Terms & ConditionsCookie settings