wenlez

Anyone here uses the 1.04b loader on VMWARE, or Proxmox, and able to upgrade to the latest 6.2.1 Update 6? My Proxmox setup failed to update with these logs: any idea why? 2019-03-25T11:34:13-05:00 DSServer updater: updater.c:6006 Start of the updater... 2019-03-25T11:34:13-05:00 DSServer updater: updater.c:6272 ==== Start flash update ==== 2019-03-25T11:34:13-05:00 DSServer updater: updater.c:6276 This is X86 platform 2019-03-25T11:34:13-05:00 DSServer updater: updater.c:6293 The SynoBoot partitions exist. 2019-03-25T11:34:13-05:00 DSServer updater: updater.c:3680 SYNORedBootUpdCheckAndApply(3680): Skip bootloader update, no uboot_do_upd.sh exists 2019-03-25T11:34:13-05:00 DSServer updater: updater.c:589 file [zImage] is being copied to [/tmp/bootmnt] 2019-03-25T11:34:13-05:00 DSServer updater: updater.c:597 file [/tmp/bootmnt/zImage] process done. 2019-03-25T11:34:13-05:00 DSServer updater: updater.c:589 file [rd.gz] is being copied to [/tmp/bootmnt] 2019-03-25T11:34:13-05:00 DSServer updater: updater.c:597 file [/tmp/bootmnt/rd.gz] process done. 2019-03-25T11:34:13-05:00 DSServer updater: updater.c:589 file [grub_cksum.syno] is being copied to [/tmp/bootmnt] 2019-03-25T11:34:13-05:00 DSServer updater: updater.c:597 file [/tmp/bootmnt/grub_cksum.syno] process done. 2019-03-25T11:34:13-05:00 DSServer updater: updater.c:580 file [/tmp/bootmnt/updater] is being removed 2019-03-25T11:34:13-05:00 DSServer updater: updater.c:597 file [/tmp/bootmnt/updater] process done. 2019-03-25T11:34:13-05:00 DSServer updater: updater.c:580 file [/tmp/bootmnt/VERSION] is being removed 2019-03-25T11:34:13-05:00 DSServer updater: updater.c:597 file [/tmp/bootmnt/VERSION] process done. 2019-03-25T11:34:14-05:00 DSServer updater: updater.c:1036 This model DS918+ needs no factory upgrade 2019-03-25T11:34:14-05:00 DSServer updater: updater.c:6649 ==== Finish flash update ==== 2019-03-25T11:34:14-05:00 DSServer updater: updater.c:4929 successfully backup image for System Migration in path (/tmpRoot/.syno/patch). 2019-03-25T11:34:14-05:00 DSServer updater: updater.c:6673 ==== Finish updater post-action ==== 2019-03-25T11:34:14-05:00 DSServer updater: updater.c:6727 Congratulations!! The update has been completed!! Do configupdate when next bootup. 2019-03-25T11:34:14-05:00 DSServer smallupd@ter: smallupdate.cpp:1052 Failed to install /volume1//@smallupd@te_deb/libsynostorage-apollolake-bin_6.2-23824-s6_all.deb 2019-03-25T11:34:14-05:00 DSServer smallupd@ter: smallupdate.cpp:1052 Failed to install /volume1//@smallupd@te_deb/libsynostoragecore-apollolake-bin_6.2-23824-s6_all.deb 2019-03-25T11:34:15-05:00 DSServer smallupd@ter: smallupdate.cpp:1052 Failed to install /volume1//@smallupd@te_deb/linux-4.4.x-apollolake-bin_4.4.15-23824-s6_all.deb 2019-03-25T11:34:15-05:00 DSServer smallupd@ter: smallupdate.cpp:1052 Failed to install /volume1//@smallupd@te_deb/mdadm-apollolake-bin_6.2-23824-s6_all.deb 2019-03-25T11:34:15-05:00 DSServer smallupd@ter: smallupdate.cpp:1052 Failed to install /volume1//@smallupd@te_deb/netatalk-3.x-apollolake-bin_3.1.1-23824-s6_all.deb 2019-03-25T11:34:15-05:00 DSServer smallupd@ter: smallupdate.cpp:1052 Failed to install /volume1//@smallupd@te_deb/selfcheck-cu06_6.2-23824-s6_all.deb 2019-03-25T11:34:15-05:00 DSServer smallupd@ter: smallupdate.cpp:1395 failed to do install debain action 2019-03-25T11:34:15-05:00 DSServer smallupd@ter: small_update.cpp:20 Failed to apply smallupdate. 2019-03-25T11:34:15-05:00 DSServer synoscgi_SYNO.Core.Upgrade_1_start[7396]: Upgrade.cpp:236 Fail to exec smallupdater 2019-03-25T11:34:15-05:00 DSServer synoscgi_SYNO.Core.Upgrade_1_start[7563]: update_cpputil.cpp:705 synoservice: start all packages ... 2019-03-25T11:34:20-05:00 DSServer synoscgi_SYNO.Core.Upgrade_1_start[7563]: update_cpputil.cpp:755 synoservice: finish started all packages 2019-03-25T11:34:20-05:00 DSServer synoscgi_SYNO.Core.Upgrade_1_start[7396]: Upgrade.cpp:708 Failed to apply smallupdate

