December 18, 2012

Adding local storage disconnects the ESXi 5.x host

Adding local disks may on some servers lead to the ESXi 5.x host to be disconnected from vCenter. If you're connected directly to the ESXi host you will be unable to connect to it again.


In the vmkernel log you will see messages about how it fails to add the disk and it ends with "dumping cartel".
In order to be able to access the server through the vSphere client again you will need to restart the server's management agents. 

This needs to be done from the local console of the ESXi host which is easiest available through DRAC (or similar). You can find the correct menu under Troubleshooting options.



After situations like these, restarting the agents may take a few minutes.


The reason that adding the local disk crashes is that this server was shipped with a preconfigured disk with several partitions. If we remove these partitions first, these problems will not occur.

From the ESXi's command line (ESXi Shell (troubleshooting mode)) of ESXi we can use partedUtil to achieve this.


There are normally multiple volumes presented to an ESXi host and we do not want to delete the wrong one(s). You may need to run partedUtil against several of your volume IDs before you hit the correct one. You can then delete partition by partition from that volume by using partedUtil delete.

Now you will be able to add the disk as expected.

Thanks to Marcos Silva who pointed me in the right direction for finding a solution to this problem.

2 comments:

  1. Adding local disks may on some servers lead to the ESXi 5.x host to be disconnected from vCenter. If you're connected directly to the ESXi host you will be unable to connect to it again.Newcastle storage

    ReplyDelete
  2. It is a great post, what you said is really helpful to me. I agree with you anymore. Also great blog here with all of the valuable information you have. Keep up the good work you are doing here. Thank you for sharing such a useful post.
    opslagruimte

    ReplyDelete