[Fixed in RoonOS #279] B274 RoonOS 3.0 Update Failure (exitcode 40)

Early Access
1

I am currently running my Roon Server on the Early Access branch and have run into a blocking issue.

My setup is currently showing:

  • Operating System: Version 3.0 (build 274) earlyaccess

  • Roon Labs Software: Version 1.0 (build 18) production

  • Roon Server Software: Version 2.70 (build 1665) earlyaccess

Yesterday I tried to use the Reinstall button via the Web UI, I saw that it downloaded the new OS. After this I saw the following error:

There was an error installing the software. Please take a screenshot and contact support. {"status":"Failure","exitcode":40}

I have already tried a full power cycle of the Titan and restarted my network gear to clear any potential download caches, but the Web UI keeps failing immediately with the exact same exitcode:40 when I open it.

I also tried to put the roons-earlyaccess.bin in the storage map of my titan, but it continued with the same error.

IMG_5774
IMG_57741320Ă—704 42.5 KB

Bekijk recente foto's
Bekijk recente foto's1320Ă—641 60.3 KB

3

Not a solution, but tagging in to say I am having a similar issue with my Nucleus One. My only difference is that I am on Roon Server Version 2.67 (build 1661) production, and I got this same error message (multiple attempts) trying to use RS version 2.7 (build 1663 and also build 1665). I even tried using different browsers to access the Nucleus admin page, just in case it was a browser cache error.

Rebooting the Nucleus from the Admin page, or physically, restores Roon to the previous state and it runs great as it had been. So, not overly concerned, just wanted to see the improved speed and stability that has been documented and discussed.

5

Thanks for report, we are looking into this issue

6

EA 2.70 (build 1668) earlyaccess does not work either. Same error message.

7

This is a RoonOS problem, We’ve made the fix, but it is pending next RoonOS EA release. Hopefully, next week

8

Thank you for the confirmation of the issue and pending solution. I’m happy to wait and glad to take a break from troubleshooting things on my end, as everything works great once the system is rebooted after the failed attempt.

9

Just wanted to report back that the RoonOS EA update was received automatically, which was nice. Once I realized it was already updated, I did a reinstall for the EA RoonServer, and that was also successful, without the exitcode error. My USB attached SSD for my local music collection was “read-only” so I did a “Check & Repair” and that was successful also.

Next, I can move the Nucleus One to my main Audio System and have it replace the Rasperry Pi RoPieee and try out the HDMI connection to my TV.

So, ALL IS RIGHT IN THE ROON AUDIO WORLD AGAIN!!!

Please make sure the entire Roon Dev team is given a huge thanks. Really enjoying all the truly meaningful progress with all these iterative steps, and new features.

10

I previously reported in a different thread that when I tried to roll RoonOS 3.0 back to production to test a different issue (now resolved), I was getting an exitcode 40 failure.

Last night I updated to RoonOS 3.0 build 279 using the built-in update mechanism through my Roon desktop client. I then performed a reboot and let it run overnight. This morning I attempted to roll back to production again. I can confirm it worked without issues.

I played one song on RoonOS 2.1 build 271 before switching back to RoonOS 3.0 build 279. Tailscale also remained signed in moving both directions.

image
image961Ă—1075 41.5 KB