· I need to restore my Roon backup after installing Roon in Container on a QNAP NAS (called "Music"). Installation was successful (Roon running in Container). I would like to restore a backup however I receive a "There was an Unexpected error: UnexpectedError" message.
I believe I am incorrectly entering the Network share location in the "Add network share" to identify the folder that contains my backup and would like assistance.
My Roon backup is on a QNAP NAS "Metcalfe" in a shared folder "Roon Auto Backup" within which there is a directors called "RoonBackups".
The Username for Roon access this folder is "Roon". I have correctly entered the Password. I do not require a Workgroup. ("Roon" is assigned to the "everyone" user group.)
Tell us about your home network
· Roon backup on a QNAP NAS TS-251B running QTS. 5.2.9.3451. I use a MacBook Pro to access both QNAP NAS drives (the one with the backup and the one running Roon in the Container). Both NAS drives hardwired to Asus router.
The errors are different between the different cases. I’d start with finding out what your shared folder name really is. You wrote:
But then you tried “Roon_Auto_Backup” with underscores in some of the screenshots. I suppose you tried it that way because you were out of ideas but if “Roon Auto Backup” is correct, “Roon_Auto_Backup” can’t work.
If “Roon Auto Backup” is correct, the spaces might get in the way. Spaces in network share names are problematic. You may have success if you try it WITH the quotes, exactly as “Roon Auto Backup”, but you might be better off by eliminating the spaces in the share name to begin with.
I’d also go with the smb:// notation, because this is what Linux-based OSes like QTS usually use, while the \\ notation is a Windows thing.
Finally, in some attempts you left out the share name altogether and got an „invalid network path“. You HAVE to include the share name.
I don’t think that running in the container has anything to do with it because the Roon Server in the container definitely has network access (or nothing would work), and you said the backup share is on a separate QNAP machine (Metcalfe) that is NOT the machine where your Roon server runs, and you are using the credentials of the “Roon” user account that exists on Metcalfe to log into the “Roon” user’s account on Metcalfe. Which makes me ask: you ARE doing this, right?
Other than that, “UnexpectedError” is not a super helpful message and can probably mean a bunch of things, but I have often seen it here on the forum when the share name was probably wrong. It may help if you post a screenshot of the share properties from Metcalfe.
And if you don’t have other reasons to learn how to access an smb share on Metcalfe from the Roon Server QNAP, maybe you can save time by simply copying the backup folder to a USB disk that you connect to Metcalfe and then plug it into the Roon Server QNAP and copy it into the backup folder that is accessible from the container.
Here are screenshots of the share properties for the folder “RoonAutoBackup”. I see that even though I changed the Name to eliminate the spaces, the Path remained with the spaces. Could that be an issue?
I would prefer to get this addressed because I use QNAP’s HBS 3 to automatically backup up my “Music” NAS to both an attached USB drive and to “Metcalfe”. And Roon backs up to “Metcalfe” which in turn backs to a USB attached to “Metcalfe”.
Perhaps. You could also create a completely new share without spaces and try if you can connect to that. If you can, copy the folder that contains the backups into that
And when you created the container, did you follow the official guide? And if yes, did allow the container to use SMB shares? Also, if the backups are on the same NAS you better change the backup path you setup when creating the Docker Application to match the backup path. Or simply copy your backup(s) into the new backup folder.
I followed the official guide. Only thing I changed was where my music was located. It’s in the “Music” folder under the shared folder “Multimedia”.
I’m not a techie so I missed the option? to allow the container to use SMB shares. It would be helpful to know where that is one when creating the application.
Along the same Iines, my Roon Server app was located on a flash drive attached to my “Music” NAS that contained my FLAC, DSD files (and on which the Container operates). Is it possible for the container to use that as the place for the new version of Roon? Or does the new version have be stored on the NAS drive itself? If I can set up the new version to mimic my old setup, it would be ideal so I can take advantage of the speed of the SSD rather than the hard drives. on the NSA.
In case others are facing the same issue, here’s what finally worked.
First I signed in to the NAS using my default admin user/password rather than the “everyday” login I had been using. I then removed the prior Roon Container app, deleted the Roon folders in the Container folder on the NAS. I also moved the Roon NAS Server on the SSD to a new folder" “Old NAS Server”.
I then used the settings below per your suggestions above:
Unfortunately, after Relaunching, I was back at the screen asking if I wanted to Login or Signup or Restore a backup. Because I was expecting that Roon would start on my Home page, I selected to Restore a backup.
The second time around I got wise and selected to Login. At that point I ended up having to deauthorize the prior Login and Roon launched perfect.
Thanks for posting the details of your solution. I was struggling with a similar problem and hadn’t thought to deauthorise the existing instance. Doing that sorted my access to Roon which wasn’t working after moving the Server to a container on my QNAP NAS.
@Roger_Morrow We are glad that the issue is resolved.
@Cosmic_Encounter As Pacoinmass and Roger_Morrow confirmed above, the way out of this loop is to select Login instead of “Restore a backup” after the initial restore is complete.
When you do this, Roon will prompt you that your license is already in use. Simply select the option to Deauthorize your previous native QNAP core. Once you deauthorize it, your new Docker instance will take over the license, and you will be taken straight to your Home screen.
Give that a try and let us know if it gets you back up and running!
but if “Roon Auto Backup” is correct, “Roon_Auto_Backup” can’t work.
