OMV 7 and SONOS S1 connectivity

1st Official Post

    Good Day, I have running OMV 6 for about 2 years, RPI 4 4GB, and everything works great including with my SONOS S1 system. I recently completed the update to OMV 7 using the supplied instructions and the upgrade scripts. The upgrade went easily and appeared to have no problems. I can access the NAS on all my Win 10 machines, access all files, do backups, etc.


    My only problem is that I cannot access the NAS via my SONOS S1 system. SONOS reports that the folder doesn't exist. I have checked the SMB/CIFS/Settings menu and the OMV 7 version matches the OMV 6 version (which works). I suspect that this has something to do with SONOS S1 requiring SMB1. I have included the OMV 7 settings page and the SONOS error message. Note that I can fully access the NAS with my Win 10 machine in every other aspect. Other than this the script worked flawlessly. Any help would be appreciated.


    ----------------------------------------------------------------------------------------------------

    Raspberry PI4 - 4GB w/ Debian Bullseye using Deskpi-Pro case :)

    OMV 6.9.16-1 (Shaitan)

    3 weeks and no comment or help from anyone???

    ----------------------------------------------------------------------------------------------------

    Raspberry PI4 - 4GB w/ Debian Bullseye using Deskpi-Pro case :)

    OMV 6.9.16-1 (Shaitan)

    I checked and there was no space server min protocol=NT1.


    I have changed this and added the space but I get the same error.

    ----------------------------------------------------------------------------------------------------

    Raspberry PI4 - 4GB w/ Debian Bullseye using Deskpi-Pro case :)

    OMV 6.9.16-1 (Shaitan)

    Still doesn't do anything, keep getting same error. I think my next step is to try a clean install of OMV 7, instead of upgrade from OMV 6, and see if that gets me anywhere.

    ----------------------------------------------------------------------------------------------------

    Raspberry PI4 - 4GB w/ Debian Bullseye using Deskpi-Pro case :)

    OMV 6.9.16-1 (Shaitan)

    Quote from scarappypappy

    Still doesn't do anything, keep getting same error. I think my next step is to try a clean install of OMV 7, instead of upgrade from OMV 6, and see if that gets me anywhere.

    You should read what is going on on the Sonos support:

    mount a smb share on sonos at DuckDuckGo


    These are very disappointed costumers:

    Adding a Windows SMB Share, Step-by-Step | Sonos Community

    Also, a nice way to isolate the security hole that SMBv1 from the rest of the host can be seen here via docker:

    Use Docker SMBv1 Server to Share Music with Sonos | Stefandroid Blog


    Maybe a good way to sort it.

    Thanks Soma, I have a look at those. I'll let you know here if I get anywhere.

    ----------------------------------------------------------------------------------------------------

    Raspberry PI4 - 4GB w/ Debian Bullseye using Deskpi-Pro case :)

    OMV 6.9.16-1 (Shaitan)

    Quote from Soma

    Also, a nice way to isolate the security hole that SMBv1 from the rest of the host can be seen here via docker:

    Use Docker SMBv1 Server to Share Music with Sonos | Stefandroid Blog


    Maybe a good way to sort it.

    In the link above, the method he describes would use an additional RPI to mount the docker on. Although this is not an issue as I have a spare, could this be setup in a docker within OMV 7 as well?

    ----------------------------------------------------------------------------------------------------

    Raspberry PI4 - 4GB w/ Debian Bullseye using Deskpi-Pro case :)

    OMV 6.9.16-1 (Shaitan)

    Quote from scarappypappy

    In the link above, the method he describes would use an additional RPI to mount the docker on. Although this is not an issue as I have a spare, could this be setup in a docker within OMV 7 as well?

    I only saw it sideways, sorry.

    But if you already have docker running on OMV, it's only a matter of creating the container to your case.


    If I'm understanding it correctly, you don't even need a NFS share (which implies an external server or looping your network to the same server)


    For eg, create a simple YML with your music folder binded as a volume:

    All you need is to edit the /srv/dev-disk-by-uuid-XXXXX-YYYYY-ZZZZZ/music to your own


    Since the ports are the defaults of SAMBA, it might clash with your HOST SAMBA.

    How to bypass this only with MacVLAN which I can't help much since I don't use it.


    And since the posted image has no updates in the last 4 years, you can try to go with a fork that's more recent:

    adrianmusante/docker-samba: An updated version of the Samba Docker image, originally developed by dperson/samba (github.com)


    Good docking, ;)

    The following is my opinion and may not be 100% accurate.


    I have not found a solution for this, however I think I know the reason why. Back in Mar(??) 2024 Sonos did a major update of their mobile app, cloud infrastructure and software running on the Sonos system. It is my understanding that this update was a major clusterf#$%. This included the removal of a number of Sonos capabilities, including the ability to connect to files stored on another machine, e.g. a music folder on your NAS (amongst others).


    Sonos has confirmed that they screwed this up royally and are trying to fix a bunch of the issues. There was a story on Slashdot this morning that the CEO of Sonos has confirmed that they are unable to roll back to a previous version of the software and the latest version will have to be fixed. No time line for this.


    Currently I can run my Sonos 1 system with OMV V 6 because that is how it was previously setup, however due to changes in the Sonos SW I cannot manage any of the folders, changed, add, create any of my playlists as that ability was removed. I am able to use my current playlists as they existed before the rollout, but I cannot change anything in them.


    I think this may in part be why it cannot recognize OMV 7. Although I have a Sonos 1 system, I understand it also affects Sonos 2 systems as well.


    I think we'll just have to wait to see what Sonos comes up with for a solution. I also wouldn't be surprised if the solution coming will be geared towards Sonos 2 systems and trying to force (coerce, push, argue for, ....) Sonos 1 customers to upgrade to Sonos 2 (again).


    My 2 bits...

    ----------------------------------------------------------------------------------------------------

    Raspberry PI4 - 4GB w/ Debian Bullseye using Deskpi-Pro case :)

    OMV 6.9.16-1 (Shaitan)

    I heard Sonos is planning a rollback for their software.


    You tried this solution with an own docker installation ?

    Use Docker SMBv1 Server to Share Music with Sonos
    Sonos only supports the Samba v1 protocol, for which a dedicated Docker container can provide the connection.
    blog.stefandroid.com


    Or this one ?
    https://stan-miller.livejournal.com/357.html


    Unfortunately I am not able to adapt this solution for OMV... if it would work!?

    But if this works and someone would provide step-by-step instructions, I would be happy ;)


    Greetings

    I tried the stefandroid one using s separate RPi that I had laying around. If I remember correctly I kept getting a failure when the dockerfile was run. Unfortunately I do not have a sufficient background to troubleshoot the problem. At this point in time as my Sonos S1 works with OMV 6 I am happy to stay there at this point.


    An imperfect answer, but that's where I am.

    ----------------------------------------------------------------------------------------------------

    Raspberry PI4 - 4GB w/ Debian Bullseye using Deskpi-Pro case :)

    OMV 6.9.16-1 (Shaitan)

    I got it working ... but i need to activate

    Quote

    server min protocol = NT1

    and the key change was under extra options


    Code
    ntlm auth = yes
unix extensions = no

    Good morning. Glad to see you made it work. Could you please proivide


    a. did you use the Stan Miller method; and


    b. This is the edited (now) smb.conf file (added bold red lines)?


    Under the [global] heading add these lines:


    # enable v1 authentication for Sonos access and SMB v3 access for Win 10

    ntlm auth=yes

    client max protocol = SMB3

    server min protocol = NT1

    At the end of the file add a music share section, modify this to match your setup:

    [music]

    Comment = Pi shared folder

    Path = /mnt/sonos

    Browseable = yes

    Writeable = Yes

    only guest = no

    create mask = 0555

    directory mask = 0555

    Public = yes

    Guest ok = yes

    ntlm auth = yes

    unix extensions = no

    ----------------------------------------------------------------------------------------------------

    Raspberry PI4 - 4GB w/ Debian Bullseye using Deskpi-Pro case :)

    OMV 6.9.16-1 (Shaitan)

    I added my 2 lines to the OMV Config and chose SMB1 for Min Protocol Version !?

    No other things, no Stan Miller method or anything else. Just OMV 7 and the SMB/CIFS config.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login