DSM Version: 7.2-64561 Released (The official version)

[Peter Suh]

Version: 7.2-64561

(2023-05-22)

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. Starting from this version, logs for drives will no longer appear in Storage Manager > HDD and will be available only in Log Center.
4. Removed the "Automatically create port forwarding rules" option from QuickConnect advanced settings to increase network security.
5. Users can now create a Btrfs volume of up to 1 PB on specific Synology NAS models. This update automatically converts existing volumes that use the Btrfs (Peta Volume) file system to Btrfs. However, to create a volume larger than 200 TB, a RAID 6 storage pool and at least 64 GB of system memory are still required.Learn more
6. The maximum single volume size supported by RS2423+ / RS2423RP+ has been adjusted to 200 TB (with a minimum system memory requirement of 32 GB).
7. Starting from this version, Windows Server 2008 domains will no longer be supported. After installing this update, current Windows Server 2008 domains will be unavailable.
8. 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
What’s New
1. Added support for WriteOnce shared folders. This feature is based on the Write Once, Read Many (WORM) technology and can be enabled to prevent files from being modified, deleted, or renamed for a specified period.
2. Added support for volume encryption. All volume encryption keys are stored in the Encryption Key Vault, which can be set up on a local Synology NAS or via KMIP on a remote Synology NAS.
3. Added more Synology NAS models to support M.2 NVMe SSD storage pools. Learn more
4. Added more Synology NAS models to support the M2D18 adapter card: RS822RP+, RS822+, RS1221RP+, and RS1221+.
5. Added more SSD cache group management options, including changing the RAID type and replacing a drive.
6. Added support for inline zero-block removal to increase the efficiency of data deduplication.
7. Adjusted how drive information is presented in Storage Manager. Users can now quickly check the condition of their drives by looking at the "Drive Status" field.
8. Users can now view the amount of used and free space for each storage pool and volume in Storage Manager.
9. Added a warning notification for when the available shared folder quota is low.
10. Supports deleting individual desktop notifications.
11. Supports sending DSM notifications via additional webhook providers, including LINE and Microsoft Teams.
12. Supports creating custom notification rules for system events, giving users greater control over what notifications to receive.
13. Supports exporting a list of users and of groups.
14. Added support for SAML to integrate DSM with external SSO servers.
15. Added the option to allow non-admin users to safely eject USB devices.
16. Users can now manually input the IP addresses or FQDNs of one or more domain controllers in the trusted domain. This allows Synology NAS to sync domain data directly with the specified domain controllers.
17. Users can now enable Synology's email server to send DSM notifications directly to their Synology Account.

