noki

DSM 5.2-5565 Update 2

Recommended Posts

(2015/06/09)
Important Information
A thorough investigation has been done, and it is confirmed that DSM and its related packages are not impacted by the LogJam vulnerability because of the way Synology implements OpenSSL in our system.
Fixed Issues
Improved the stability of SHR expansion.
Improved the stability of SMB transfer when the system is being accessed by an excessive number of clients.
Fixed multiple kernel vulnerabilities (CVE-2014-3122, CVE-2014-3153, CVE-2014-0196, and CVE-2014-4699).
Fixed an issue where CPU usage could remain high when widget is enabled.
Fixed an issue where LDAP users could fail to log in to DSM.
Fixed an issue where files could not be downloaded via Windows' terminal.
Fixed an issue where system cannot enter hibernation.
Fixed an issue where some folders with non-English names would become inaccessible via SMB.
Fixed an issue where volumes/iSCSI LUN cannot be displayed after the Synology High Availability system resumes from safe mode with UPS connected.

 

Is possible update without problem on XPEnoboot 5.2-5565.2 ???

Share this post


Link to post
Share on other sites

Quick reply: Just tested in VMware Workstation with no volumes, iSCSI or packages installed and it looks like it works but no guarantees from me that it will work in all situations :smile:

Share this post


Link to post
Share on other sites

Just installed it on my nas with 1 volume and the phpvirtualbox package. The update "hangs" after install, so i just turned the power off and rebooted the nas. After the reboot i could start the vm running on the nas just fine.

Share this post


Link to post
Share on other sites

update run, I too have been stuck at 47%. Off brutally restart everything seems to work well!

 

Xpenology run in Dell Optiplex USSF 760

Share this post


Link to post
Share on other sites

Works fine on HP Microserver Gen 8 bare metal.

 

I have also to restart "hard" after the timer finished.

Share this post


Link to post
Share on other sites

After updating my HP Microserver Gen 8 (baremetal) there are problems with SSL. No https-service runs correct. It must have to do with the certififcates...

I will investigate this later.

 

EDIT:

So first workaround is to disable SSL:

- make a SSH connection and logon as root

- edit /etc/synoinfo.conf with your favorite editor (vi or nano I asume)

- search "runHTTPS" and "runWebHTTPS" and change both entries to "no"

- save file and reboot

 

After the reboot SSL is deactivated but you can login.

 

Now to step 2 and howto make SSL work again....

 

EDIT2:

I make SSL working again :grin:

Something in the update-process has destroyed the contents of files under /etc/httpd/conf/extra so e.g. the file "httpd-ssl.conf-cipher" was totally filled with garbage.

 

I copied the files from /etc.defaults/httpd/conf/extra (which has correct files) to /etc/httpd/conf/extra. To make it complete I copied /etc.defaults/httpd/conf to /etc/httpd/conf.

 

The last step is to remake the internal SSL-certificates:

cd /usr/syno/etc/ssl/
./mkcert.sh

 

wait till the new internal certificates are created and then

reboot

 

Voila, after the reboot all SSL-Sites are up and running again! :mrgreen:

Share this post


Link to post
Share on other sites

My second DSM installation under Hyper-V runs without any issues but there I have not enabled any ssl-services (not under web-services and not under DSM itself).

 

So be careful at upgrading if you have enabled SSL!

Share this post


Link to post
Share on other sites

I updated my machine with update 2 and works fine. I will describe as below.

 

My environment setup:

mobo: Asus J1900I-C

RAM: 4G SO-DIMM

HD: Seagate 1T ST1000DM003

DSM installed ver: 5.2-5565 update 1

XPEnology ver: 5.2-5565.2 (07/06/2015)

 

upgrade to 5.2-5565 update 2 method

login in to web GUI, auto download the update file and upgrade form there.

 

my issue

I after applied 5.2 update 2, first reboot the system after the update, the console hanged at:

================== Start udevd ========================
===== trigger device plug event =======

 

how to fix the issue

I pressed the reset button and then it booted ok.

 

Hope this will help to some people.

 

The direct link for downloading the 3615xs update 2 is as below:

http://usdl.synology.com/download/criti ... 3615xs.pat

 

Version : 5.2-5565 Update 2

(2015/06/09)
Important Information

   A thorough investigation has been done, and it is confirmed that DSM and its related packages are not impacted by the LogJam vulnerability because of the way Synology implements OpenSSL in our system. 

Fixed Issues

   Improved the stability of SHR expansion.
   Improved the stability of SMB transfer when the system is being accessed by an excessive number of clients.
   Fixed multiple kernel vulnerabilities (CVE-2014-3122, CVE-2014-3153, CVE-2014-0196, and CVE-2014-4699).
   Fixed an issue where CPU usage could remain high when widget is enabled.
   Fixed an issue where LDAP users could fail to log in to DSM.
   Fixed an issue where files could not be downloaded via Windows' terminal.
   Fixed an issue where system cannot enter hibernation.
   Fixed an issue where some folders with non-English names would become inaccessible via SMB.
   Fixed an issue where volumes/iSCSI LUN cannot be displayed after the Synology High Availability system resumes from safe mode with UPS connected. 

Share this post


Link to post
Share on other sites

I'm running 5.2-5565 directly on a N54L (without esxi). Do I just run the regular DSM update method? No need to change boot image/run any commands?

Share this post


Link to post
Share on other sites

If you already have the actual boot-image (XPEnoboot 5.2-5565.2 (07/06/2015)) then you can do the update directly within the DSM like on real Synology.

 

The first boot after the update might hang and you have to make a hard reset. If you want to make it safe, make a copy of /etc (e.g. with winscp) to your pc so you are able to recover important files if an error occours like at my installation (read a few posts up).

Share this post


Link to post
Share on other sites

Just log over, do the dsm update and on the console of esxi it show Xpeno just hang after the reboot. I wait 15min and just do a hard reset and after i got the login promp again.

fully working and my setting were all preserved.

Very great released of the team.

Share this post


Link to post
Share on other sites

Successful update to update 2 on N54L here. I disabled https in DSM just to be safe then re-enabled it after the upgrade. I did have the first boot get stuck and had to hard power down and power up. Second boot, everything was fine.

 

Thanks!

Share this post


Link to post
Share on other sites

No issues with HTTPS here, but I am using a cert that was generated by my CA rather than by the box itself.

 

I did however have to give the box a power-cycle.

 

Bare-Metal build on dual-core intel Atom D510, BCM IXBDN R10 ITX motherboard, in a Lacie EthernetDisk chassis.

Share this post


Link to post
Share on other sites

I just did the same as kuma16830: was already running on Update 1, installed Update 2 through the web interface, rebooted, server locked up part way through boot, reset, booted successfully. All good now.

Share this post


Link to post
Share on other sites