wenlez

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

my guess is that your motherboard now "wants" to boot from the hard drive with the DSM OS installed. You may need to go to the BIOS, and change the boot order to first start from your USB drive.

Does the ds3615 work for you? I still have the mount failed error.

kazuni did say DSM 6.2-23739, so it would has to be 1.03 loader. But there is a 1.03b? where you get that?

I am running into the same problem as well. I'm trying to troubleshoot this.

Disk order with "machine: q35" enabled in Proxmox. If out that line, the disk will start from 1st box.

Does anyone use machine: q35 ? If I have this option enabled, all my hard drives are shifted to a higher number. Any idea on how to fix that?

Looks like I solved my own problem. Enabling Write Cache in DSM is the key.

I encounter similar issue, posted on a different topic. I have no SSD Cache, and my set up is virtualized.

SATA controller chipset. doesn't have to be supported by ESX. As long as your CPU(and its chipset) supports VT-d, you should be passthrough individual PCI(e) device to the VM. Also check the VM/ESX log, during the VM start. If ESX has issue passing through the PCI device, it would say something in the log. You can also do a "lspci" in the VM to validate. I have Proxmox 5.1, and the onboard Intel SATA controller is reported as: 0000:01:00.0 Class 0106: Device 8086:a282 (prog-if 01) Subsystem: Device 1458:b005 Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 45 Memory at 91600000 (32-bit, non-prefetchable) [size=8K] Memory at 91603000 (32-bit, non-prefetchable) [size=256] I/O ports at a020 [size=8] I/O ports at a028 [size=4] I/O ports at a000 [size=32] Memory at 91602000 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [70] Power Management version 3 Capabilities: [a8] SATA HBA v1.0 Kernel driver in use: ahci