Fixed Issues
1. Fixed an issue where adding drives to a JBOD storage pool did not expand its capacity.
2. Updated Mbed-TLS to version 2.28.2 to fix multiple security vulnerabilities (CVE-2021-36647, CVE-2022-46392, CVE-2022-46393).
3. Updated Libksba to version 1.6.3 to fix a security vulnerability (CVE-2022-3515).
4. Updated SQLite to version 3.40.0 to fix a security vulnerability (CVE-2022-46908).
5. Updated Certifi to version 2022.12.07 to fix a security vulnerability (CVE-2022-23491).
6. Updated Node.js to version 14.21.1 to fix a security vulnerability (CVE-2022-43548).
7. Updated cURL to version 7.86.0 to fix multiple security vulnerabilities (CVE-2022-27774, CVE-2022-27775, CVE-2022-27776, CVE-2022-27781, CVE-2022-27782, CVE-2022-32205, CVE-2022-32206, CVE-2022-32207, CV E-2022-32221, CVE-2022-35252, CVE-2022-42915, CVE-2022-42916).
8. Updated PHP to version 8.1.9 to fix multiple security vulnerabilities (CVE-2019-11043, CVE-2021-21705, CVE-2022-31625).
9. Updated Sysstat to version 12.7.1 to fix a security vulnerability (CVE-2022-39377).
10. Updated OpenSSL to version 3.0.7 to fix multiple security vulnerabilities (CVE-2022-2068, CVE-2022-2097, CVE-2022-2274, CVE-2022-3358, CVE-2022-3602, CVE-2022-3786).
11. Updated Expat to version 2.5.0 to fix a security vulnerability (CVE-2022-43680).
12. Updated Libtirpc to version 2.87 to fix a security vulnerability (CVE-2021-46828).
13. Updated GnuPG to version 2.2.39 to fix a security vulnerability (CVE-2022-34903).
14. Updated OpenVPN to version 2.5.8 to fix a security vulnerability (CVE-2022-0547).
15. Updated libxml2 to version 2.9.14 to fix a security vulnerability (CVE-2022-23308).
16. Updated GMP to version 6.2.1 to fix a security vulnerability (CVE-2021-43618).
17. Updated ImageMagick to version 6.9.12-61 to fix multiple security vulnerabilities (CVE-2020-25664, CVE-2020-25665, CVE-2020-25666, CVE-2020-25667, CVE-2020-25674, CVE-2020-25675, CVE-2020-25676, CVE-2020-27560, CVE-2020-27750, CVE-2020-27751, CVE-2020-27752, CVE-2020-27753, CVE-2020-27754, CVE-2020-27755, CVE-2020-27756, CVE-2020-27757, CVE-2020-27758, CVE-2020-27759, CVE-2020-27760, CVE-2020-27761, CVE-2020-27762, CVE-2020-27763, CVE-2020-27764, CVE-2020-27765, CVE-2020-27766, CVE-2020-27767, CVE-2020-27768, CVE-2020-27769, CVE-2020-27770, CVE-2020-27771, CVE-2020-27772, CVE-2020-27773, CVE-2020-27774, CVE-2020-27775, CVE-2020-27776, CVE-2020-29599, CVE-2021-20176, CVE-2021-20224, CVE-2021-20241, CVE-2021-20245, CVE-2021-20246, CVE-2021-20309, CVE-2021-3574, CVE-2021-3596, CVE-2021-39212, CVE-2021-4219, CVE-2022-1114, CVE-2022-1115, CVE-2022-28463, CVE-2022-32545, CVE-2022-32546, CVE-2022-32547).
18. Updated FFmpeg to version 4.1.9 to fix multiple security vulnerabilities (CVE-2020-20892, CVE-2020-20902, CVE-2020-21688, CVE-2020-21697, CVE-2021-3566, CVE-2021-38114, CVE-2021-38291).
19. Fixed a security vulnerability regarding Netatalk (CVE-2022-45188).
20. Fixed multiple security vulnerabilities regarding Python3 (CVE-2020-10735, CVE-2021-28861, CVE-2022-45061).
21. Fixed multiple security vulnerabilities regarding iproute2 (CVE-2022-3527, CVE-2022-3529, CVE-2022-3530).
22. Fixed multiple security vulnerabilities regarding D-Bus (CVE-2022-42010, CVE-2022-42011, CVE-2022-42012).
23. Fixed a security vulnerability regarding syslog-ng (CVE-2022-38725).
24. Fixed a security vulnerability regarding inetutils (CVE-2022-39028).
25. Fixed a security vulnerability regarding DNSmasq (CVE-2022-0934).
26. Fixed a security vulnerability regarding BusyBox-udhcp (CVE-2019-5747).
27. Fixed multiple security vulnerabilities regarding Linux Kernel (CVE-2021-22600, CVE-2021-38209, CVE-2021-4037, CVE-2022-0168, CVE-2022-1016, CVE-2022-1729, CVE-2022-1786, CVE-2022-20141, CVE-2022-20368, CVE-2022-2078, CVE-2022-2639, CVE-2022-2905, CVE-2022-29581, CVE-2022-32250, CVE-2022-3524, CVE-2022-3566, CVE-2022-3567, CVE-2022-36879, CVE-2022-36946, CVE-2022-42703).
28. Fixed a security vulnerability regarding Nginx (CVE-2022-3638).
29. Fixed a security vulnerability regarding ghostscript (CVE-2023-28879).
30. Fixed a security vulnerability regarding curl (CVE-2023-23916).

Limitation
1. S.M.A.R.T. testing for M.2 NVMe SSDs is no longer supported.
2. Starting from DSM 7.2 Beta, Virtual Machine Manager will no longer support creating clusters with older DSM versions. Please update each host in the cluster to the same DSM version or above versions for the Virtual Machine Manager cluster to operate properly.
 

 

