Contributor I

Issue with Music Library update in latest software update?

Forum|Forum|4 years ago
December 20, 2021
50 replies
2214 views

My Music Library is refusing to update, on both scheduled and manually triggered.

This seems relatively recent. When I trigger a manual update, it says that my NAS drive is no longer available, despite it being able to browse and play music from it.

This is effecting all installs of my controllers, on Mac, PC, Amazon Kindle and Android Phone. I’ve got multiple Play:1, a Play: 3, and Connect and a Beam connected to the network.

I had thought about removing and trying to add the device again, but I’m concerned that it will just not find it.

Any ideas?

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

Show previous replies

B

bobc99

Lyricist I

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 did remove the entire library - and then couldn’t replace it! I’ve been able to get some of it back by dividing it into smaller folders. Some folders are accepted by Sonos, the rest are “no longer available”. Router reboots make no difference. And no, my router doesn’t support SMB v2. My current router arrangement has been working fine for the last six years, and there have been no recent updates to the router firmware. I really do think this is a Sonos issue.

Ken_Griffiths

I suspect something rotten with 13.4.1,

There are quite a few different versions of the SMB protocol, as shown in this summary-list taken from my NAS server… it appears Sonos may currently support upto v3.0 from their recent announcement and from my own ‘initial’ testing here. I’m thinking that there maybe an issue for those who have their shares set at a higher version of the protocol, but this is just a guess on my part.

Maybe try setting the SMB version to 3.0 or lower on the server and see if that ‘perhaps’ resolves any issues seen.

B

beynym

World-Class Superstar

Maybe try setting the SMB version to 3.0 or lower on the server and see if that ‘perhaps’ resolves any issues seen.

On a My Cloud Home there is no configuration panel, so nothing to configure.

Ken_Griffiths

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 did remove the entire library - and then couldn’t replace it! I’ve been able to get some of it back by dividing it into smaller folders. Some folders are accepted by Sonos, the rest are “no longer available”. Router reboots make no difference. And no, my router doesn’t support SMB v2. My current router arrangement has been working fine for the last six years, and there have been no recent updates to the router firmware. I really do think this is a Sonos issue.

Maybe… but the library share is working okay here for me and many others appear to have it working too, so the suggestions are worth exploring perhaps …and if still no joy, then it’s maybe worthwhile speaking with Sonos Support Staff direct via this LINK to see if they can assist.

Ken_Griffiths

Maybe try setting the SMB version to 3.0 or lower on the server and see if that ‘perhaps’ resolves any issues seen.

On a My Cloud Home there is no configuration panel, so nothing to configure.

I don’t know your particular server, but are there no official add-ons, or 3rd-party plug-ins, that may support the configuration of the local shares?

B

beynym

World-Class Superstar

I don’t know your particular server, but are there no official add-ons, or 3rd-party plug-ins, that may support the configuration of the local shares?

No, there aren't.

J

John from England

Lyricist I

Well, in the end I gave up. I've bought a Synology NAS, an expense I can do without. I've copied a small amount of music into the folder on the Synology, typed the new pathway into the S2 app and I now have music on my Sonos. So problem solved(expensively) and I'll just use my MyBookLive for other things.

1

133133

Enthusiast II

I have just updated to S1 11.2.13 and came on here to look because I have the same problem with a relatively new Synology DS416 slim with SSDs inside. “Unable to play….access to ‘NAS’ denied. <foldername> no longer available.

Try to add a different folder on the same NAS and it says it can’t ‘reason <computername> not responding.

Never update on Christmas Eve after support hours, eh? Not that it seems support know what is going on?

Just another nail in the coffin.

Cheers Sonos.

Ken_Griffiths

I have just updated to S1 11.2.13 and came on here to look because I have the same problem with a relatively new Synology DS416 slim with SSDs inside. “Unable to play….access to ‘NAS’ denied. <foldername> no longer available.

Try to add a different folder on the same NAS and it says it can’t ‘reason <computername> not responding.

Never update on Christmas Eve after support hours, eh? Not that it seems support know what is going on?

Just another nail in the coffin.

Cheers Sonos.

Why is it mentioning ‘computername not responding’ when you are using a NAS box and accessing it using SMB, rather than the http protocol? - It sounds like you may have something wrong there in the path to the local library, or the SMB share login credentials are incorrect - perhaps try using the IP address instead of the netbios name in your library path and check the SMB share login credentials too?

Airgetlam

Important to note that as you’re using S1, higher versions of SMB are not available, and you need to be certain that SMB v1 and NTML v1 are active. Both have been known to be reset by background updates to NAS software.

Bruce

Show more replies

Sign up

Login to the community