Install XPEnology (DSM) 5.1 on ESXi 6 (HP MicroServer Gen 8)

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)

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! it’s okay, just shutdown the vm, and start it again, it will load the initial image that boot info does not overwritten by DSM.

– create raw disk mapping

ref: http://xpenology.com/forum/viewtopic.php?f=2&t=2147
use SSH & vsphere client

vsphere: Configuration > Storage Adpaters > HP Dynamic Smart Array B120i RAID Controller > Details
select the targeted disk > right click, copy Identifier to clipboard

SSH to ESXi console.
# vmkfstool --help -z –createrdmpassthru /vmfs/devices/disks/…

– install open-vm-tools
download “open-vm-tools_bromolow-5.1_9.10.0-2476743-1.spk” from http://xpenology.me/downloads/, see link in http://xpenology.com/forum/viewtopic.php?f=2&t=5294

Go to “Package Center” > “Settings” and tick the box “Any Publisher”
Manually install with the downloaded file.