[PincoPalla]

6 hours ago, Peter Suh said:

8. 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

Hi Peter, I don't understand this passage, if you can explain it better thanks. For example, I installed a 918+ vers. 7.0.1 - 42218 what should I do???. Thank you

[Orphée]

This is official release note from Synology.

It just means on official Synology hardware, they won't be noticed a new release is available. They will have to manually put the new PAT file.

 

Nothing to be afraid for us.

[PincoPalla]

9 hours ago, Orphée said:

This is official release note from Synology.

It just means on official Synology hardware, they won't be noticed a new release is available. They will have to manually put the new PAT file.

 

Nothing to be afraid for us.

Ok thank you Orphee

[Orphée]

Upgraded my 7.1.1 u5 using arpl-i18n to 7.2 final.

It worked fine. Thanks @wjz304

 

Edit : On 2 Proxmox VMs.

Edited May 23 by Orphée

[Peter Suh]

Supports M Shell for TCRP , DSM 7.2-64561 official version.

 

 

 

[Al lex]

I have tried MShell. First I tried to update from 64551 to 64661 interactively. It was partly successfull. DSM loaded but it erased map info and lost rtl8125 driver as it was original sino with no community updates . Then I made a new buid and it worked like a charm

 

BTW I still have no idea how to move between tabs... in MShell

Edited May 23 by Al lex

[Peter Suh]

(Warning) There is a problem with the mpt3sas driver (module). (ARPL, TCRP are the same)

 

Users who use the SAS controller Dell Perc H200, H310, etc. that use the module should not upgrade until the stabilization module is released.

 

I think pocopico should fix it again.

 

Tested on DS3622xs+ (Broadwellnk).

 

https://github.com/pocopico/redpill-modules/blob/master/broadwellnk-4.4.302/mpt3sas.ko

 

https://github.com/PeterSuh-Q3/arpl-modules/blob/main/broadwellnk-4.4.302/mpt3sas.ko

[Peter Suh]

My DS3622xs+ for backup, which I tried migrating from DSM 7.1.1-42962 to 7.2-64561, uses 3TB x 6 RAID6.
This is the 2nd XHenology in my bottom profile.
I am using a Dell Perc H310 and the error message below occurred in the mpt3sas.ko module and there was a file corruption message during DSM installation.

However, the DELL T1700 under the same conditions installed as a test
The migration from DSM 7.1.1-42962 to 7.2-64561 has just been processed successfully.

It may be a situation unrelated to mp3sas.ko.
In the module itself below, "Exec format error" occurs, but the actual module seems to have nothing to do with the operation.

If you need to use the mp3sas module once, it would be better to proceed after a little more stabilization review.

 

[linuxrc.syno.log]

modprobe: ERROR: could not insert 'mpt3sas': Exec format error
Found SAS Controller : pciid 1000d00000070  Required Extension : Searching for matching extension for mpt3sas

[messages]

