Trending Lyricist I

Answered

Failure reading files from NAS

Forum|Forum|9 months ago
December 25, 2025
9 replies
194 views

An S2 system that’s been working fine off the same Synology NAS for years.
No network changes.
Sonos reports that it can’t read the music files from the NAS share.
Rebooted all round (inc network router) and readded the Music Library share. Connects ok, indexes all the files (Library contents are fine), but trying to play a track gives a file access error.
I’m baffled.

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.

Best answer by Stanley_4

You might add static/reserved addresses for all Sonos and then do another power down the Sonos and reboot router and controller cycle.

Sonos can pass the library index process to other Sonos in some situations so it could be the Sonos IP glitch again.

buzz

Did this issue begin after a NAS or SONOS update? Are the unplayable tracks part of a SONOS playlist? I’m not having issues with my SYNOLOGY, but it does require an annoyingly long time to spin up — during which the files are “unplayable”.

T

tyddynonnAuthor

Trending Lyricist I

No Sonos or DSM update since it was known to be working. NAS is on 24/7 so not a startup issue.
it feels like an SMB or permissions issue- so Sonos can scan the files to build the index, but not read the contents. I’m not sure how to check for that.

T

tyddynonnAuthor

Trending Lyricist I

Oh, and yes in playlists, but also when playing directly from the library

buzz

Yes there can be SMB issues, but they shouldn’t suddenly creep up. SMB could be an issue if you are using S1 because SYNOLOGY could have disabled it as a security update. SMB can be an issue when upgrading to S2. You can check SMB in the SYNOLOGY setup.

User117655

Prodigy II

@tyddynonn I had this, or very similar, issue a week or so ago suddenly stopped recognising my shared folders with the same error so would not re-index - this was after adding content. Sonos would, however, still play my music 🤔.

I found removing and re-adding a shared folder to Sonos resolved it (via the desktop app for info).

I only did this with one folder with minimal content though. I held off on my main (55k + track) library... It resolved itself at some point soon after.

I guess it was a Sonos glitch and not a Synology issue, or maybe a network traffic issue but 🤷🏼‍♂️

T

tyddynonnAuthor

Trending Lyricist I

The NAS is definitely set for SMB 2 or 3.

What makes this particularly baffling is not knowing what’s changed.

might have to get WireShark out to see what’s happening on the network… what a pain.

BTW I’ve also tried adding the NAS share using its static IP address - in case it’s a name resolution issue - but no difference.

buzz

While you are messing with WireShark, check to see if there is any access of the SONOS online servers during local music play.

T

tyddynonnAuthor

Trending Lyricist I

Well, in true Sonos style, the problem has simply ‘gone away’.

A repeat of the ‘power down all the Sonos devices and restart’ technique - and leaving it all alone for ~24hours - resulted in things working again.

I can only imagine a weird network glitch. Luckily I didn’t have to resort to WireShark. I do use pihole to block queries to msmetrics.ws.sonos.com, but that’s been the case for a long time.

Thanks again for the suggestions

Stanley_4Answer

Grand Maestro

You might add static/reserved addresses for all Sonos and then do another power down the Sonos and reboot router and controller cycle.

Sonos can pass the library index process to other Sonos in some situations so it could be the Sonos IP glitch again.

Sign up

Login to the community