Upgraded MacOS client and Synology Server to 2.65. Synology application starts and then stops. Tried reinstalling. No luck. Upgrade path was 2.64 –> 2.65
I’ve lost all my Muse Presets, Parametric EQ, etc.
I see in another thread on the same issue with QNAP a user is reporting “NAS Server” is not supported any more and Docker is the path forward. I would have happily switched to Docker as I use it for other things.
You should have required or warned users to execute a backup prior to this extensive of an update. I certainly would have done so. I found out too late that my Synology Roon configuration did not have a backup folder defined.
You should not have used a 0.0X release # for this extensive of an update. This should have been 3.0.
You should have notified Synology server users it was deprecated and to switch to Docker.
@John_McTurnan1 Agreed. Communication should have been handled much better. I’ve created a list of things for a post update review to improve these things going forward.
There was a notice about it in the April newsletter, but unfortunately it was at the end of the email
We also delayed and posted about it in the forum, but I’ve realized that many people didn’t see that either
In “theory” it should have gone out as an in app notification. I’m not sure how that system is supposed to work and not sure why it appears to have completely failed
Having said all of that… The intent wasn’t to drop support for NAS devices. We moved to net10.0 which requires a newer glibc library (2.27 released 8 years ago). We found out that QNAP hasn’t updated their version in just over 11 years. QNAP is working on new version of their OS, but it is still in beta. Newer versions of Synology should work. I believe if you are running at least Synology 7.2 or newer then the old Roon NAS app should work.
When we realized this was going to be the case we delayed the release and tried to come up with a solution so that anyone running at least QNAP or older Synology NAS devices would have an option instead of being left with nothing. Unfortunately, it isn’t the simpliest shift for people, but going forward it should help better isolate use from platforms that don’t update their dependencies. The expectation is that this’ll prevent things like this in the future.
There is definitely a strong argument that we probably should have considered moving to 3.0 instead of 0.0X. In hindsight, I’ve wondered about this a fair bit.
