Page 1 of 1

VMWare "no coredump target has been configured. Host coredumps cannot be saved"

Posted: Mon Dec 12, 2016 5:13 pm
by cah
After storage migration, we started seeing the warning "no coredump target has been configured. Host coredumps cannot be saved" on laxv1bvse50a/b/c. I didn't get a chance to check until today.

It was caused by the missing SAN boot disk after storage migration from the old array to the new array.
The steps to fix it and clear the warning are as follow. The new SAN boot disk will be used for the core dumps.

Code: Select all

~ # esxcli system coredump partition get
Not a known device: naa.60000970000198700284533030373842
~ # esxcli system coredump partition set --unconfigure
~ # esxcli system coredump partition set --unconfigure
~ # esxcli system coredump partition get
   Active: 
   Configured: 
~ # esxcli system coredump partition set --enable true --smart
~ # esxcli system coredump partition get
   Active: naa.60000970000196801669533030313239:7
   Configured: naa.60000970000196801669533030313239:7
 ~ # esxcli system coredump partition list
Name                                    Path                                                        Active  Configured
--------------------------------------  ----------------------------------------------------------  ------  ----------
naa.60000970000196801669533030313239:7  /vmfs/devices/disks/naa.60000970000196801669533030313239:7    true        true