DSM Update Version: 7.2.2-72806

[SynoMan]

(2024-09-11)

Important Note​

1. After installing this update, you will not be able to downgrade to a previous DSM version.
2. This update will restart your Synology NAS.
3. For the models below, you can only download the upgrade patch from Synology Download Center because you won't receive notifications for this update on your DSM.
   • FS Series: FS3017, FS2017, FS1018
   • XS Series: RS18016xs+, RS4017xs+, RS3617xs+, RS3617xs, RS3617RPxs, RS18017xs+, DS3617xs, DS3617xsII, DS3018xs
   • Plus Series: RS2416RP+, RS2416+, DS916+, DS716+II, DS716+, DS216+II, DS216+, DS1817+, DS1517+, RS2818RP+, RS2418RP+, RS2418+, RS818RP+, RS818+, DS1618+, DS918+, DS718+, DS218+, RS1219+
   • Value Series: DS416, DS416play, DS216, DS216play, DS116, RS816, DS1817, DS1517, RS217, DS418play
   • J Series: DS416slim, DS416j, DS216j, DS418j, DS218j, DS419slim, DS119j
4. Starting from this version, the processing of media files using HEVC (H.265), AVC (H.264), and VC-1 codecs will be transitioned from the server to end devices to reduce unnecessary resource usage on the system and enhance system efficiency. These codecs are widespread on end devices such as smartphones, tablets, computers, and smart TVs. If the end device does not support the required codecs, the use of media files may be limited. Refer to this article for workarounds. In addition, please note the following exceptions:
   • Surveillance Station on DSM will continue to support server-side processing of AVC (H.264) streams, see the release notes.
   • Deep Video Analytics (DVA) series models and VisualStation clients will retain support for AVC (H.264) and HEVC (H.265) codecs.
5. To ensure package compatibility, Advanced Media Extensions (AME), File Station, Media Server, Surveillance Station, Synology Drive, Universal Search, Synology Photos and Snapshot Replication will automatically update to the latest version.
6. Video Station is not available on DSM 7.2.2. Refer to this article for workarounds to stream videos to end devices.
7. Updated Storage Manager to 1.0.0-00502 to fix issues. For more information, see the release notes.

Compatibility & Installation​

1. The following third-party packages are currently incompatible with DSM 7.2.2. Compatible package versions will be released in the future, and this list will be updated accordingly:
   • BRAVIA Signage
   • TeamViewer

What's New​

1. Added support for selecting whether to verify response or assertion signatures for SAML SSO clients.
2. Supports customization of package installation, upgrade, and uninstallation wizards for third-party package developers. Learn more

Fixed Issues​

1. Enhanced protection against deletion of immutable snapshots.
2. Enhanced file system error recoverability.
3. Fixed an issue where backing up WriteOnce shared folders in Hyper Backup might occupy extra space.
4. Enhanced the performance of Thick Provisioned LUNs when the volume is nearly full.
5. Enhanced file search performance when there are a large number of files with the same name.
6. Fixed an issue where restarting the system during an entire system backup could prevent volumes from mounting properly.
7. Fixed an issue where scheduled tasks of emptying recycle bins might fail to delete folders only containing the "desktop.ini" file.
8. Fixed an issue where triggering Adaptive MFA or entering incorrect account credentials might cause the auto block function to count login attempts abnormally.
9. Fixed an issue where users might not be able to set up OTP for login.
10. Fixed an issue where uploading IdP metadata might fail when setting up SAML SSO clients.
11. Fixed an issue where users might not return to DS cam or DS finder after using OIDC SSO login.
12. Fixed an issue where users might not receive emails with emergency codes when using 2FA for DSM login.
13. Fixed an issue where data synchronization might fail when creating backup or replication tasks to a remote target server via Snapshot Replication, Hyper Backup, or other packages.
14. Fixed an issue where login might fail when creating backup or replication tasks to a remote target server via Snapshot Replication, Hyper Backup, or other packages.
15. Fixed an issue where OpenVPN might fail to disable gateways.
16. Fixed an issue where using SAML SSO for DSM login might fail if the IdP's response was too long.
17. Fixed an issue where the system might become unresponsive when setting up OIDC SSO clients.
18. Fixed an issue where Resource Monitor might display abnormal connection times in Connections > Connected Users.
19. Fixed an issue where users might not be able to use a hardware security key for DSM login.
20. Fixed a security vulnerability regarding ghostscript (CVE-2024-29510).
21. Fixed security vulnerabilities regarding netatalk (CVE-2024-38439, CVE-2024-38440, CVE-2024-38441).
22. Fixed a security vulnerability regarding Terrapin Attack (CVE-2023-48795).
23. Fixed a security vulnerability regarding glibc (CVE-2023-4911).
24. Minor bug fixes.

Notes:

• This version is released in a staged rollout.

 

[fredbert]

New release notes for the previous 7.2.2 release

Version: 7.2.2-72803​

---

(2024-08-26)
This update is recalled on 2024/09/11 to provide clearer details about the DSM and package updates to avoid confusion. This issue is fixed in version 7.2.2-72806.

However! I took the release notes, as posted here by @SynoMan, and the new notes (both above and from Synology's site, because I didn't believe the results). Doing a text comparison resulted in the following changes:

1. 7.2.2-72806 as Fixed Issues item 24 added.
2. Errr... that's it, all the rest of the text is the same.

The clearer details may be during the update process itself, but I would expect the new release notes to reflect this too.

 

[Rusty]

because I didn't believe the results

Same reason why I copy the content into my blog posts as well .

There are no differences in the installation process:

The update went fine.

 

[equinox]

My DS220+ updated successfully from 7.2.2-72803.

 

[Jan Janowski]

Surprise! Updated without a -1 attached to the name! That is a feature in itself!
Done

 

[Telos]

Version: 7.2.2-72803 recalled/replaced with 7.2.2-72806?

The Synology comedy is back in swing with a new season ... and a required reboot

With great fanfare, Synology launches v7.2.2 ... but then ...

 

[Jan Janowski]

But an update-able Non-Dash version is a pleasant surprise! How many times have you done an early update, only to be stuck awaiting a dash update? This change is good, and deserves an atta-boy!

See! I give credit when credit is due!

 

[Rusty]

Well said! Looks like they do listen!

 

[Telos]

It gives me great confidence when Synology removes releases from the downloads archive ... 72803? ... never happened.

I've got to wonder what all changed that was not documented

 

[Jan Janowski]

For those who have seen the issue…
New version of Surveillance Station just dropped

 

[Hein]

Soooo they said the detection for movement has been delegated to camera now instead of the nas device.

I noticed the following in my test lab. I updated the lab to the latest available DSM 7.2.2-72806.
I had one camera there set on H265 and it was set to detection by SS. That changed to camera now that the new SS is installed. However no new recordings were made when someone walked in the room where the camera is situated.

I checked the camera and the option for detection was not activated. On SS i checked the camera detection settings. Still set to camera but also the option the keep the original camera settings was still ticked on. Once i manually deactivated that option and saved the cam settings in SS i noticed the detection setting was activated on the camera and recordings resumed based on detected movement.

Anybody else notice this behaviour. And to be clear i did try that with H264 and H264, did not change a thing on the detection settings in SS and the camera itself.

 

[Jan Janowski]

IF you never open up and edit existing cameras With SS Stored as mot det source…..
IT WILL REMAIN ACTIVE!! It will continue to work correctly!

So Don’t open it up!!

I’m just trying to continue to use What works best, in the face of absolute rediculous short-sided decision making!
That is as stupid as removing H265 Support was!

 

[Hein]

Hello Jan. Why are you SHOUTING in most comments you make? It is counterproductive.

Anybody else have a productive comment?

 

[Jan Janowski]

With latest DSM & SS, the 264 4K cameras with SS Set as motion detect still work, (With SS as motion detect) but I had changed them back from H265 to H264 just before the update killed H265.
Motion detect works to this day- Just do not edit or change SS CAMERA settings, or SS as motion detect selection will then go away

 

[Hein]

Contacted Synology support. Explained the situation and it is now being send to the development team.

So as far as i can tell if the new DSM/SS update automically switches all cameras with motion detection from SS to camera it does not switch off the retain camera settings. Which results in cameras being switched to camera for detection source but the actuall camera is not switched on by SS and thus no recordings are made when someone enters the room.

The option to retain original camera settings is not a problem if you already had motion detection switched on in the camera itself. It only poses a problem if you, like us, never bothered to use the camera itself as the detection source but instead relied on SS to do the heavy lifting.

I'll keep this thread updated once i know more from our friends at Synology Taiwan.

 

[Akount]

I just want to say, I love that Synology is making progress and continuing to invest in license-free upgrades that most people use, like hopefully soon upgrading their Docs features.

 

[Jan Janowski]

Glad they are doing updates for security issues. I’ve always been impressed by the amount of security updates Synology has done, and the documentation regarding the fix timeline they used. You know what version has what protections.
But, I wish they would have offered H265 as a onetime license to buy. and left SS as a Motion Detector Source alone!
My reasons for this:
As long as the camera does H265 smoothly and preserves fine picture details: (That will be camera firmware dependant: out of Synology’s control!)
Being forced to go back to H264 will greatly increase disk useage. The cost of a H265 license, depending on number of cameras you use, would probably be far less than the cost of the extra space you are now using in the downgrade to 7.2.2 & H264. The more cameras, the greater disk space issue this creates.
If you were close to full on drive space when this occurred it’s even more obvious, as now your staring at a greater expense as well to update drive(s) sizes.
I had used SS as a Motion detect source and had far better control over mot detect than any camera ever did. Leave it for those who like it, otherwise they can elect to use camera settings as motion detect!
The best of both worlds, to let the operator decide which to use! Not forcing us to use the weakest of the two!

 

[Telos]

Many recent "security updates" are attributable to the current OS. DSM 6.2.4 (which still receives security updates) has had minimal updates in the past two years. DSM 7, OTOH, remains a hot mess.

 

[Hein]

I do agree with Jan on this. It would have been better to let the actual operator of a camera system choose which device does the motion detection. I'll be sure to communicate this bit to them as well. Good point Jan.

 

[sergiosis]

Does the below mean that my DS218play will no longer offer 4K hardware transcoding which was the "great added value" of this device?

4. Starting from this version, the processing of media files using HEVC (H.265), AVC (H.264), and VC-1 codecs will be transitioned from the server to end devices to reduce unnecessary resource usage on the system and enhance system efficiency. These codecs are widespread on end devices such as smartphones, tablets, computers, and smart TVs. If the end device does not support the required codecs, the use of media files may be limited. Refer to this article for workarounds. In addition, please note the following exceptions: