"Cannot change the host configuration" error message when adding disk storage to a VMware vSphere ESXi Host

"Cannot change the host configuration" error message when adding disk storage to a VMware vSphere ESXi HostExperiencing the “Cannot change the host configuration” and or Call “HostDatastoreSystem.QueryVmfsDatastoreCreateOptions” for object “datastoreSystem-xxxx” on vCenter Server error message when trying to add disk storage to your VMware vSphere ESXi host?  If so, check out my video below where I run through the easy to follow steps in resolving this issue.

As with most things there can often be a multiple causes to a particular error, though in my experience I have found in the majority of cases this particular error message is down to adding pre-used disks which contain an existing partition or similar information on the disk.  Now this isn’t always the case, so in the basic steps outlined in the video I show you how to confirm what the actual error is.

*** IMPORTANT ***  Whenever touching anything to do with your storage, always ensure you have a good backup of your production data first.  Even in an instance such as this where “in theory” you are adding a “new” disk to your ESXi host, if you were to identify the disk ID incorrectly you could end up impacting data on another disk.  Just be careful, and use common sense.  Smile

 

Also, check out this useful VMware KB article for some more troubleshooting information.

I hope this videos helps, and definitely keep note of the couple of commands I use as these often prove useful when storage trouble shooting on an ESXi host.  If you found the video of use, please consider giving it a thumbs up on YouTube and also subscribing to my channel – thanks.

About Simon Seagrave 706 Articles
Simon is a UK based Virtualization, Cloud & IT Technology Evangelist working as a Senior Technology Consultant and vSpecialist for EMC. He loves working in the ever changing IT industry & spends most of his time working with Virtualization, Cloud & other Enterprise IT based technologies, in particular VMware, EMC and HP products. As well as on this site, you can find him on Twitter and Google+

24 Comments

  1. Many thanks for your video, fast, simple and useful. I avoided to format my disk after disconnecting and using external pc.
    Thank again

  2. Hi there,

    Great article! I have just tried this and encountered a problem. When i place the command ‘partedUtil getptbl… etc’ I get the error – unable to read partition table for device XXX

    then if i try the ‘setptbl’ commmand – I get “Error:Can’t create partition outside the disk!”

    Is this something you’ve ever come across? Many thanks,

  3. Simon, I am getting the following error message while trying to perform the same steps.

    Error: Connection timed out during write on /dev/disks/naa.600c0ff000db109c8c5a545801000000
    WriteNewPtable: Unable to commit to disk

    please help me to resolve the issue. thanks in advance.

  4. Really good info. I have converted a server – which has RAID disc and could not add storage.

    Worked really well. My disc were also call t10…..

  5. Hello Simon-

    I just ran across your post here, and it was most helpful. While your fix didn’t work for me (I got “Error:Can’t create partition outside the disk!” errors like James and Joey had). I think this might be due to the drive being a 2Tb (which should* work on msdos, but didn’t for me. Solution: change msdos to gpt in your instructions and everything seems to have worked.

    Just a couple comments:

    1) Your site seems to be having trouble in Chrome with AdBlock- lots of redraws, hesitations and obscuring of the entire site. It took me a chunk of time to even see the article.

    2) While your video was fine and useful; it suffers from the usual video problem: I had to find headphones to listen to it (no speakers on my pc) and then it took me 15 minutes to get the info that I could have gotten in 30 seconds if you had written out the commands. Not to mention I could cut and paste, and wouldn’t have followed along and typed the incorrect command you have in your video because I had to pause to enter it, then you say “oops, no it’s this command”.

    Not trying to beat you up, it was still a very useful post, it just would have been more* useful as a text article vs. a video (ideally, it would be both).

    Keep up the good work!

  6. Thanks for your video. I had the same error when trying to configure a vFlash SSD disk. Following your steps confirmed the same partition error and fixed it. I was able to configure the vFlash in the GUI after that.

  7. First of all: THANKS for your fix!

    However, with one of three disks on a fresh installed ESXi 6.7 on a HP DL380 G8, I’ve encountered another crazy error:
    ———————————
    [root@VMHost2:~] partedUtil setptbl /vmfs/devices/disks/naa.600508b1001cf46f601272edf0b71c21 msdos
    msdos
    0 0 0 0
    Error: Can’t have a partition outside the disk!
    ———————————

    I found the following fix for that particular problem:

    partedUtil mklabel “/vmfs/devices/disks/naa.600508b1001cf46f601272edf0b71c21” gpt

    after that, the setptbl command worked as on the two other disks!

  8. Excellent video. I allmost got it right but the second command doesn’t want to finish and the entire ssh session gets unresponsive (i can hit the enter and get a new line, but that is all).. The same applys to the third command. Where I get
    msdos
    0 0 0 0
    and the prompt doesn’t get back

  9. First I thought the freshly created logical drive on my HP RAID contorller had a failure – but this drive was working properly:

    => ctrl slot=1 pd all show status

    physicaldrive 2I:0:5 (port 2I:box 0:bay 5, 500 GB): OK
    physicaldrive 2I:0:6 (port 2I:box 0:bay 6, 500 GB): OK
    physicaldrive 2I:0:7 (port 2I:box 0:bay 7, 250 GB): OK
    physicaldrive 2I:0:8 (port 2I:box 0:bay 8, 250 GB): OK

    => ctrl slot=1 ld all show status

    logicaldrive 1 (465.7 GB, 1): OK
    logicaldrive 2 (232.9 GB, 1): OK
    After some research in the internet I discoverd that a invalid GPT label can be the reason for this issue. A solution is to re-create the GPT table using the gParted live medium. I didn’t want to reboot my system – especially because ESXi can do this on its on as is also has the parted utility installed. You only need to know the device name of the logical drive with the invalid GPT table. If you don’t know this file have a look at the output of the fdisk utility and compare the drive sizes:

    # fdisk -l
    # partedUtil mklabel /dev/disks/naa.xxx gpt
    After re-creating the GPT label the VMFS creation worked like a charm for me

  10. Your comment is awaiting moderation.

    This was very helpful when I ran into this problem while trying to add a bunch of old drives to ESXi 6.7u3 on a Dell R710.

    Thanks!

Leave a Reply

Your email address will not be published.


*


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