May 23 13:43:13  kernel: [   12.141722] mpt3sas version 41.00.00.00 loaded
May 23 13:43:13  kernel: [   12.146377] mpt3sas 0000:06:00.0: can't disable ASPM; OS doesn't have ASPM control
May 23 13:43:13  kernel: [   12.154262] mpt2sas_cm0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (32877396 kB)
May 23 13:43:13  kernel: [   12.234637] mpt2sas_cm0: IOC Number : 0
May 23 13:43:13  kernel: [   12.238500] mpt2sas_cm0: CurrentHostPageSize is 0: Setting default host page size to 4k
May 23 13:43:13  kernel: [   12.246677] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 29
May 23 13:43:13  kernel: [   12.251761] mpt2sas_cm0: iomem(0x00000000f71c0000), mapped(0xffffc90000270000), size(16384)
May 23 13:43:13  kernel: [   12.260162] mpt2sas_cm0: ioport(0x000000000000c000), size(256)
May 23 13:43:13  kernel: [   12.337632] mpt2sas_cm0: IOC Number : 0
May 23 13:43:13  kernel: [   12.341492] mpt2sas_cm0: CurrentHostPageSize is 0: Setting default host page size to 4k
May 23 13:43:13  kernel: [   12.385631] mpt2sas_cm0: scatter gather: sge_in_main_msg(1), sge_per_chain(9), sge_per_io(128), chains_per_io(15)
May 23 13:43:13  kernel: [   12.396089] mpt2sas_cm0: request pool(0xffff8807eed80000) - dma(0x7eed80000): depth(3492), frame_size(128), pool_size(436 kB)
May 23 13:43:13  kernel: [   12.435892] mpt2sas_cm0: sense pool(0xffff8807eee00000) - dma(0x7eee00000): depth(3367), element_size(96), pool_size (315 kB)
May 23 13:43:13  kernel: [   12.447339] mpt2sas_cm0: reply pool(0xffff8807eee80000) - dma(0x7eee80000): depth(3556)frame_size(128), pool_size(444 kB)
May 23 13:43:13  kernel: [   12.458389] mpt2sas_cm0: config page(0xffff88081a397000) - dma(0x81a397000): size(512)
May 23 13:43:13  kernel: [   12.466352] mpt2sas_cm0: Allocated physical memory: size(7579 kB)
May 23 13:43:13  kernel: [   12.472483] mpt2sas_cm0: Current Controller Queue Depth(3364), Max Controller Queue Depth(3432)
May 23 13:43:13  kernel: [   12.540195] mpt2sas_cm0: LSISAS2004: FWVersion(20.00.07.00), ChipRevision(0x03)
May 23 13:43:13  kernel: [   12.547549] mpt2sas_cm0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)
May 23 13:43:13  kernel: [   12.559581] mpt3sas 0000:06:00.0: Enabled Extended Tags as Controller Supports
May 23 13:43:13  kernel: [   12.566919] scsi host1: Fusion MPT SAS Host
May 23 13:43:13  kernel: [   12.571697] mpt2sas_cm0: sending port enable !!
May 23 13:43:13  kernel: [   12.577081] mpt2sas_cm0: hba_port entry: ffff8807f27efb40, port: 255 is added to hba_port list
May 23 13:43:13  kernel: [   12.588638] mpt2sas_cm0: host_add: handle(0x0001), sas_addr(0x500062b0002a5e9c), phys(8)
May 23 13:43:13  kernel: [   12.597822] mpt2sas_cm0: handle(0x9) sas_address(0x4433221102000000) port_type(0x1)
May 23 13:43:13  kernel: [   12.605835] mpt2sas_cm0: handle(0xa) sas_address(0x4433221103000000) port_type(0x1)
May 23 13:43:13  kernel: [   12.619625] mpt2sas_cm0: port enable: SUCCESS
May 23 13:43:13  kernel: [   12.627484] scsi 1:0:0:0: Direct-Access     TOSHIBA  DT01ABA100V              A8A0 PQ: 0 ANSI: 6
May 23 13:43:13  kernel: [   12.636874] scsi 1:0:0:0: SATA: handle(0x000a), sas_addr(0x4433221103000000), phy(3), device_name(0x5000039fdef391ca)
May 23 13:43:13  kernel: [   12.647545] scsi 1:0:0:0: enclosure logical id(0x500062b0002a5e9c), slot(0) 
May 23 13:43:13  kernel: [   12.654760] scsi 1:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
May 23 13:43:13  kernel: [   12.663779] scsi 1:0:0:0: serial_number(           306NEU7MS)
May 23 13:43:13  kernel: [   12.669566] scsi 1:0:0:0: qdepth(32), tagged(1), scsi_level(7), cmd_que(1)
May 23 13:43:13  kernel: [   12.678428]  end_device-1:0: mpt3sas_transport_port_add: added: handle(0x000a), sas_addr(0x4433221103000000)
May 23 13:43:13  kernel: [   12.678974] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
May 23 13:43:13  kernel: [   12.678979] sd 1:0:0:0: [sdb] 4096-byte physical blocks
May 23 13:43:13  kernel: [   12.705595] scsi 1:0:1:0: Direct-Access     WDC      WD6400AAKS-00A7B0        3B01 PQ: 0 ANSI: 6
May 23 13:43:13  kernel: [   12.715176] scsi 1:0:1:0: SATA: handle(0x0009), sas_addr(0x4433221102000000), phy(2), device_name(0x50014ee1013c8ee4)
May 23 13:43:13  kernel: [   12.725849] scsi 1:0:1:0: enclosure logical id(0x500062b0002a5e9c), slot(1) 
May 23 13:43:13  kernel: [   12.733065] scsi 1:0:1:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
May 23 13:43:13  kernel: [   12.742270] scsi 1:0:1:0: serial_number(     WD-WCASY2130464)
May 23 13:43:13  kernel: [   12.748056] scsi 1:0:1:0: qdepth(32), tagged(1), scsi_level(7), cmd_que(1)
May 23 13:43:13  kernel: [   12.758325]  end_device-1:1: mpt3sas_transport_port_add: added: handle(0x0009), sas_addr(0x4433221102000000)
May 23 13:43:13  kernel: [   12.759061] sd 1:0:1:0: [sdc] 1250261615 512-byte logical blocks: (640 GB/596 GiB)
May 23 13:43:13  kernel: [   12.767536] sd 1:0:1:0: [sdc] Write Protect is off
May 23 13:43:13  kernel: [   12.767542] sd 1:0:1:0: [sdc] Mode Sense: 7f 00 10 08
May 23 13:43:13  kernel: [   12.769990] sd 1:0:1:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
May 23 13:43:13  kernel: [   12.800300]  sdc: sdc1 sdc2 sdc3
May 23 13:43:13  kernel: [   12.816535] sd 1:0:1:0: [sdc] Attached SCSI disk
May 23 13:43:13  kernel: [   12.928873] sd 1:0:0:0: [sdb] Write Protect is off
May 23 13:43:13  kernel: [   12.933710] sd 1:0:0:0: [sdb] Mode Sense: 7f 00 10 08
May 23 13:43:13  kernel: [   12.939893] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
May 23 13:43:13  kernel: [   13.207650]  sdb: sdb1 sdb2 sdb3
May 23 13:43:13  kernel: [   13.478296] sd 1:0:0:0: [sdb] Attached SCSI disk

 

