Windows Server 2012 with RAID5 and several SMB Network shares with my music
When I setup Roon
it successfully connects to my SMB shares and adds all my music
BUT anytime you restart Roon / reboot ROCK OS
It can no longer connect to the SMB network shares
the only way to fix it is to remove the SMB shares and re-add them
Now when my ROCK was stable, that was no big deal. But recently it isn’t performing with Build 274 with my NBR and I have to CONSTANTLY re-start it. That is causing me to have to fix the SMB Network shares EVERY time.
Please fix. I’d be happy to test a fix or provide more details. Just let me know.
Hi @Mohammed_Samji ---- Thank you for the post and sharing your feedback with us. The insight is very appreciated!
Moving forward, to help us better understand this behavior you are experiencing (i.e losing the SMB network shares) I would like to enable some diagnostics on your account, but first may I very kindly ask you to please reproduce the issue once and note the time when the observation is made.
Looking forward to your follow up, Mohammed. Many thanks!
-Eric
Ok, I just rebooted Roon Server on my Intel NUC running ROCK OS.
As soon as Roon came back up, if I launch the Roon Client from any Device (PC, iPhone, Andriod Phone) it now shows that all of my SMB shares are no longer available.
The error under Setttings -> Storage -> Folders (where I see my SMB Shares) is: "The Drive is not available. Check the drive or edit this folder if its moved.
There is no way to recover. Each time I have to remove the SMB folder, and re-add it.
Once its re-added, it works perfectly until Roon Server is re-started.
Confirming that we’ve received the report. I will be getting all of your information/feedback (along with the diagnostics report) into a ticket for analysis by our tech team shortly.
@Eric was going to follow up, but I can tell you we looked at this today, and we’re nearly ready to pass it off to QA to reproduce and write up as a ticket.
One piece of information I was missing was a log of the NAS being successfully added after this process:
Eric was going to make sure we got time stamp for that, since the last diagnostic report we generated was unfortunately from right before your post above:
Sorry about that
I can generate another report now, but I don’t want to do it if the logs have rolled over from 5 days ago. I hate to ask again, but would you mind running through it one more time and letting me know the timestamp for the failure, and the resolution, then I can get what I need? Apologies for making you jump through another hoop here.
