Ermite

DSM 6.2.3-25426 Update 2

Polanskiman

Please read the READ ME topic before posting:

 

Message added by Polanskiman

Recommended Posts

Posted (edited)

- Outcome of the update:  SUCCESSFUL

- DSM version prior update: DSM 6.2.3-25426

- Loader version and model: Jun's Loader v1.04b DS3615xs

- Using custom extra.lzma: No

- Installation type: ESXi (with FixSynoboot.sh installed)

Edited by Bob1975
after FixSynoboot.sh installation the update was succesful

Share this post


Link to post
Share on other sites

- Outcome of the update:  SUCCESSFUL

- 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: 2 x BAREMETAL - Dell Optiplex 790

- Additional comments: Reboot required


- Outco me of the update:  SUCCESSFUL

- D SM version prior update: DSM 6.2.3-25426

- Lo ader version and model: JUN'S LOADER v1.03b - DS3615xs

- Using custom extra.lzma: NO

- Installation type: BARAMETAL - HP Microserver Gen8

- Additional comment : reboot required | Intel NIC | WOL works | PhpVirtualBox works


- Outcome of the update:  SUCCESSFUL

- 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: BAREMETAL - HP Microserver  Gen7 N54L  - HP Microserver Gen7 N40L

- Additional comments:  reboot required | Intel NIC | WOL works | PhpVirtualBox works

  • Like 1

Share this post


Link to post
Share on other sites

- Outcome of the update:  SUCCESSFUL

- DSM version prior update: DSM 6.2.2-24922 Update 1

- Loader version and model: JUN'S LOADER v1.03b - DS3617XS

- Using custom extra.lzma: YES

- Installation type: BAREMETAL

- Additional comments: 2 reboots required, first 6.2.2=>6.2.3 where loader stuck because of custom extra.lzma, then I copied new extra.lzma from IG-88 (version 0.11.2), and it booted to 6.2.3, then it auto updated to 6.2.3-25426 Update 2 and rebooted.

Share this post


Link to post
Share on other sites
Posted (edited)

Auto installation

  • Outcome of the update: FAILED
  • DSM version prior to update: DSM 6.2.3-25426 Update 1
  • Loader version and model: Jun v1.04b - DS918+
  • Using custom extra.lzma: NO
  • Installation type: MSI B250M PRO-VDH / i3-7100 / 32 DDR4 2333
  • Additional comments: Node restarted but still "Fail to update the file. The file is probably corrupt."

 

Manual installation

  • Outcome of the update: FAILED
  • DSM version prior to update: DSM 6.2.3-25426 Update 1
  • DSM downloaded from: https://archive.synology.com/download/DSM/criticalupdate/update_pack/25426-2/
  • Loader version and model: Jun v1.04b - DS918+
  • Using custom extra.lzma: NO
  • Installation type: MSI B250M PRO-VDH / i3-7100 / 32 DDR4 2333
  • Additional comments: "Node restarted but still "Fail to update the file. The file is probably corrupt."

    image.png.d93f921b83567b47617abbb3115d5086.png

 

 

Edited by Fulatins

Share this post


Link to post
Share on other sites

- Outcome of the update:  SUCCESFULL
- 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: BAREMETAL - Supermicro X10SLL-F, 32GB ECC RAM, Xeon E3-1270v3, 10GBit NIC Mellanox ConnectX-3, LSI SAS2008 IT-Mode
- Additional comment: Reboot required, custom synoinfo

Share this post


Link to post
Share on other sites
Posted (edited)

- Outcome of the installation/update: SUCCESSFUL

- DSM version prior update: DSM 6.2.3-25426 Update 1

- Loader version and model: JUN'S LOADER v1.04b - DS918+

- Using custom extra.lzma: YES

- Installation type:  BAREMETAL - ASUS ROG STRIX Z390 I GAMING, Intel - Core i3-8100 3.6 GHz Quad-Core Processor

- Additional comments: Reboot required
 

Edited by Wreid23
missing text

Share this post


Link to post
Share on other sites
Posted (edited)

- Outcome of the installation/update: SUCCESSFUL

- 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 7.0

- Additional comments: Reboot required

Edited by jeromim

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: SUCCESSFUL

- DSM version prior update: DSM 6.2.3-25426

- Loader version and model: JUN'S LOADER v1.04b - DS918+

- Using custom extra.lzma: NO

- Installation type: Proxmox 6.2.6 VM

