SMB v1 requests fail on Roon ROCK to QNAP network share (ref#MXRGF0)

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· SMB v1 requests fail from Room ROCK Version 2.1 (build 271) to QNAP network share every 5 seconds

Tell us about your home network

· QNAP does not accept SMB v1, it is depreciated. Why is Roon ROCK using it? Roon works as normal ....

Hello @colin and welcome to the forum.

Because some older, and maybe even some current devices from audio manufacturers, may still depend on that protocol. Roon tries different SMB versions, starting from the oldest one (v1), to newer ones until it can connect so Roon should still be able to connect to a share if SMB v1 is denied but v2 is supported.

Hello @colin

Thanks, BlackJack, that’s correct:

Original text

Roon Server negotiates SMB starting from the oldest version and works its way up until it finds one that connects, which is why things keep working normally even though the v1 attempts get rejected on your QNAP.

To add a bit more: this negotiation behavior is part of the current file-sharing stack, and it’s being modernized in the upcoming RoonOS 3.0 update, which moves to Samba 4. That’s the fix for this, rather than anything you’d need to change on the QNAP side. We wouldn’t recommend re-enabling SMB v1 on your NAS just to quiet these log entries, since QNAP deprecated it for good reason.

For more on what’s changing:

We don’t have an exact release date to share yet, so please keep an eye on our release notes for when it lands.

Ah, OK. Thanks for the explanation! It’s annoying but not the end of the world. Maybe I’ll just exclude that from the logs as it’s filling them up nicely.

Thanks also Vadim. There’s no way I was going to re-enable SMB v1! I do see a valid connection as it progresses up the SMB versions. Just thought I might be able to exclude the Roon ROCK from the smb logs somehow. I will keep an eye on the v3.0 update.

Hi @colin

We need to correct something from our earlier reply in this thread. We told you that Roon Server negotiates SMB starting from the oldest version and moving to newer ones. That’s backwards: it actually tries the newest version first (2.1, then 2.0, then 1.0), stopping at the first one that connects. Apologies for the mix-up.

More importantly, when we looked at the full diagnostic logs rather than just the summary, we found this isn’t just background negotiation noise like we first assumed. Your hd audio share specifically is not mounting at all right now. We can see repeated connection attempts roughly every 5 seconds, and every single one fails, across all three SMB versions Roon tries, not just SMB v1. Your Music share on the same NAS is mounting and working fine, so this looks specific to hd audio rather than a general SMB v1 compatibility issue.

A few things would help us narrow this down. Could you please check in Roon under Settings > Storage whether the hd audio location currently shows as available, or whether it shows an error or offline status? Could you also please confirm on the QNAP side that the hd audio share still exists under that exact name, and that the Roon user account still has read/write permission to it? If anything changed recently on that share (renamed, moved, permissions edited, or SMB1 handling changed specifically for it), that would be useful to know as well.

We’ll hold off on further explanation until we hear back, since we’d rather confirm the actual cause than guess again.

Hi @vadim.

Interesting. I did have an HD Audio folder/share too but had multiple HDD issues recently on the QNAP followed by the Roon account locking on the QNAP. I never bothered to reinstate it in Roon and today I removed it! The share is reinstated on the QNAP and probably just needs reconnecting, but I barely used it. The relevant permissions should have been given to the roon account but I may not have bothered! Trying SMB versions in descending order does make more sense. I think we can call this one known, thanks everyone for your help.

Hi @colin

Thanks for the update and for tracking that down. That explains it well: HDD issues on the QNAP followed by the account lock would do exactly this, and since the share was never reconnected in Roon, it just kept trying and failing in the background. Removing it was the right call.

Glad the SMB version order made sense once we walked through it. Good to hear the QNAP side and your Music share are unaffected throughout.

We’ll mark this one resolved. Thanks for closing the loop, and please reach out if the HD Audio share gives you any trouble once you reconnect it.