I have a persistent SMB authentication issue on my Nucleus+.
• Login with roon / roon is rejected • Guest access works but is effectively read-only • Internal Music Storage (8 TB Samsung 870) is present, indexed and plays normally • Music is fully visible in Roon
What I already tried: • Reinstall of Roon OS via Web UI • Full power cycle • Different Ethernet cable / different power outlet
Additional observation: • The unit previously entered a boot loop caused by unstable power. • After fixing power, the Nucleus is now stable, but SMB authentication remains broken.
This looks like a persistent Samba / authentication state that does not reset with an OS reinstall.
Please advise on recovery steps or whether the unit needs service / replacement.
We’ve reviewed the diagnostics from your account, and everything looks correct on the system side:
The internal storage is mounted properly
All directories and the internal music storage are mounted read/write
File system permissions and ownership are correct
There are no signs of storage or mount issues
On Nucleus / Roon OS, SMB access is intended to be used via guest authentication, and the internal storage should be writable when accessed as a guest.
Based on the diagnostics, the Nucleus itself is behaving as expected. If you’re seeing read-only behavior when accessing the share, this is most likely being enforced by the client OS or SMB client configuration, not by the Nucleus.
At this point, there’s nothing on the Nucleus side that requires correction. We recommend double-checking the SMB mount options or credentials handling on the client machine.
Let us know if you have questions or need clarification.
Thanks for the update! We’d be happy to take a closer look at the issue Roon remote on your Mac - let us know a more specific date and time the next time this happens.
This said, it does appear to be an issue that is more centered around the Mac itself versus your Nucleus, as @vadim has mentioned.
None the less, we’d love to help further if possible. Thank you!
This thread is now closing due to inactivity/lack of response. You can reactivate the conversation by simply submitting a new tech support request here if you require additional support.