- Additional comments: Used the FixSynoboot.sh to update

Share this post


Link to post
Share on other sites

Attempt 2:

 

- Outcome of the update:  FAILED

- 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: BAREMETAL - HP ProLiant MicroServer GEN8

- Additional comment: Auto Downloaded Via Synology GUI - Failed Again

- Additional comment: Changed VID & PID Still No Luck

Share this post


Link to post
Share on other sites

- Outco me of the update:  SUCCESSFUL

- 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: BARAMETAL - HP Microserver Gen8

- Additional: no ESx, with FixSynoboot.sh installed

Share this post


Link to post
Share on other sites

Attempt 3:

 

Finally All 3 Updated :) 

 

- Outcome of the update:  SUCCESSFUL

- 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: BAREMETAL - HP ProLiant MicroServer GEN8

- Additional comment: Fixed VID & PID, Rebooted, Upgraded

 

 

- Outcome of the update:  SUCCESSFUL

- 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: BAREMETAL - HP ProLiant MicroServer GEN8

- Additional comment: Fixed VID & PID, Rebooted, Upgraded

 

 

- Outcome of the update:  SUCCESSFUL

- 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: BAREMETAL - HP ProLiant MicroServer GEN8

- Additional comment: Fixed VID & PID, Rebooted, Upgraded

Share this post


Link to post
Share on other sites
Posted (edited)
On 7/26/2020 at 2:53 PM, Fulatins said:

Auto installation

  • Outcome of the update: FAILED
  • DSM version prior to update: DSM 6.2.3-25426 Update 1
  • Loader version and model: Jun v1.04b - DS918+
  • Using custom extra.lzma: NO
  • Installation type: MSI B250M PRO-VDH / i3-7100 / 32 DDR4 2333
  • Additional comments: Node restarted but still "Fail to update the file. The file is probably corrupt."

 

Manual installation

  • Outcome of the update: FAILED
  • DSM version prior to update: DSM 6.2.3-25426 Update 1
  • DSM downloaded from: https://archive.synology.com/download/DSM/criticalupdate/update_pack/25426-2/
  • Loader version and model: Jun v1.04b - DS918+
  • Using custom extra.lzma: NO
  • Installation type: MSI B250M PRO-VDH / i3-7100 / 32 DDR4 2333
  • Additional comments: "Node restarted but still "Fail to update the file. The file is probably corrupt."
     

 

 

Auto installation

  • Outcome of the update: SUCCESS
  • DSM version prior to update: DSM 6.2.3-25426 Update 1
  • Loader version and model: Jun v1.04b - DS918+
  • Using custom extra.lzma: NO
  • Installation type: MSI B250M PRO-VDH / i3-7100 / 32 DDR4 2333
  • Additional comments: After FixSynoboot.sh script
Edited by Fulatins

Share this post


Link to post
Share on other sites
On 7/22/2020 at 6:32 PM, qwrty said:

- Outcome of the update:  FAILED

- DSM version prior update: DSM 6.2.3-25426

- Loader version and model: Jun's Loader v1.04b DS918+

- Using custom extra.lzma: No

- Installation type: Debian 10 / Qemu 3.1.0 (Debian 1:3.1+dfsg-8+deb10u6) / Libvirt 5.0.0 -  SuperMicro X11SSH-F (BIOS 2.3) / Intel E3-1275 v6

- Additional comment: File States Corrupt. Downloaded It A Few Times Do Not Know What is Going On, also Tried Manually. First failed update since I installed my VM 1 years ago.

 

Seems fixed after installing FixBoot.sh

more /etc.defaults/VERSION
majorversion="6"
minorversion="2"
productversion="6.2.3"
buildphase="GM"
buildnumber="25426"
smallfixnumber="2"
builddate="2020/07/08"
buildtime="06:14:27"

 

Share this post


Link to post
Share on other sites

- Outcome of the update:  SUCCESSFUL

- DSM version prior update: 6.2.3-25426

- Loader version and model: JUN'S LOADER v1.04b - DS918+

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - DELL Optiplex 3020 | i3-4160 | 8 GB RAM

- Additional comments: Reboot required, had to apply FixSynoboot.sh script, without that "Fail to update the file. The file is probably corrupt."

Share this post


Link to post
Share on other sites
Posted (edited)

- Outcome of the update:  FAILED

- 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: VMWare Fusion 11.5.3 High Sierra

