Sonos no longer recognizing folder.jpg for cover art?

Looking at my SMB (Linux Samba) server status I’m seeing this even though SMBv1 is enabled there: SMB3_02.  The smbstatus command should work on any Linux based server, it may need sudo/root to run.

If you can’t personally use the information please feel free to ignore it.

pi@pi-3b-2:~ $ sudo smbstatus

Samba version 4.9.5-Debian
PID     Username     Group        Machine                                   Protocol Version  Encryption           Signing              
--------------------------------------------------------------------------------------------------------------------------------
7412    nobody       nogroup      172.16.1.115 (ipv4:172.16.1.115:41484)    SMB3_02           -                    -                    

Service      pid     Machine       Connected at                     Encryption   Signing     
---------------------------------------------------------------------------------------------
music        7412    172.16.1.115  Wed Nov 24 09:36:16 AM 2021 MST  -            -           

Locked files:
Pid          Uid        DenyMode   Access      R/W        Oplock           SharePath   Name   Time
--------------------------------------------------------------------------------------------------
7412         65534      DENY_NONE  0x89        RDONLY     NONE             /mnt/ssd-music   Current/B/Beach Boys, The/20 Good Vibrations The Beach Boys Greatest Hits Volume 1/Beach Boys - 11 - Dance, Dance, Dance.flac   Wed Nov 24 09:36:16 2021
 

Thanks for that update!

I made some testing on my Synology NAS. I had it set to SMB1 minimum and SMB3 maximum. I changed that so that minimum was SMB2 with large MTU. At first music did not play, but it was sufficient to restart the Windows controller for the music to start playing. Still no cover art. Then I changed the setting to SMB1 as both minimum and maximum. Cover art are now starting to show up. Not only in Imported Playlists, but also in Albums where I did not see it before.

Since SMB3 support is certainly a welcome addition (and much belated), I’m prepared to cut Sonos some slack for things not working perfectly the first time.

Well, running with only SMB1 proved not to be a solution in my case. This morning I did not have a new set of imported playlists as I should have. (I generate a random selection every night and copy to the NAS). Troubleshooting revealed this error message from Windows:

You can't connect to the file share because it's not secure. This share requires the obsolete SMB1 protocol, which is unsafe and could expose your system to attack.
Your system requires SMB2 or higher. For more info on resolving this issue, see: https://go.microsoft.com/fwlink/?linkid=852747

Hi all,

My Sonos recently stopped being able to play or index anything on my local network music file share. After some time with support, Sonos has confirmed to me via email that the 13.4 release contains SMBv2v3 support.

After further testing it’s clear that support for SMB v2v3 is buggy and resulted in my not being able to index music libraries or play anything on my file share over SMB. When I limit my server to only use SMB v1 Sonos is working fine again, but this is not a viable solution for me due to other clients that use the same file share.

I have already replied back to support with this information. If any others can confirm the same behavior, please contact Sonos as well with your details so they understand how widespread this problem is and can accelerate a solution.

I can confirm this buggy behavior. Since 13.4 my folder.jpg files sometimes (but not always) show themselves in the queue, sometimes (but not always) they pop up in the music library, sometimes (but not always) they can be seen in the desktop app but not in the cell phone app. 

Is it unreasonable of me to expect that this error should have been fixed already? No official comment from Sonos or even a timeline for the fix either, means this all seems really poor on Sonos' part.

Yes. I think that it is a little unreasonable. Sonos 13.4 has not been out for two weeks. I started this thread nine days ago. Also, recall that Sonos are located in the US where the passed week was a short week due to Thanksgiving.

To compare, I started thread on a broken update in May, and in this case it took 13 days before from someone Sonos appeared in the thread and confirmed that there was an issue. It took a couple of releases until a fix appeared. That issue only affected Sonos One SL, but in a way it was more severe, as some music files were rendered inaccessible. This time it is after all only cover art.

I also like to point out that Sonos has already confirmed the issue. Even if they have not posted directly to this thread, others have relayed the information.

As for a fix, I can see three options:

1. Roll back on SMB2/SMB3 support. That should be easy, but there could other improvements that are dependent on this support, so they may not want to do that.
2. Gives us in option to disable SMB2/SMB3. That would be a very un-Sonos thing to do.
3. Actually fix the issue. This is of course the desirable long-term solution, but it may also take longer time to roll out.

And, again, it’s only cover art. When I started this thread, my main concern that Sonos might have decided not support folder.jpg at all. I can live with not always seeing covert in my players for a month or so.

Chiming in late to the party to report that on my Synology Diskstation, I have the same issue, though oddly enough only in the Android controller; the Windows Desktop controller shows artwork. Full report here; diagnostics 89729938; thanks to @buzz for pointing me to this thread. I've set my NAS to use only SMBv1 (though I remember reading that this is unwise for security reasons). Album art is now showing up in the Android controller, after a library index refresh (same effect as right after I prioritized Sonos and phone in my Wifi router). Hoping for a quick fix, because if there is a security issue with SMBv1, I'd rather switch back soon.

What surprises me most about this issue is that the album art display was so erratic. Without closing the controller on my phone, over the course of the same day, I can see some artwork showing in the morning, disappearing in the afternoon, and showing again in the evening. I wonder why Sonos doesn't just have the controller cache the artwork? 

PS: Setting the NAS to use only SMBv1 did solve the album art issue. But in order to be able to access my NAS from Windows 10, I had to re-enable SMBv1 in the OS, and even then Windows had issues accessing the shared folders on the NAS. And with the strongly worded Microsoft blog piece on the reasons why we should no longer use SMBv1, I've decided to accept the album art issue for now, and wait for Sonos to fix the SMBv3 issue.

On the upside, did discover that my NAS was still set to support Apple and Linux protocols, so switched those off.

Most likely why Sonos hasn’t ‘announced’ the SMB version upgrade. It appears to be mostly, but not completely, working. I’d imagine their engineers are working overtime trying to figure out this issue, which may not have shown up in beta testing, given the numbers of people testing. At least, having run a fair number of betas for gaming software and not having a bug show up until it was released to everyone, that is what I’d assume.