Tried to update from build 281 to the new build 282 using the update button in the web ui and got the following error:
RoonServer cannot be restarted via the Web UI either.
A reboot brings RoonServer back up and running.
WebUI reports build 282 to be installed yet still offers the update button to build 282:
Roon App however reports build 281 to be installed and also prompts for update.
EDIT: Triggering the update from the RoonApp and not the Web UI has worked in the third attempt.
I had a similar issue but after a reboot of the NUC, all was fine…
I updated through the app and no issue at all
Same for me…I’ll update in the morning in the app rather than the web UI
How does one “update in the app”? I only know how to update Nucleus via the web UI.
… which is kind of irritating, considering I can update EVERYTHING ELSE from within any one of the remote apps.
Settings > About in the app. It lists only the RoonServer version in the Nucleus/ROCK box, but if there is a RoonOS update it is advertised as well and installed when you run the update.
Ah, got it. I don’t use the Nucleus as a server (long story, it basically just functions as a bridge in my environment), so it doesn’t show up in the app as a target for upgrade even though the server is running.
Then you probably don’t need RoonOS 3.0 on it either 
This is weird, we are going to look into that on Monday. Thanks for sharing! cc @Paul_Argue
I saw the same error message last week on b281 but wasn’t paying 100% attention so assumed I had made a misstep.
Reboot of NUC cleared it.
Paying attention now…
I haven’t manually pushed my system to B282 and yet I don’t see an update on the /about page in roon.exe. (as described by @suedkiez)
It’s possibly more ambiguous (for me at least) as the web GUI shows this
Version 3.0 (Build 282) ready suggests to me that B282 is running and ready, but, 
suggests that the update is available. Which is it?
I have not manually activated any RoonOS update for the recent updates but they all seem to happen by themselves (100% certain of this as I was away for the last two so cannot have pushed update for them).
For Roonserver, I can set whether to allow auto-update or not.
So, I proceed to action the update (even though it suggests I already have it !?!)
This leads to this which is what I saw on B281
Reboot NUC from the GUI button
So, I have to hard boot the NUC to get past this (I have reported this before with LG OLED attached to the NUC)
Physical reboot works and I am back to this
So, it looks like the RoonOS update process is a bit broken. And the HDMI functionality doesn’t work from a soft reboot.
OK…totally unclear in that case as that section is titled Roon Server. Maybe that is where I have been activating the RoonOS updates previously as I have assumed the update is for Roon Server.
@vova suggest add this to the list of things to make clearer.
The most likely reason is that /tmp is full. It’s an in ram filesystem so rebooting it should clear the space and allow the install to complete. I thought there was an error code included with that dialog so will make sure that comes up. Also adding more checks before starting the install.
Rebooted mine several times and it still hangs downloading the larger (OS) update - gets to 431, 432, something like that, then just hangs.
I rebooted a few times also and activating the update via the web gui fails.
Activating the update via the settings/about page of the roon app succeeds.
I am having the same issue, where upgrading from the web interface resulted in an error, and the server not being able to restart without a reboot. Running 281 trying to install 282
At the same time, upgrading from the app wasn’t working either. I currently run the server using ROCK os in a vm on Proxmox and had 4GB of RAM assigned to it. As the above post suggested, the tmpfs was probably getting full because VM RAM usage was maxed out. I bumped it to 8GB RAM and it upgraded to 282 no problem.
Meanwhile, I moved Proxmox to a new version this past week as support was ending for the older version I’d been running. I’ve noticed since then I am having frequent playback dropouts which never occured on this system before in over 2 years using the setup. Now I don’t know what to blame between Proxmox and the fact I am running early access Roon. This is outside the scope of this thread.
I am now trying to revert to production version and I am getting the same error when doing a reinstall from the web interface. I can’t trigger a reinstall in the app in this case, so my thinking is there might be an issue with the state of the upgrade process in early access since 281?
