I upgraded my Mac Pro (Late 2013) to run MacOS Sierra (10.12 Beta).
Once Roon started up it could not mount SMB disks from my Synology 1511+ any longer.
I removed them from the settings and tried adding them again.
From the beginning with the same settings using the following URL, smb://diskstation/Music with correct username, password and workgroup. I also tried other combinations with and without username/password/work group as well as IP address.
The result was all the same, Roon could not connect to the remote server.
Installing Roon Core on a MacMini running OS X Yosemite, worked fine and using the Mac Pro with Sierra as a Remote works fine i, including local playback.
Is this a known problem and if so is there a way around it?
Never a good idea to install a beta OS on a system you actually want to do something useful.
If thereâs any incompatibilities between the SMB implementation in Sierra and the way Roon handles things, these will be straightened out after release for sure, but it would be a bad allocation of resources chasing compatibility with an OS thatâs in an ever-changing beta cycle.
Obviously, I made sure to have a fallback solutions provided including another Roon Core Server and a backup of the Mac Pro before upgrade, so no loss of service.
A question and a comment: 1) have you set Synology File Services to accept SMB 3 via the advanced settings in the WIN File Services control panel? 2) thereâs a lot of discussion online about poor SMB behavior in recent OS X versions â Iâve had trouble with incredibly slow access to large Synology folders over SMB in El Capitan 10.11.6.
Hi @qdtjni ---- Thank you for the feedback and my apologies for the trouble here. In regard to your question, we can not guarantee stability with pre-release os builds, but we can certainly take a look for you
I will be contacting you via PM momentarily with instructions on how to retrieve and upload logs to our servers. Thanks!
Interesting tidbits: when running Roon as root â do not try this on a functional install! â (sudo /Applications/Roon.app/Contents/MacOS/Roon), it mounted just fine:
The simple reason why it doesnât work as normal user but works as root is a change of permissions on /Volumes.
In older version of the OS the permission are as follows:
drwxrwxrwxt
But in the Beta MacOS Sierra it is:
drwxr-xr-x
It both case the directory is owned by root.
If you in MacOS Sierra changes it to drwxrwxrwxt, it works but after reboot, itâs set back to the non-working permissions.
I installed the release candidate earlier today.
Iâll try setting the permissions back to workable permissions and see if they remain after a reboot.
If they donât there are multiple way to work around, for instance setting SUID bit for executables, having a root cronjob set the settings ever so often, etc.
Just tried with a dirty hack, adding a chmod to rootâs cron.
As expected, it did work.
jmy-mp:/ johan$ sudo crontab -l
Password:
/bin/chmod a+rwxt /Volumes
Roon starts fine and can mount the SMB shares.
However, this is obviously not a permanent solution.
So it would seem like Roon has to access SMB shares directly without mounting, if that is possible in MacOSâŠ
Hi, Iâve merged you post into this existing topic, you will see the issue you reported is being worked on and for now there is a workaround (see qdtjni Johan N) post above.