[freddie]

Hello Everyone.

I Just installed DSM 7.2.0-64561 Latest Version with TCRP latest too, on Baremetal, everything fine but with find.synology.com, he found the NAS and when I connect it it has ( lost configuration ), I reinstall DSM with this file : DSM_DS3622xs+_64561.pat, after 56% an error occur tell me the file are corrupted or damaged.

 

if anyone have a solution thanks.

 

I Try to Postupdate and tell you if it worked.

[freddie]

il y a 43 minutes, freddie a dit :

Hello Everyone.

I Just installed DSM 7.2.0-64561 Latest Version with TCRP latest too, on Baremetal, everything fine but with find.synology.com, he found the NAS and when I connect it it has ( lost configuration ), I reinstall DSM with this file : DSM_DS3622xs+_64561.pat, after 56% an error occur tell me the file are corrupted or damaged.

 

if anyone have a solution thanks.

 

I Try to Postupdate and tell you if it worked.

So After an Postupdate, the Wizard installation, became a migration, but installation failed again at 56%, I tried with file in .pat and with directly on synology site nothing !! so i get stuck lool

[pocopico]

1 hour ago, freddie said:

So After an Postupdate, the Wizard installation, became a migration, but installation failed again at 56%, I tried with file in .pat and with directly on synology site nothing !! so i get stuck lool

 

Syno has made the posibility to loose data very rare. You can keep your serial/mac/sataportmap/diskidxmap and you can download latest image to rebuild a new loader using a new USB stick and see how that goes. You can try the HTML builder which is easier.

[freddie]

Il y a 4 heures, pocopico a dit :

 

Syno has made the posibility to loose data very rare. You can keep your serial/mac/sataportmap/diskidxmap and you can download latest image to rebuild a new loader using a new USB stick and see how that goes. You can try the HTML builder which is easier.

Hello, Pocopico, I Reinstall on the USB Stick to non-production NAS, to be sure no data, get lost and I finally successfully installed 7.2.0 on NAS . Thanks to you for the Loader to maintain it updated.