Topic title is the problem. Not a large Roon library nor a lot of audio processing. Not sure of what version I was running before I updated, but I think I have applied all updates as they were pushed to me, so I was probably at the last version before 2.65. I have a current Roon backup.
The Docker-based solutions I’ve seen so far all require DSM 7.3 which is not supported on the DS1515+. What is the next step?
I used the instructions here and after some fiddling, I could install docker on my system. 7.3. is AFAIK not a prerequisite for docker, it runs on lower versions as well.
It is unfortunate, that Roon pushes an update notification to user with running systems without discrete warnings. Not everybody spends time in this forum and got alerted to upcoming changes. I knew about the change, but it came as a surprise to me that the update killed my well running 7.3 CRieke app and messed up my backup location. Not very well executed Roon.
This is somehow true. But, as with any software on some platform you should always read the release notes first in order to decide if you want to update or not. But since roon server is rather marketed as some end consumer audio/music environment than as a music PC software (which it is) you may not see and treat it exactly like that.
What should have made things much less confusing for consumers is a pre-install check which detects if the offered update is actually compatible with your system. But such does not exist AFAIK.
FWIW - I’m running the Core on a Synology NAS 916+ which was on DSM 7.1.x. On another thread around here Roon server dont' start after after today’s Roon upgrade - #6 by Moonshiner there was a suggestion to do a manual update of the DSM to a 7.3.x version. After hesitating for a bit…I took the plunge and followed the Synology instructions exactly (step-by-step updating) and it all just instantly worked with Roon Core and Database suddenly all accessible again. Magic!
Only thing is I had recently done a complete back-up of the NAS, so had a level of comfort I wasn’t going to lose anything on the NAS if it all failed miserably. But in my case, all worked out fine. Big relief and I can get back normal life 
Manual upgrade is fairly easy for compatible models. Did that on another Synology that I run as a backup. You still have to install container and docker AFAIK unless you keep running the great CRieke app until it rides into the sunset.
Thanks all for the replies. My Synology setup is old but does the NAS thing with reliability and speed that meets my needs. With that in mind, I am not really interested in messing around with tweaks to DSM just to make Roon work. I think I’ll see if I can backlevel Roon first off. If not, I do have an available SFF Win 11 box that I could use as a Roon Core so……
There are instructions for migrating to the old “Docker” package that is compatible with your unit. Have you tried those?
I have gone through the (apparently new) “Installing RoonServer on Synology with Docker”. This set of instructions does have a ‘Method’ that addresses older versions of DSM which use the legacy Docker app. I’ll start down that road.
It is clear that the general assumption when discussing Docker and Roon Core on Synology is that DSM is at ver. 7.2 or later.
Synology still supports (but does not feature update) DSM 7.1.1.
‘Method 2’ in the ‘Installing RoonServer on Synology with Docker’ sheet addresses Synology DSM 7.1 or older using the legacy Docker app.
I installed the legacy Docker app on my DS1515+ without issues.
The url shown to retrieve the image in ‘Method 2’ on the Docker install sheet returns ‘invalid’.
There is a ‘Docker image URL is invalid’ thread which has a solution but that solution involves going to the Project tab in the app and creating a new Project. The legacy Docker app has no Projects tab - I assume that solution is referring to the Container Manager app which is not available on DSM 7.1.1
The legacy Docker app does have a ‘Registry’ category which seems like it might apply. I’ll open a support ticket and a new conversation asking where and what are the proper entries in the legacy Docker app to retrieve the roonserver:latest image.
All of this would have been avoided if the ‘bricks your server’ nature of the 2.65 update had been flagged in any reasonable manner.
Alerting @Stephen .
Hey guys,
I ran into what looks like the same issue on my Synology RS815+ running DSM 7.1.1.
After the recent Roon Server update, RoonOnNAS would no longer start properly. In DSM Package Center it looked like it was starting, but after a few seconds it went straight back to Manually Stopped / Run.
After some digging via SSH, the actual error was:
Failed to load .../RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/libcoreclr.so
error: /lib64/libm.so.6: version `GLIBC_2.27' not found
Failed to create CoreCLR, HRESULT: 0x80008088
On my NAS, DSM 7.1.1 only has glibc 2.26:
/lib64/libc.so.6
So the issue seems to be that the newer Roon Server build now expects GLIBC_2.27, while older Synology models/DSM versions only provide GLIBC_2.26.
I managed to get Roon working again by rolling back the Roon Server Linux x64 build to the previous version:
Roon 2.64 build 1646
The old build is still available here, at least at the moment:
https://download.roonlabs.net/builds/RoonServer_linuxx64_206401646.tar.bz2
What worked for me:
curl -L -o RoonServer_linuxx64_206401646.tar.bz2 \
https://download.roonlabs.net/builds/RoonServer_linuxx64_206401646.tar.bz2
RoonServer_linuxx64.tar.bz2
Uninstall RoonOnNAS from DSM Package Center.
Rename/back up the existing RoonServer application folder instead of deleting it, just in case.
Start the RoonOnNAS manual installation again through Package Center.
During the installation, choose the offline installation option and point it to the renamed RoonServer_linuxx64.tar.bz2 file.
Start Roon Server and restore from your Roon database backup if needed.
After doing this, my Roon Server came back as if nothing had happened.
I would definitely not recommend trying to manually upgrade or replace glibc on Synology DSM — that feels like a good way to break DSM itself.
Maybe this is something @crieke could work around in RoonOnNAS, although I’m not sure if that is even possible if the newer Roon/.NET runtime itself requires a newer glibc. The major issue Synology NAS owners will experience is that dockerized RoonServer needs DSM 7.2+ which is not supported on some older devices.
For now, this rollback seems to be a workable recovery path, but probably not a long-term solution. I suspect future Roon updates may hit the same problem again on older Synology units. Long term I’ll probably move Roon Core to a small x86 mini PC and keep the Synology just for music storage over SMB.
Sincerely,
Adam Palaczyk