Synology - DSM 7 build 41882 - Breaking Changes

WARNING

DO NOT UPGRADE TO DSM 7 Release Candidate.

For those who have upgraded –

4 Likes

… too late for me unfortunately :frowning:

Can’t wait for a fix as I tried all I could for a couple of hours to understand what was wrong with y setup, until I saw this WARNING message right now.

I have just upgrade tp DSM 7.0-41882 RC and couldn’t find anything wrong with my current Plex server version 1.23.2.4600, all is working as intended. I did shut down the Plex server prior to DSM upgrade.

I guess until either Plex or Synology say what the breaking change is, then we won’t know if it effects current builds installed, or updates to future builds. I’m just hoping it’s nothing too serious.

You have 41882 ?

They sent me 41876

@ChuckPa I’ve got DSM 7.0-41882, which for some reason on my plex server it was set to automatically install the update. Though all my other Synology NAS’s are set to just notify when there is an update. I’ve now set my plex server to also just notify.

Synology gave me DSM 7.0-41876

41876 does not allow PMS to work.

:crossed_fingers: they fixed the problem for DSM 41882 ?

I am testing now

1 Like

So far not seen any issues with Plex using 41882

I have 41882 (freshly installed a new NAS today) and I cannot install Plex version higher than the one available through the Synology Beta channel package repository, i.e. 1.21.0.3744. Manually downloaded packages (1.23.1, 1.23.2 and higher) are all returning “Invalid File Format”, carefully reading related threads and following steps didn’t help.
Maybe not related to RC then?

1 Like

Using 1.22.3.4392 on DSM7 41882.
cannot update PMS to 1.23.1.4602 because of “Invalid File Format” in Synology Package Center. Otherwise currently installed PMS works with 41882.

I cannot install on DSM 7.0-41882 on ARMv8

This is madness

It seems Synology has decided to REQUIRE “Synology Signed Packages” ONLY

I have 1.23.2.4600, then DSM updated to 7.41882. Seems to be working fine

@jaime.guillermo

If you have it installed – then upgrade – you are fine.

Now you’re stuck

@ChuckPa Indeed. But hey, they say patience is a virtue. :slight_smile:

try using Google Chrome to install the package, not Edge

@ChuckPa Does this mean every time you release an update, you have to wait for Synology to sign it off?