Guest Posted February 23, 2021 Share #1 Posted February 23, 2021 https://www.synology.com/en-global/releaseNote/DSM?model=DS3615xs Révélation (2021-02-23) 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. 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. Quote Link to comment Share on other sites More sharing options...
flyride Posted February 23, 2021 Share #2 Posted February 23, 2021 (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 - DS3615xs - Using custom extra.lzma: NO - Installation type: ESXi VM - Notes: appears to complete the install, reboots and hangs at 100% CPU utilization immediately after the bootloader initializes 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: appears to complete the install, reboots and hangs at 100% CPU utilization immediately after the bootloader initializes Outcome of the update: FAILED - DSM version prior update: DSM 6.2.3-25426 Update 3 - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: ESXi VM - Notes: appears to complete the install, reboots and hangs at 100% CPU utilization immediately after the bootloader initializes Edited February 23, 2021 by flyride 1 7 Quote Link to comment Share on other sites More sharing options...
gadreel Posted February 24, 2021 Share #3 Posted February 24, 2021 (edited) Outcome of the installation/update: FAILED - DSM version prior update: DSM 6.2.3-25426 Update 3 - 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: Same as @flyride "appears to complete the install, reboots and hangs at 100% CPU utilization immediately after the bootloader initializes" Edited February 24, 2021 by gadreel 1 Quote Link to comment Share on other sites More sharing options...
Polanskiman Posted February 28, 2021 Share #4 Posted February 28, 2021 So I leave 3 days on holidays and everyone forgets the rules... They are rather simple and stated just above the first post. All Off-Topic posts have been moved. 5 1 4 Quote Link to comment Share on other sites More sharing options...
ozef Posted February 28, 2021 Share #5 Posted February 28, 2021 (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: HP MicroServ GEN8 - Notes: Upgrade successfully but nothing works after Edited February 28, 2021 by ozef 1 Quote Link to comment Share on other sites More sharing options...
altas Posted March 2, 2021 Share #6 Posted March 2, 2021 Outcome of the update: FAILED - DSM version prior update: New Installation - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: No - Installation type: Dell Latitude 7470 - Notes: After DSM Installation the Network card was active but no IP get assigned anymore, fresh install with DSM 6.2.3 is working 2 Quote Link to comment Share on other sites More sharing options...
xpe-usr Posted March 5, 2021 Share #7 Posted March 5, 2021 (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: Installation seems fine, but than stuck at bootloader. FixSynoboot.sh (latest from feb 2021) was used. Logging in COM-port (serial) shows the following right after the grub2 bootloader menu selection: Quote va not found Failed to process header This looks to be the same as some users reported with DSM7 preview. Seems Synolgy has changed a lot in their boot-process/images/kernel in 6.2.4. Edited March 5, 2021 by xpe-usr 2 1 Quote Link to comment Share on other sites More sharing options...
mitzone Posted March 29, 2021 Share #8 Posted March 29, 2021 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. 1 Quote Link to comment Share on other sites More sharing options...
specter9mm Posted March 30, 2021 Share #9 Posted March 30, 2021 Outcome of the installation/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: YES - Installation type: ASRock Z390M-ITX/ac - VENGEANCE® LPX 16GB (2 x 8GB) DDR4 DRAM 3000MHz C15 Memory Kit - Intel 9900K - Additional comments: Update applied to running system. - Notes: System hangs initializing, appears to be during driver/kernel module load. 2 Quote Link to comment Share on other sites More sharing options...
peppi01 Posted April 8, 2021 Share #10 Posted April 8, 2021 - Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.3_25432 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: QNAP-TS-269_PRO - NIC: Intel Atom(TM) CPU D2701 @ 2,13GHz (2 Kerne, 4 Threads) - Additional comments: DON'T RESTART HANGED NO POSSIBILITIES TO FIX IT 4 Quote Link to comment Share on other sites More sharing options...
Alanx Posted April 9, 2021 Share #11 Posted April 9, 2021 - Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.3_25426 - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: NO - Installation type: ESXi 7 U2 on HPE MicroServer G10 X3421 - Additional comments: Downloaded and applied the update through DSM control panel, took a while till it's back up running but lost network connection - no response to ping, while through ESX console, could see the VM booted successfully - with high CPU uti and no network so not working at all; had to restore from the snapshot taken b4 the update. 3 Quote Link to comment Share on other sites More sharing options...
julien451 Posted April 10, 2021 Share #12 Posted April 10, 2021 - 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 4 Quote Link to comment Share on other sites More sharing options...
plaka Posted April 10, 2021 Share #13 Posted April 10, 2021 - 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: KVM - Additional comments: Fresh Install of DSM 6.2.4-25556 failed with va not found Failed to process header 4 Quote Link to comment Share on other sites More sharing options...
sony21 Posted April 13, 2021 Share #14 Posted April 13, 2021 - Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.3_25432 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: HP ProLiant MicroServer G7 - N54L - Additional comments: Update seems ok, but it doesn't boot after restart. Recovery doesn't work. 5 Quote Link to comment Share on other sites More sharing options...
digitall12 Posted April 14, 2021 Share #15 Posted April 14, 2021 Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: ESXi VM - Notes: appears to complete the install, no reboot 5 Quote Link to comment Share on other sites More sharing options...
thedaggert Posted April 14, 2021 Share #16 Posted April 14, 2021 - Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.2_24922 Update 6 - Loader version and model: JUN'S LOADER 1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: HP ProLiant MicroServer Gen10 Plus - Additional comments: Fresh Install - Update seems ok, but it doesn't boot after restart - Synology Assistant can't find the server. 3 Quote Link to comment Share on other sites More sharing options...
DanielXP Posted April 15, 2021 Share #17 Posted April 15, 2021 Outcome of the installation/update: UNSUCCESSFUL - 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: YNO - Installation type: Custom Hardware - Additional comments: Help 5 Quote Link to comment Share on other sites More sharing options...
gquiring Posted April 15, 2021 Share #18 Posted April 15, 2021 (edited) Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.3.25426 Update 2 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: No - Installation type: TheCUS N5550 - Notes: Would not complete install, system still worked Edited April 15, 2021 by gquiring 6 Quote Link to comment Share on other sites More sharing options...
yogy Posted April 17, 2021 Share #19 Posted April 17, 2021 Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 Update 3 - Loader version and model: JUN'S LOADER 1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: unRAID KVM - Additional comments: INSTALLED AND REBOOTED, AFTER 30 MIN. NOTHING. CANNOT FIND VM ANYWHERE. 8 Quote Link to comment Share on other sites More sharing options...
viorelbuhoi Posted May 13, 2021 Share #20 Posted May 13, 2021 - Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.3_25426 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: YES - Installation type: ML-350 G6, CPU-X5690, 36Gb-RAM, 2xLSI9211-IT with 12x2Tb in RAID6, 2x512Gb CACHE-SSD, DELL X520-2T 10Gbe - Additional comments: Downloaded and applied the update through DSM control panel. after reboot no network connection, no activity. 5 Quote Link to comment Share on other sites More sharing options...
Guest Posted May 30, 2021 Share #21 Posted May 30, 2021 - Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 Update 3 (clean install) - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: Yes (virtio) - Installation type: KVM (Proxmox) - Additional comments: reboots and stalls before booting Linux with the following on serial: va not found Failed to process header Quote Link to comment Share on other sites More sharing options...
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.