- Additional Comment: Auto and Manual, File corrupt, impossible to install, even with a proper restart. Didn't try FixSynoboot.sh

Edited by Kryper
  • Thanks 1

Share this post


Link to post
Share on other sites

- Outcome of the update:  SUCCESSFUL
- DSM version prior update: DSM 6.2.3-25426 Update 2
- Loader version and model: JUN'S LOADER v1.04b - DS918+ / extra918plus_v0.8_recovery
- Using custom extra.lzma: No
- Installation type: BAREMETAL - HP Z240| i5-4590 | 8 GB RAM| HP NC360T
- Additional comments: Reboot required

Share this post


Link to post
Share on other sites

Outcome of the update:  SUCCESSFUL

- 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: BAREMETAL - HP Microserver  Gen7 N54L 

- Additional comments:  reboot required | Quad Intel NIC | WOL works | PhpVirtualBox works

Share this post


Link to post
Share on other sites

- Outcome of the update:  SUCCESSFUL

- DSM version prior update: DSM 6.23-25423

- Loader version and model: Jun's Loader v1.03B 3615XS

- Using custom extra.lzma: No

- Installation type: VM - Proxmox 6.1-8 - Supermicro X10SL7-F - E3-1246 v3 - Storage Disks using LSI 2308 PCI Device Pass-through

- Additional comment : Using "FixSynoboot.sh" startup script.  Reboot required.  

Share this post


Link to post
Share on other sites

Outcome of the update: SUCCESSFUL

- DSM version prior update: DSM 6.2.3-25426
- Loader version and model: Jun's Loader v1.04b - DS918+
- Using custom extra.lzma: NO
- Installation type: BAREMETAL – Celeron G4900; Asrock H310M-HDV 3.30; 4GB RAM, 3 disks, onboard NIC RTL8111H
- Additional comments: worked like a charm

Share this post


Link to post
Share on other sites

- Outcome of the update: SUCCESSFUL

- 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: BAREMETAL - Asus P10S-M [Intel Xeon E1230 v6] + Lenovo ServeRAID M5110 (mod firmware for IT mode)

- Additional comments: reboot required

 

Fixed CPU usage is 100% (Docker package) 😀

Share this post


Link to post
Share on other sites
Posted (edited)

- Outcome of the update:  SUCCESSFUL

- DSM version prior update: DSM 6.23-25423 update 2

- Loader version and model: Jun's Loader v1.03B 3615XS

- Using custom extra.lzma: No

- Installation type: TheCUS N5550

- Additional comment Reboot required

Edited by gquiring

Share this post


Link to post
Share on other sites

- Outcome of the update:  SUCCESSFUL

- DSM version prior update: DSM 6.23-25423

- Loader version and model: Jun's Loader v1.03b 3615XS

- Using custom extra.lzma: No

- Installation type: Proxmox 6.2-10

- Additional comment : Intel 1000e, reboot required, some time ago i corrected VID & PID (it has to be proper now - simplest way is to connect loader as the usb drive to some Windows VM, the same way that you're connecting it to xpenology machine, and read it using for example this tutorial https://xpenology.club/read-vid-and-pid-usb-stick/ or any other tool of your choosing)

Share this post


Link to post
Share on other sites

- Outcome of the Installation: SUCCESSFUL

- DSM version prior update: DSM 6.2.3-25426

- Loader version and model: Jun's Loader v1.04b - DS918+

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - ASROCK Z390M-ITX/AC, Intel Core i7 8700, 16GB RAM on U-NAS 410 Chassis with Noctua NH-L9i CPU fan

-Additional comments: Reboot Required

Share this post


Link to post
Share on other sites
Posted (edited)

-Outcome of the update: SUCCESSFUL

-DSM version prior to update: DSM 6.2.3-25426

-Loader version and model: Jun v1.04b - DS918+

-Using custom extra.lzma: NO

-Installation type: Fujitsu Esprimo E720, i3-4170, 2GB DDR3

-Additional comments: After FixSynoboot.sh script

Edited by Iwanme

Share this post


Link to post
Share on other sites

- Outcome of the update:  SUCCESSFUL

- DSM version prior update: DSM 6.2.3-25426

- Loader version and model: JUN'S LOADER v1.04b - DS918+

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - HPE MicroServer Gen10 (P04923-S01)

- Additional comments: 10Gtek(Intel) X520-DA1 SFP+ NIC working alongside internal GbE, Reboot Required

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.