EVOTk 79 Posted March 8 Share Posted March 8 (edited) https://www.synology.com/en-global/releaseNote/DSM?model=DS3615xs Révélation Version: 6.2.4-25556 (2021-03-08) Important Note Your Synology NAS may not notify you of this DSM update because of the following reasons. If you want to update your DSM to this version now, please click here to manually update it. The update is not available in your region yet. The update is expected to be available for all regions within the next few days, although the time of release in each region may vary slightly. This update will restart your Synology NAS. Integrates the beep control options for degraded/crashed volumes and abnormal SSD caches. The new LED indicator behavior makes the system status easier to distinguish on 15-series and newer models. (Learn more) DNS Server must be updated to version 2.2.3-5028 or above to be compatible with this update. LDAP Server must be updated to version 2.4.49-2515 or above to be compatible with this update. This update includes fixes to the below issues mentioned in 6.2.4-25554. Fixed an issue where external hard drives couldn't wake from hibernation on certain platforms (Grantley, Broadwell, Broadwellnk, Broadwellntbap, Purley). Fixed an issue where users could not sign in to Synology mobile apps after they had cleared the remembered device list in DSM 6.2.4. Compatibility & Installation Enhanced the password policy. Passwords must exclude usernames and descriptions, include both upper-case and lower-case letters as well as numerical digits. The minimum password length is 8 characters. Fixed a compatibility issue between the Geminilake platform and virtual machines running Windows 10. On a newly installed version of DSM, file rename and deletion log events for SMB will be enabled by default. What's New Users can now set 10 email addresses to receive system notifications. Enhanced domain database synchronization performance by syncing only altered data. Supports bad block detection on Synology SSDs. Supports the updating of Synology HDD and SSD firmware directly via DSM. Improved fan speed control based on the Synology network interface card temperature for 19-series and newer models. Fixed Issues Fixed an issue where the "Enable Web Assistant" option didn't work on NVR216 and NVR1218. Fixed an issue where the date and time formats for scheduled tasks were inconsistent in the widget and system settings. Fixed an issue where scheduled tasks may fail to be executed or modified. Fixed an issue where tasks scheduled at a high frequency generated a lot of logs and occupied system partitions. Fixed an issue where the custom welcome text may differ on the preview and actual login page due to character limits. Fixed an issue where data could still be written to LUNs after the volume runs out of space. Fixed an issue where if Wi-Fi dongles are installed, some available network interfaces weren't listed when users edit iSCSI targets. Fixed an issue where iSCSI services may be unstable when the host is too busy or when users disable iSCSI targets and ending sessions simultaneously. Fixed an issue where initiators couldn't connect to the iSCSI target after ethernet interfaces reconnect in a high-availability cluster. Fixed an issue where packages may not operate properly when drives migrated from another Synology NAS cause volume ID conflicts. Fixed an issue where users may not be able to find their Synology NAS in My Network Places on Windows when WS-Discovery isn't operating properly. Fixed an issue where Log Center didn't record recycle bin enabling/disabling events. Fixed a security vulnerability regarding Sudo. (Synology-SA-21:02) Fixed multiple security vulnerabilities. (Synology-SA-21:03) Limitations In response to the enhancement of domain database synchronization efficiency, the domain user/group list will be updated once an hour when it is created with Synology Directory Server. Edited March 8 by EVOTk Quote Link to post Share on other sites
gadreel 17 Posted March 8 Share Posted March 8 Outcome of the installation/update: FAILED - DSM version prior update: DSM 6.2.X - Loader version and model: Jun's Loader v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: UNRAID - TUF GAMING B550M-PLUS - RAM 64Gb DDR4 NON-ECC - AMD Ryzen 9 3900X - Additional comments: The update was applied on a fresh VM. - Notes: I guess no differences from the previous version... 2 Quote Link to post Share on other sites
cleandata 0 Posted March 28 Share Posted March 28 Outcome of the installation/update: FAILED - DSM version prior update: DSM 6.2.2_24922 - Loader version and model: Jun's Loader v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: PVE - J1900 - Additional comments: The update was applied on a fresh 24922 and applied Fixsynoboot.sh before trying upgrade to 25556 - Notes: Upgrade step failed after progress 100%, waiting 10 min after reboot, the VM shown booted up in PVE, but cannot be found by LAN IP or find.synology.com anymore 2 Quote Link to post Share on other sites
fahantech-007 0 Posted March 28 Share Posted March 28 - Outcome of the update: FAILED - DSM version prior update: DSM 6.2.3-25426 Update 3 - Loader version and model: JUN'S LOADER V1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - MB: Asrock C236 WSI | CPU: Intel Xeon E3-1235L V5 Quad-core - Additional comment: Upgrade step failed after progress 100% could not boot. 2 Quote Link to post Share on other sites
mitzone 8 Posted March 29 Share Posted March 29 (edited) Outcome of the update: FAILED - DSM version prior update: DSM 6.2.3-25426 Update 3 - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: NO - Installation type: ESXi VM - Notes: va not found; Failed to process header message in console, as reported earlier. Edited March 29 by mitzone 1 Quote Link to post Share on other sites
mitzone 8 Posted March 29 Share Posted March 29 (edited) Outcome of the update: FAILED - DSM version prior update: FRESH INSTALL - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: ESXi VM - Notes: va not found; Failed to process header message in console, as reported earlier. Edited March 29 by mitzone 3 Quote Link to post Share on other sites
LeoDaso 0 Posted March 31 Share Posted March 31 Outcome of the update: FAILED - DSM version prior update: DSM 6.2.3-25426 Update 3 - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - MB: Supermicro C7Z170-SQ, i5-6500 - Notes: Loader boots normally, no hard drive activity. 4 Quote Link to post Share on other sites
postgardh 0 Posted Wednesday at 07:15 PM Share Posted Wednesday at 07:15 PM (edited) Outcome of the update: FAILED - DSM version prior update: 6.2.4-25556 - Loader version and model: Jun’s Loader v1.03b DS3617xs - Using custom extra.lzma: NO - Installation type: ESXi VM - Notes: Not possible to ping after upgrade, try to restart 2 times.. Edited Wednesday at 08:07 PM by postgardh 1 Quote Link to post Share on other sites
skalliphone 0 Posted Thursday at 05:07 PM Share Posted Thursday at 05:07 PM Hi everyone I'm in the same configuration that you, after updating the system doesnt reboot properly, anyone have the process to rollback whitout loose my data on the raid shr ? Thanks for your help Quote Link to post Share on other sites
IG-88 755 Posted Thursday at 05:51 PM Share Posted Thursday at 05:51 PM 42 minutes ago, skalliphone said: I'm in the same configuration that you, after updating the system doesnt reboot properly, anyone have the process to rollback whitout loose my data on the raid shr ? keep a eye on the tutorial section, i created a new thread "how to undo a unfinished update 6.2.3 to 6.2.4 (no boot after 1st step of update" that will be visible after approval of a mod 2 Quote Link to post Share on other sites
skalliphone 0 Posted Thursday at 09:30 PM Share Posted Thursday at 09:30 PM Thank you very much, but your solution is too complex for me(I m so bad on Linux) , but I've try the second solution propose you, with a new installation of xpenology on a new hdd and reconnect my old raid disk after. and it work now. Thank a lot for your quick answer !!! Quote Link to post Share on other sites
calimansi 1 Posted Friday at 04:45 PM Share Posted Friday at 04:45 PM 22 hours ago, IG-88 said: keep a eye on the tutorial section, i created a new thread "how to undo a unfinished update 6.2.3 to 6.2.4 (no boot after 1st step of update" that will be visible after approval of a mod Does that mean that this update works now? I'm still seeing failed updates. Quote Link to post Share on other sites
IG-88 755 Posted Friday at 07:19 PM Share Posted Friday at 07:19 PM 2 hours ago, calimansi said: Does that mean that this update works now? I'm still seeing failed updates. no, the topic is "how to undo a unfinished update 6.2.3 to 6.2.4..." i thought that would sell it enough its meant to be a help for the unfortunate unknowingly having done the update to 6.2.4 Quote Link to post Share on other sites
amikot 8 Posted yesterday at 12:30 AM Share Posted yesterday at 12:30 AM 5 hours ago, IG-88 said: no, the topic is "how to undo a unfinished update 6.2.3 to 6.2.4..." i thought that would sell it enough its meant to be a help for the unfortunate unknowingly having done the update to 6.2.4 Actually the topic of the thread is: DSM 6.2.4-25556 No word about undoing unfinished update, so entering here people assume it's about installation reports. Quote Link to post Share on other sites
IG-88 755 Posted 23 hours ago Share Posted 23 hours ago 50 minutes ago, amikot said: Actually the topic of the thread is: DSM 6.2.4-25556 5 above On 4/8/2021 at 7:51 PM, IG-88 said: keep a eye on the tutorial section, i created a new thread "how to undo a unfinished update 6.2.3 to 6.2.4 (no boot after 1st step of update" that will be visible after approval of a mod https://xpenology.com/forum/topic/42765-how-to-undo-a-unfinished-update-623-to-624-no-boot-after-1st-step-of-update/ Quote Link to post Share on other sites
amikot 8 Posted 22 hours ago Share Posted 22 hours ago (edited) I think we didn't understood each other Never mind Edited 22 hours ago by amikot Quote Link to post Share on other sites
julien451 0 Posted 10 hours ago Share Posted 10 hours ago - Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.4-25556 - Loader version and model JUN'S LOADER 1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: Proxmox VM - Additional comments: Fresh Install of DSM 6.2.4-25556 failed with va not found Failed to process header Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.