I was doing a hardware upgrade for some of the VMWare hosts in lazy fashion. I pulled the disk (small SATA SSD) from old host (HP BL460c Gen8) and inserted it into new host (HP BL460c Gen9). The old hosts used SAS HBA and the new hosts are using integrated SATA controller.
Using this method I avoided the unnecessary re-installation of the hosts. But when they booted I got warning message – “No coredump target has been configured. Host core dumps cannot be saved.”
Update 12.08.2016 – Starting from ESXi 5.5 U3 build 4179633 this issue will fix it self automatically. You can read more from here.
I turned to KB article 2004299 to fix it but I had to do a little more than described there.
My fix process was following:
- Logged in to ESxi via SSH
- esxcli system coredump partition get returned – “Not a known device: naa.xxxxxxxxxxxxxxxxxxxxxxxxxxx”
- Executed following command to list all the disks and find the SSD disk I was booting from: esxcli storage core path list | more
- My SSD disk was “Runtime Name: vmhba0:C0:T0:L0”, “Device: t10.ATA_____MO0100EBTJT_____________________________S0RFNEAC603385______”
- Executed following command to list partitions on my disk – “esxcli storage core device partition list -d t10.ATA_____MO0100EBTJT_____________________________S0RFNEAC603385______”
- Identified that my coredump partition is number 7 (type fc)
- Executed following command to set the partition: esxcli system coredump partition set –partition=”t10.ATA_____MO0100EBTJT_____________________________S0RFNEAC603385______:7″
- Executed the following command to activate the partition: esxcli system coredump partition set –enable true
- esxcli system coredump partition get now returns and the warning message dissipated: