Unable to Restore Backup on QNAP 453 Be after Upgrade (ref#MJ90D1)

[Jeffrey_Gilliam]

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

· I upgraded with the most recent release. I spent a day setting up container station successfully. Now I can’t restore the back up. Despite container station running properly( I think), it does not find the back ups. I got one message that said backup “root invalid”. I feel like I am almost there but can’t get over the last hurdle of restoring my back ups. I have it running on a QNAP 453 Be, with ssd feeding distributed audio throughout the house and backyard. HELP…..it is eerily quiet in my home!

Tell us about your home network

· ASUS ax 86u pro Aimesh system

[connor]

Hi @Jeffrey_Gilliam,

Thank you for your post and for your patience.

This is fundamentally just a file mapping issue and not something broken about the Backup.

When Roon is reinstalled via Container Station, the container needs to know where your backup folder lives on the QNAP. The “root invalid” error is a strong sign that the path inside the container no longer matches where your files actually are on disk. Start by opening File Station and locating your Roon backups folder. The exact path depends on what you named your shared folder and where you originally pointed Roon to save backups, but it will follow a structure like /share/YOUR_SHARE_NAME/RoonBackups.

Once you have that path, go into Container Station, open your Roon container, hit “Edit,” and check the Volume/Storage tab. The host path on the left side needs to point exactly to that folder. If it is blank, wrong, or pointing somewhere that changed during the upgrade, that is your culprit. Stop the container, fix the mapping, save, and restart, then try the restore again in Roon.

If you are not sure where your backup folder ended up, you can SSH into the QNAP and search for a folder named RoonBackups, or browse through your shares in File Station until you find it. We can help with that if you’re stuck.

Please let us know if this helps.

[Jeffrey_Gilliam]

Connor, thank you so much for taking the time to provide the advice. I would like to report that after several attempts to correctly map to my backups we were successful. It would not have happened without your guidance. Now, of course I have what I hope is my last problem. My Qnap 453Be feeds from its usb into a Douk U2 Pro digital converter, and then into an Anthem distributed audio amp. The problem that I have now is that I am only sending 24 bit, 44.1 kHz to the Douk. Before the update it was 24 bit, 192 khz. for the last year. I went back into the Docker configuration tool and created another configuration with the “USB audio doc” turned off, Hdmi audio is off,SMBCifs mount is on. I am not sure what the problem is, but any help you can offer would be greatly appreciated. I thought I had crossed the finish line only to see the damn thing move one me…LOL.

Connor, I decided to supplement my post with screenshots of my set up. After reading several posts from others having problems, I realize that my issue is probably easily fixable by someone who has a better understanding than I do.

[benjamin]

Thanks for the additional information and screenshots @Jeffrey_Gilliam! We’re close to complete success!

Looking at your screenshots, I can see you have Roon Server running in Docker on your QNAP and the container appears healthy (running, good CPU/memory stats). The logs show repeated chunk id: 2F entries which suggest Roon is actively communicating with the USB device.

The main issue, dropping from 192kHz down to 44.1kHz is almost certainly a sample rate/DSP configuration issue within Roon itself rather than a Docker or hardware problem. Here’s how I’d approach troubleshooting:

First, check Roon’s Device Setup for the Douk U2 Pro: In your Roon Remote app, go to Settings → Audio, find your Douk U2 Pro USB device, and click the gear icon. Look at:

• Max Sample Rate — make sure it's not capped at 44.1kHz
• Max Bits Per Sample — confirm 24-bit is set

If that doesn’t help, check the Signal Path: When music is playing, tap the colored dot (light bulb icon) next to the track to open the Signal Path. This will tell you exactly where the downsampling is happening, whether it's Roon applying DSP, or the endpoint reporting limited capabilities.

It would also be worth checking any MUSE/DSP Settings. A sample rate conversion rule could have been inadvertently set to 44.1kHz after the update.

If none of the above help, re-enable the USB Audio device in Docker. You mentioned turning USB audio off in a new config, for the Douk to receive high-res audio over USB, the container needs /dev/bus/usb passthrough enabled. Looking at image 6, I can see your compose config does include USB device passthrough, so confirm your active container still has that.

Can you share what the Signal Path shows when playing a hi-res track? That will pinpoint the problem immediately.

Thank you!

[Jeffrey_Gilliam]

Benjamin, thank you so much for the detailed troubleshooting instructions. Thanks to your help we have success! The problem with the 44.1 kHz was probably my fault. The sample rate conversion was not set to 192 khz. Somehow it was set to convert 192 to 192 but everything else was defaulted to 44.1 kHz. Once all sample rates were set to convert to 192, it worked perfectly. Again thank you to all who have helped us. I will reach in the future to deal with problems that I am having with the display no longer working. For now we are ecstatic to have music throughout our home again!