similar to previous blog: https://www.hang321.net/2014/08/16/debian-chroot-on-dsm/ Prerequisite: add custom source:  Package Centre > Settings > Package Sources > add Name: SynoCommunity Location:  https://packages.synocommunity.com/ Installation: – select Debian Chroot and click install – select yes to install python (SynoCommunity version) as well. – after installation completed, ssh to DSM as root root@diskstation> /var/packages/debian-chroot/scripts/start-stop-status chroot bash: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8) root@diskstation:/# – now under chroot ##backup and update source list. e.g. from France to Australia ##see https://www.debian.org/mirror/list sed -i.`date +%Y%m%d` ‘s/fr.debian.org/au.debian.org/g’ /etc/apt/sources.list aptitude update aptitude upgrade aptitude install locales dpkg-reconfigure locales dpkg-reconfigure tzdata # optional: packages to install aptitude install less vim curl rsync screen openssh-server bash-completion – enable home for users: Control Panel > User > Advance, “Enable user home services”, Apply. ls -al /var/services/homes  symbolic link updated and pointed correctly – some additional directories want to be mount by startup script diff -u /var/packages/debian-chroot/scripts/start-stop-status.org /var/packages/debian-chroot/scripts/start-stop-status — /var/packages/debian-chroot/scripts/start-stop-status.org +++ /var/packages/debian-chroot/scripts/start-stop-status @@ -19,6 +19,7 @@ grep -q “${CHROOTTARGET}/sys ” /proc/mounts || mount -t sysfs sys ${CHROOTTARGET}/sys grep -q “${CHROOTTARGET}/dev ” /proc/mounts || mount -o bind /dev ${CHROOTTARGET}/dev grep -q “${CHROOTTARGET}/dev/pts ” /proc/mounts || mount -o bind /dev/pts ${CHROOTTARGET}/dev/pts + grep -q “${CHROOTTARGET}/home ” `realpath /var/services/homes` || mount -o bind `realpath /var/services/homes` ${CHROOTTARGET}/home # Start all services ${INSTALL_DIR}/app/start.py @@ -35,6 +36,7 @@ umount ${CHROOTTARGET}/dev umount ${CHROOTTARGET}/sys umount ${CHROOTTARGET}/proc + umount ${CHROOTTARGET}/home } daemon_status () – setup users on debian domain ## find user id id -u username id -g username ## Debian domain. XXXX YYYY is the id value adduser username -uid XXXX –gid YYYY –home /home/username …

Download: Boot images of XPEnoboot DSM 5.2 from http://xpenology.me/downloads/ Official DSM 5.2 file from https://www.synology.com/en-global/support/download/DS3615xs Installation: 1. upload XPEnoboot_DS3615xs_5.2-5565.1-9d792e9.vmdk and XPEnoboot_DS3615xs_5.2-5565.1-9d792e9-flat.vmdk to datastore via vSphere client 2. Edit the old boot image hard disk to IDE (0:1) 3. Then add a new Hard disk from the image uploaded above, make it as “Nonpersistent” 4.  start virtual machine, select “Install/Upgrade” from boot screen, like step 1 in http://www.xpenology.nl/how-to-install-dsm-5-2/ 5. click install 6. select migration 7. upload the official pat file 8. after reboot, login, open Control panel, check update. There is an DSM 5.2-5565 Update 1 file, download and upgrade. 9. (optional) after verifying everything okay, remove the old boot image harddisk [IDE(0:1)].   Appendix DSM 5.2 support docker! If I knew it earlier, I may not install ESXi and DSM as vm…

My installation record. As of today, DSM 5.2 is out. Thanks to XPEnology team, bootloader now support DSM 5.2 Basically follow official documentation: http://www.xpenology.nl/vmware-esxi-installatie/ http://www.xpenology.nl/installation-dsm-5-1/ http://xpenology.me/downloads/ and somebody’s tutorial http://seiler.it/vmware-esxi-5-5-installation-hp-proliant-microserver-gen8/ http://www.chiphell.com/thread-867588-1-1.html   ESXi (vShpere 6) For me, my iLo web interface does not support after POST (boot up), so I used unetbootin to expand the HP-VMware ISO file to USB drive. install vSphere 6 client, manage storage – got create datastore failure: Call “HostDatastoreSystem.QueryVmfsDatastoreCreateOptions” for object ‘ha-datastoresystem’ on ESXi [host] failed. – failure due to my old SSD contains existing partition info: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2007328 solution: enable SSH access on vshpere http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1003808 find disk from #ls -lah /vmfs/devices/disks/  or vSphere client Then fix and review (should be your own value of naa.xxxxxxx) # partedUtil mklabel /vmfs/devices/disks/naa.60050xxxxxxxxxx msdos # partedUtil getptbl /vmfs/devices/disks/naa.60050xxxxxxxxxx reference: http://www.vexperienced.co.uk/2012/01/02/error-adding-datastores-to-esxi-resolved-using-partedutil/ http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1008886 http://serverfault.com/questions/537101/how-to-delete-old-linux-partition-with-esxi   Installation of DSM 5.1 Then follow the XPEnelogy EXSI version offical installation guide http://www.xpenology.nl/vmware-esxi-installatie/ – Fail to boot up, “Missing Operating System” error. due to DSM overwrite partition and boot disk info http://xpenology.com/forum/viewtopic.php?f=15&t=5255 “IDE (0:0) is important because this is the boot disk that starts up XPEnoboot Non-persistent is important because it prevents the non-booting situation after you do the DSM install. Technical explanation is during DSM install all hard drives get repartitioned including the XPEnoboot drive, the non-persistent setting makes these changes temporary and after a reboot the original XPEnoboot boot partition is returned.” My fix was delete the VM, re-create VM, set IDE (XPEnoboot_DS3615xs_5.1-5022*) to “non-persistent”, then follow the installation process after installation complete, boot disk failure again! …