Hi @JF_Basin,
Thanks for writing in, and sorry for the disruption.
What you’re experiencing is directly related to a change in Roon’s minimum system requirements that took effect with the latest release (build 1653). Roon now requires glibc 2.27 or later and OpenSSL 1.1.1 on Linux. From what we see in diagnostic servers, your operating system runs an older Linux kernel that falls below that threshold. This is why both the existing NAS server stopped working after the update, and why a fresh install on the SSD is getting stuck.
Roon has released an official Docker image specifically to address this situation. Your Synology very likely meets the hardware requirements. Docker runs a containerized environment on top of your existing DSM, bypassing the kernel/glibc limitation entirely.
Roon has a dedicated guide for migrating from your existing native installation to Docker here:
Installing RoonServer on Synology with Docker – Migrating from a Native Installation
One critical step before you begin: before creating your final backup, you must disable all watched storage folders in Settings → Storage. If you skip this, Roon will treat all your files as new after the migration and you’ll lose your listening history and edits. The guide covers this in detail.
For further context on why this change happened and what systems are affected, see the announcement: [UPDATED] Roon Minimum System Requirements Are Changing
Let us know if you hit any snags during the migration and we’ll help you through it.