OK, we found the issue, and unfortunately there is no fix, only a workaround.
The problem is that the Linux kernel, with mount.cifs options of ‘nounix’ has a bug a share can’t be mounted both with and without the ‘nounix’ option. The result is what you have seen here, and something we have been able to reproduce outside of Roon, on multiple different Linux versions and platforms.
Roon has to mount with the ‘nounix’ option as it ensure better compatibility with Windows shares (got user complaints about missing files when they would normally be mangled by smb).
Now, you have 3 options to work around this bug:
- stop mounting twice and let Roon do your mount exclusively. Nothing changes in Roon, the only change is outside of Roon.
- Stop mounting twice and you do the mount completely yourself. Change the location of the storage folder inside Roon to be whenever your mounted it. Just ignore that the “add network share” exists inside Roon.
- Mount the share with the ‘nounix’ option outside of Roon. Nothing changes in Roon, the only change is outside of Roon.