Ermite

DSM 6.2.3-25426 Update 2

Recommended Posts

- 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
Posted (edited)
Le 22/07/2020 à 13:32, qwrty a dit :

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

 

Should I use custom extra.lzma now ?

Host machine:

 

 

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"

 

Edited by qwrty

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
On 7/23/2020 at 1:33 AM, mitzone said:

- 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: ESXi 6.7

 

I also had the "File is corrupt issue." Fixed it after installing FixBoot.sh :

 

 
 
 

Had the same issue here, thanks for the heads up on the fix.

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

- Outcome of the update: SUCCESSFUL

- DSM version prior update: DSM 6.2.2-24922

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

- Using custom extra.lzma: Yes, v0.13.3 by IG-88

- Installation type: BAREMETAL - Lenovo IdeaCentre 310S-08IAP, CPU: Celeron J3455, NIC: onboard RTL8111GN

Edited by zsdd

Share this post


Link to post
Share on other sites

- Outcome of the update:  SUCCESSFUL

- DSM version prior update: None, clean install

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

- Using custom extra.lzma: No

- Installation type: Thecus N5550

- Additional comment : Regular installation

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: VM in ESXi 7.0 

- Additional comments: Update via DSM GUI. 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 - Dell Optiplex 980

- Additional comments: Update via DSM GUI. 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 to DSM 6.2.3-25426 Update 2

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

- Using custom extra.lzma: YES and extra2 from 0.11 IG-88

- Hardware details: Gigabyte GA-J4105N-H, 1x4Gb DDR4 ram, Raid 5 4x2TB Seagate Ironwolf Harddisk, LAN: Realtek RTL8111 Gigabit, SATA3: 2x Intel chipset; 5x Sata3 Expansion card.

- Additional comments: Shutdown and Reboot no issue. 

Edited by htvsm

Share this post


Link to post
Share on other sites

- Outcome of the update:  SUCCESSFUL

- DSM version prior update: DSM 6.2.2-25426

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

- Using custom extra.lzma: No

- Installation type: BAREMETAL - HP ProLiant MicroServer Gen8 (Xeon E3-1260L)

- Additional comment: Working LSI9211-8i + Internal NIC.

 

- Outcome of the update:  SUCCESSFUL

- DSM version prior update: DSM 6.2.2-25426

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

- Using custom extra.lzma: No

- Installation type: VM in ESXi 6.5

- Additional comment: Need FixSynoboot.sh.

 

 

Edited by reketeee

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 J4105-ITX production system

 

Share this post


Link to post
Share on other sites

- Outcome of the update:  SUCCESSFUL

- DSM version prior update: DSM 6.2.2-24922 U4

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

- Using custom extra.lzma: Yes

- Installation type: Baremetal on Supermicro X11SSL-CF, 16GB ECC mem., 6 SATA drives attached to LSI3008 SAS controller.

  Used the existing (unmodified) bootloader that was previously carried over and operating for DSM 6.2.2-24922. The upgrade completed normally

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.