Piszki Lab | EN

My case study in the clouds…

Magic partition aka "No vmkcore disk partition is available".


Much of the servers used by us in the Datacenter is equipped with internal hard drives. They are not used for anything. I decided to take the opportunity to move these drives to our Lab in order to better test the EMC ScaleIO. Before physically removing, done on each server detach procedure. In some cases, this procedure ended with the message “The device does not contain a diagnostic partition”:



The strange thing is that no one did not create such a partition on local disks. According to this KB, partitions can be assumed to activate and deactivate from the esxcli. You can also remove it by setting up the datastore to “infected” disks using the whole space. Then remove datastore and disconnect the drive (properly).


The second and better method is to reset the information about vmkcore using command:

esxcli system coredump partition set -u

No matter which method you choose, delete all partitions vmkcore ends with the message: “No vmkcore disk partition is available and no network coredump server has been configured. Host core dumps can not be saved “. The solution to this problem is simple (once you will do chores with disks), basically boils down to a single command:

esxcli coredump partition set –enable true –samart


And all this, the simplest solutions are the best!

Rate this article:
[Total: 2 Average: 4.5]

Author: Piotr Pisz

Computer always, since I got a Commodore 64 at the end of primary school, through his beloved Amiga and Linux infinite number of consoles, until today, fully virtual day. Since 2001, Unix/Linux Systems Administrator, for seven years a faithful companion and protector of Solaris system, until his sad end. In the year 2011 came in the depths of virtualization, then smoothly ascended into the clouds and continues there today. Professionally working as Systems Architect in the Polish Security Printing Works.

Leave a Reply

Required fields are marked *.