Oh, you're still on the 1.03b loader? I'm using the 1.04b loader for DS918+. We have a different setup then.

anyone with this Proxmox setup can update to DSM6.2.1-23824 Update 6?

- Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.1-23824 Update 4 - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: Proxmox Virtualization - Additional comments: After clicking update, it quickly restarted. Below is the log taken from

As far as I know, Intel turbo isn't working. That's why I've been using Proxmox and Xpeno as a guest. For that, Turbo works.

Does baremetal install on AsRock J4105-ITX work with the CPU's turbo? I recall it only run on stock 1.5GHZ.

There is no QEMU guest agent for Xpenology. At least not at the moment.

Seems like I can only have up to 6 virtual hard drives. any additional disk I add will not show up in DSM. my boot loader has the following, but doesn't seem to help. set sata_args='SataPortMap=666'

Oh, I see. My mistake, I thought you are using the DS918+ loader.

@blessendor, you didn't have the issue I had when upgrading DSM version?

so your Synoboot is set as an USB in the ARG, and it's vm-102-disk-2 (SATA1) ? The original ARG method no longer work with the latest boot loader, but you can use it as a SATA disk. Your boot order is cdn, which is cd-rom, disk, then network. can you try to change it in the Proxmox GUI, to book from SATA1 ?

I can try to help you, as I've been on the Proxmox + Xpenology track since we start. SO you got it to install, then it does its reboot? Whats your configuration of your VM? from /etc/pve/qemu-server/vmID.conf . Depends on your boot loader settings ( whether it's a SATA drive with the image, or the USB method ), you'll need to choose the right boot order.

when I try to update to DSM 6.2.1-23824 Update 2, I get this from DSM. This log is taken from /var/log/messages 2018-12-12T16:20:39-06:00 Portal updater: updater.c:6006 Start of the updater... 2018-12-12T16:20:39-06:00 Portal updater: updater.c:6272 ==== Start flash update ==== 2018-12-12T16:20:39-06:00 Portal updater: updater.c:6276 This is X86 platform 2018-12-12T16:20:39-06:00 Portal updater: boot/boot_lock.c(227): failed to mount boot device /dev/synoboot2 /tmp/bootmnt (errno:2) 2018-12-12T16:20:39-06:00 Portal updater: updater.c:5816 Failed to mount boot partition 2018-12-12T16:20:39-06:00 Portal updater: updater.c:2711 No need to reset reason for v.23824 2018-12-12T16:20:39-06:00 Portal updater: updater.c:6810 Failed to accomplish the update! (errno = 21) 2018-12-12T16:20:39-06:00 Portal smallupd@ter: smallupdate.cpp:1203 failed to exec updater -ir 2018-12-12T16:20:39-06:00 Portal smallupd@ter: smallupdate.cpp:1374 failed to update flash 2018-12-12T16:20:39-06:00 Portal smallupd@ter: small_update.cpp:20 Failed to apply smallupdate. 2018-12-12T16:20:39-06:00 Portal synoscgi_SYNO.Core.Upgrade_1_start[21967]: Upgrade.cpp:236 Fail to exec smallupdater 2018-12-12T16:20:39-06:00 Portal synopkg: pkg_pause.cpp:26 Fail to get package info of [ActiveBackup] 2018-12-12T16:20:39-06:00 Portal synopkg: pkg_pause.cpp:26 Fail to get package info of [ActiveDirectoryServer] 2018-12-12T16:20:39-06:00 Portal [ 305.068848] init: smbd main process (11367) killed by TERM signal 2018-12-12T16:20:39-06:00 Portal synoscgi_SYNO.Core.Upgrade_1_start[22080]: update_cpputil.cpp:705 synoservice: start all packages ... 2018-12-12T16:20:41-06:00 Portal synoscgi_SYNO.Core.Upgrade_1_start[22080]: update_cpputil.cpp:755 synoservice: finish started all packages 2018-12-12T16:20:41-06:00 Portal synoscgi_SYNO.Core.Upgrade_1_start[21967]: Upgrade.cpp:708 Failed to apply smallupdate

Thanks, @blessendor . I love the fact that I can use the Boot loader in a USB mode, so I can use all 6 SATA ports. However, it seems I can't update with the bootload as USB.

I have the same motherboard, but I use 2x 16GB DDR4 SOdimm. Even though it says max RAM is 8GB, it does work with 32GB.