Hello everyone, I’m having this strange problem.
For reasons I won’t list so as not to overdo it, I was forced to use the USB recovery kit for my Merging Nadac Player. The reason is that I could no longer see the Roon server at all. When I restored the Nadac Player via the USB recovery kit, I found myself with Roon 1.0 build 40 operating system and Roon server software 1.3 build 193, and everything worked. I can see the server with the Roon Remote Legacy app, which immediately offered me an update. After downloading and installing the update I see Roon operating system 1.0 build 148 and always Roon server software 1.3 build 193. Now, if I try to update from the legacy Roon remote app it gives me an error before downloading, obviously the Remote 2.0 app does not see the Roon Server, if I try to update from the web UI, even after following the guides in the various topics, such as inserting the roon-production.bin file for the update to Roon 2.0 in the Data / Reinstal folder, or even inserting the bits file inside the Roonserver / Database / Registry / Core folder, after a while it gives me the error code “status”:“failure”,“exitcode”:40 and from that moment the Roon server communicates “not running” and there is no way to reactivate it. So, since I restored the NUC disk image of the Merging Nadac Player to its original factory state, with such an old version of Roon and the Roon server, how can I update to the latest versions of Roon 2.0? Of course, I also tried using Roon recovery, downloaded the Roon software to a bootable USB stick, and installed it as recovery on the NUC. However, I obviously lost the Merging codes, and afterward, it was no longer seen as a Nadac Player but as a standard ROCK, so there’s no way to get it to work, even though the operating system and server were working perfectly. Thank you for your attention, and I look forward to hearing from you.
Alessandro
Hello @Alessandro,
Thank you for the detailed description — I know this situation is frustrating, especially when working with older integrated Roon builds.
Unfortunately, we don’t have insight into how Merging integrated Roon Server into their NADAC Player firmware. Their units do not run the standard ROCK/Roon OS image, and the update/upgrade process is handled entirely by Merging’s own software layer.
From our side, we can only confirm what is publicly documented on Merging’s product page:
According to their marketing and specification materials, the NADAC/Merging Player platform supports Roon 1.3.1, and all Roon-related updates on those devices must come through Merging’s own firmware update system, not through the Roon Remote apps or manual file placement.
Because of this integration model:
- We unfortunately cannot provide an upgrade path to Roon 2.0 for a Merging NADAC Player
- We have no access to their factory images, licensing keys, or update packages
- The update failure with exit code
40means
Unable to unmount Roon application partition. Prior to reinstall of RoonOS / Roon the system will attempt to unmount the partition on which RoonServer is installed. This error indicates that the filesystem cannot be unmounted.
Given all of the above, the safest next step is to contact Merging Technologies Support directly. They are the only ones who can:
- Provide the correct firmware containing their supported Roon version
- Restore the Merging-specific software environment (including device identification)
- Confirm whether your particular hardware revision supports anything beyond their integrated Roon 1.3.x build
I’m very sorry we can’t provide a direct solution here, but Merging will be able to guide you through the correct recovery and update process for your unit.
Please keep us posted — we’re happy to assist with any Roon questions once the device is back on a supported firmware.
This is their guide for updating.
Thank you so much for your detailed reply, Vadim. I think I’m starting to understand the mechanism. In any case, I’ve forwarded your reply to the Merging service, which I was in contact with recently regarding other issues. Thanks again, and I hope to resolve this issue soon. Alessandro
Thank you so much, MJW. Just this morning, while continuing to research online, I discovered that the Merging firmware also contains files and information about the Roon Core. I know the firmware update procedure using the Merging guide, but I noticed that when I restore the Player with the USB recovery kit, going to the device info always shows the latest firmware available, so I didn’t think I could try a new firmware update first. I’ll keep you updated, hoping to be able to help other users with Merging devices. Best regards, and thanks again.
Alessandro
Hello @Alessandro_Azzaroni
Thank you for the update. Please let us know if you need anything else from the Roon support side.
Hi everyone, thanks to the help of Merging support (truly impeccable!), I managed to install the latest available ROCK image for the Player. Now everything works! Just to be clear, even for users who might have the same problem in the future, the Merging Player firmware does not modify or affect the NUC or the Roon system. It’s the WEB UI, which, having the Merging vendor codes and the system identified as Nadac Player, and not generic ROCK, fetches the specific releases for the product. The problem with restoring a Merging Player to factory defaults is that the versions are really too outdated to be updated; you absolutely need a more recent NUC software image for Nadac Player. Thank you so much for the support!
Alessandro
The latest build for supported hardware is 2.1 (September 2024.)
Hello @Alessandro_Azzaroni
Thanks for the feedback here. Since this is not a current feature of Roon, I would recommend also posting your suggestion in the Feature Suggestions section of the site.
Our product team and developers keep a close eye on that category, so that’s definitely the best place to propose a change like this and get feedback from the Community.
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.