VMware Fix for Call “HostDatastoreSystem.QueryVmfsDatastoreCreateOptions” for object “ha-datastoresystem” on ESXi failed

Jun 26, 2016 | Linux, Server administration, Technology, Virtualization | 24 comments

While installing ESXI 6 update 2 on a Dell R410 I found that I could not create a datastore using the VSphere UI. assumed this was something to do with the Windows partition that was previously used on that disk so I decided I’d drop back into the CLI and delete the existing partition manually.

Here’s how you do this:

  1. Open VSphere.
  2. Go to Configuration
  3. Click Security templates on the left
  4. Click Properties
  5. Select SSH
  6. Click Options
  7. Click start
  8. Connect to your host using PuTTY or any other SSH client
  9. Move to the /dev/disks directory

    cd /dev/disks/

  10. List the files here


  11. Match the identifier with the datastore that you cant create in VSphere.
    For example: naa.6d4ae5208f875700172a910c5402c983
  12. Run partedUtil to delete that partition.

    partedUtil mklabel /dev/disks/naa.6d4ae5208f875700172a910c5402c983 msdos

  13. Go back into VSphere and create the datastore.
  14. Now disable the SSH service to clean up and close the security vulnerability that you’ve opened.

I hope that helps someone. It worked for me perfectly.


  1. Jarod

    Thank you so much for this. I was ready to pull my hair out with this error.

  2. Jakub

    Thank you for sharing your experience!!! You save me lots of time 🙂

  3. manolis manolidis

    thanks you are great.

  4. Roman


  5. PatrickOliveira

    Very good. Thank you very much!!

  6. M to the K

    Cheers! Worked like a charm.

  7. Gabriel

    thanks! you are the best

  8. James

    Thank you!! This was just what I needed, quick and easy!

  9. Samuel

    Thank you man! I thought is a disk error, and was near throwed it away, until i find your post! It worked very well. Thank you again!

  10. Gotye

    How was the cane made? Who made it?

  11. Andika

    Thank you so much for this lesson. It work for me perfectly 🙂

  12. Michel G

    Very nice write up, saved me a lot of time figuring it out by myself. This happened to me when I reconfigured a raid set without removing the datastore from VMware before reconfiguring. Somehow the identifiers get left behind. This fixes that in 1 minute. Perfect.

  13. Vital

    Worked for me too, thank you.

  14. David

    With this fix I was able to add my 3.6TB array on my new (old) Dell server.
    Thank you very much!

  15. Sean

    That fix it right up, Thanks!!!

  16. Steve

    You tha MAN! Just put a new 500GB SSD in my primary host and suddenly couldn’t create datastores…this fixed it up. Thank you!!

  17. martyn

    thanks dude

  18. Bart

    Solution worked well TYVM digitaldarragh :0) for sharing this solution with us

  19. Justin

    worked like a champ!

  20. Pyromancer

    Thanks for this, tried to add a 10TB disk that had previously been part of a raid to an ESXi box and got this error, this fix cured it instantly. Much appreciated.

  21. Øyvind

    Nice! Thanks

  22. Kamil Toprak

    It worked for me . Thanks for your help

  23. hamid

    Thanks you for sharing but unfortunately i have below error on command

    Error: Read-only file system during write on /dev/disks/naa.600508b1001cf93ad5dbf49f3d71e213
    WriteNewPtable: Unable to commit to device /dev/disks/naa.600508b1001cf93ad5dbf49f3d71e213



  24. cip

    Thank you!


Leave a Reply to PatrickOliveira Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.