Call “HostDatastoreSystem.CreateVmfsDatastore” for object “ha-datastoresystem” on ESXi “host??.??????.com” failed.

Today I was playing in my home lab environment. After installing a new vSphere 4.1 host, I went on to add an  iSCSI target as a datastore, however it failed with an error

Call "HostDatastoreSystem.CreateVmfsDatastore" for object "ha-datastoresystem" on ESXi "host??.??????.com" failed.

I failed to understand why???

Just a day before I had used the same LUN to create a VMFS5 datastore on a vSphere 5.0 host. So I decided to investigate further. Logged in to the vSphere host via the troubleshooting shell and went through the /var/log/messages.

I found the following error:

Hostd:  Error : Unsupported partition table (gpt) on disk. Only msdos supported

Then I realized that when I created a VMFS5 partition on the same LUN, it also updated the disk label to “gpt”, and whereas vSphere 5.0 can understand both “gpt” & “msdos”, vSphere 4.1 is unable to handle the “gpt” labels .

The fix was to remove the gpt label! So I quickly assigned the said iSCSI LUN to my Linux box, and removed it using the parted utility.

root@linux-vm:~# parted /dev/sdd
GNU Parted 2.2
Using /dev/sdd
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) mklabel msdos
Warning: The existing disk label on /dev/sdd will be destroyed and all data on this disk will be lost. Do you want to continue?
Yes/No? yes
(parted) quit
Information: You may need to update /etc/fstab.

root@linux-vm:~#

After removing the “gpt” label, on retrying to create a VMFS3 filesystem on the said LUN, everything worked smoothly.

Moral of the Story: If you are planning to use/format a LUN with VMFS3 using vSphere 4.x and if you had used the LUN earlier to create a VMFS5 filesystem then you will first need remove the “gpt” label from your LUN.

Advertisements

15 thoughts on “Call “HostDatastoreSystem.CreateVmfsDatastore” for object “ha-datastoresystem” on ESXi “host??.??????.com” failed.

  1. Hello, I am having the same problem. Any chance you could provide step by step instructions for those who are not typically Linux users? Do I need a bootable Linux USB stick? Or would it not be worth the effort and just completely erase the USB stick I am botting ESXi from?

    • Well, you will need to boot Linux on a system that can see the said LUN which was earlier formatted with VMFS5. The other way is to present this LUN to a machine where you have Linux installed. After presenting the LUN, run the ‘parted’ command and remove the GPT partition table. The exact steps for using parted are mentioned in the blog.

  2. Just grab a copy of the GParted LiveCD and run that.

    Once booted in to the LiveCD:

    1) Select ‘Devices’
    2) Select ‘Create a partition’
    3) Leave it as MSDOS and click apply
    4) Reboot and attempt again.

  3. GParted LiveCD not helping for my.

    My solution:
    1) Disconect all HDD except leave only this one
    2) Loade ESXi 4.1 install & install on this one HDD. Instaliation wizard fully formating HDD and creating vmfs3.
    3) Connect all hdd back and boot original ESXi 4.1 system but i getting error: System detected two partitions with seame UID name.
    4) Reaboot and start GParted Live CD then Delete partitions from hdd, leaving unpartioned
    5) Start original ESXi 4.1 add create new datastore.

    • That’s true. However that may not be the best option if you are working in an Enterprise environment where you may need to raise a change request for the same. 🙂

      — Shekhar

  4. Hai … I am still facing the issue after changing the label as “msdos”…. below is the error pop up i am getting…
    Call “HostDatastoreSystem.CreateVmfsDatastore” for object “ha-datastoresystem” on ESXi “172.35.14.150” failed.
    Operation failed, diagnostics report: Unable to create Filesystem, please see VMkernel log for more details: Function not implemented

    Any idea????

      • Well it should work.

        Could you please tell me in detail the exact steps followed by you when you hit this error? Also could you find out what is reported in /var/log/messages when you hit this error.

  5. Another Solution!!
    Add the same volume as VMFS-3, this should be successful as the previous partition would be VMFS-5.

    Once VMFS-3 is created, you can now delete the datastore to create a VMFS-5 datastore.
    This worked for me.

  6. Añadan el hdd con problemas a un sistema windows, usen el comando DISKPART para limpiar el disco añadido.
    ejemplo: si al listar el disco, es el disco 1
    Abrir linea de comandos (cmd) y ejecutar DISKPART
    Luego ir ejecutando:
    DISKPART> list disk
    DISKPART> select disk 1
    DISKPART> clean

    Luego añadan el disco limpiado al ESXi y listo, no habrá inconvenientes de ser agregado como nuevo DATASTORE

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s