VMware vSphere 5.5 – Call “HostStorageSystem.ComputeDiskPartitionInfo” for object “storageSystem” on ESXi failed

Intel NUC

I recently installed VMware vSphere 5.5 on my Intel (Haswell) NUC (D34010WYH1).

Today I got the following error when I tried to create a VMFS 5 datastore on the SATA hard drive that I installed in my NUC:

Call "HostStorageSystem.ComputeDiskPartitionInfo" for object "storageSystem" on ESXi failed

A quick search of the internet took me to this solution which required logging as root and manually deleting partitions on the drive.

Fortunately I found a simpler solution.

I was able to create a datastore using the (legacy) VMFS 3 filesystem and then just upgraded it to VMFS 5.


Installing VMware vSphere ESXi 5.5 on an Intel (Haswell) NUC (D34010WYH1)

Intel NUC

My vSphere hardware has long been due an update and I have finally got my hands on an Intel NUC ! Here is my (completely un-supported) parts list:

The D34010WYH1 NUC gives me the option of storing virtual machines on a 2.5 inch HDD or SSD inside the NUC (and the 1TB WD Red drive gives me a good amount of local storage to play around with). The RAM is low voltage (1.35v) which is required. The 32 Gb USB 3 flash drive is over-kill (only 4GB is required for vSphere 5.5) but it is very small (and pretty fast too). I needed the HDMI adapter to connect the NUC to my HDTV during vSphere installation.

The installation process is quite straight-forward and you will need the following:

Before installing vSphere we need to create a custom .iso image that includes the two .vib drivers that we downloaded. This is done using ESXi Customizer.

ESXi-Customizer 01

The first time you run ESXi Customizer select the vSphere 5.5 ,iso image and the network driver (net-e1000e-2.3.2.x86_64.vib) to create a customized image.

Run ESXi Customizer again and this time select the customized .iso image and add the sata driver (sata-xahci-1.10-1.x86_64.vib) to create a final customized .iso image.

I chose to burn my customized .iso to CD and install using a USB DVD drive – if you want to use a flash drive to install you will need to use UNetbootin.


In UNetbootin select the Diskimage radio button and then browse to the location of your final custom .iso. Select the flash drive to copy files to and then click the OK button.

In the BIOS of my NUC I disabled the UEFI option in the Boot menu. After that I booted from my USB DVD drive and installed vSphere to a USB 3 flash drive.

[I did test installing from one flash drive to another too and this also worked without any issues].




2013 Potential Hardware for vSphere Home Nanolab and NAS Refresh


My current VMware vSphere white-box will be 5 years old in August. It has an AMD Athlon X2 BE-2400 Brisbane @2.3GHz and 8Gb of RAM – and these days 8Gb of RAM is just not enough.

The hardware for my NAS is more recent – a HP Microsever N40L with 6Gb of RAM, running FreeNAS 8.x.

The cpubenchmark score for my vSphere box is 1333 – the score for the N40L is 979.

While I still need to look at the performance of ZFS on the N40L (it is OK but not exactly where I would like it to be) I know that a lot more CPU is not desperately needed for new vSphere hardware (but it would be nice).

I have been considering the Intel NUC (Next Unit of Computing) as an alternative to having a tower PC to run vSphere for a while now. It maxes out at 16Gb of RAM and it really shines in terms of its power efficiency (13-27 watts) and diminutive size (4″ x 4″). The i3 -3217U DC3217IYE NUC (Ivy Bridge architecture) is the current NUC that I have my eye on.

The Intel i3 NUC
The Intel i3 NUC

The issue with the NUC though is storage – I can either install an msata SSD in the NUC or use shared storage on my NAS (or both). I would like to use local storage on the NUC for speed and back up VMs to my NAS – the cost of SSDs will limit my local storage capacity though.

The next generation of NUCs are based on the Haswell architecture and include Core i5 (Horse Canyon) and i7 (Skull Canyon) CPUs. The i5-3427U offering (cpu benchmark: 3580) is of interest to me here as it includes Intel vPro remote management capabilities.

This still leaves us with the 3rd generation of NUCs (also Haswell) which have an on-board sata and sata power connector – these are slated to arrive in Q3 2013.

3rd Gen Intel NUC
3rd Gen Intel NUC

The other option for a diminutive vSphere box is the Gigabtye take on the NUC called Brix. It looks like Gigabyte plans to offer Intel (i3 – i7) CPUs and AMD Kabini (E1-2100, E1-2500 & E2-3000 dual core, and A4-5000 quad core) CPUs.

I think it will be worth keeping an eye on the Brix offerings to see where they differ from the NUC. The key areas for me will be efficiency, pricing and storage – what if Brix offers a 2.5 or 3.5″ internal drive bay, for example? I imagine that the AMD offerings will be cheaper than the Intel NUC – but we will have to wait and see.

On the home NAS side of things HP very recently updated their Microserver (Gen 8) with Celeron and Pentium models:

  • Intel® Celeron® G1610T (2 core, 2.3 GHz, 2MB, 35W)
  • Intel® Pentium® G2020T (2 core, 2.5 GHz, 3MB, 35W)

This does potentially make the Microserver a better vSphere candidate too, especially as the supported RAM has been upped to 16Gb.

The other good news is the built in iLO support, dual gigabit NICs and USB 3.0 ports (as seen on the beta unit, at least):

HP Microserver (Gen 8) rear panel - courtesy of
HP Microserver (Gen 8) rear panel – courtesy of blog.themonsta.id.au

So I’ll be keeping an eye on the new generation of Microserver too. The additional CPU and RAM are quite welcome (especially for ZFS). I am also keen to know the power consumption for these machines as a whole.

Either way with both the NUC and the Microserver I can build a power efficient and much smaller lab.

If I can score a couple of NUCs and another Microserver by the end of the year, I will be a happy man!