Disk dump fails with the error: Couldn't dump header 0xbad001

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

When Non-Volatile Memory Express (NVMe) SSDs are formatted with active diagnostic partition, you experience these symptoms:

• Disk dump fails during system panic.
• You see the error:
  
  DiskDump failed : Couldn't dump header 0xbad001

Environment

VMware vSphere ESXi 6.0

Cause

This issue occurs if NVMe SSDs are activated as diagnostic partition.

Resolution

This is a known issue affecting VMware ESXi 6.0.

Currently, there is no resolution.

To work around this issue, avoid configuring diagnostic partition on NVMe SSDs. If a diagnostic partition already exists on NVMe SSD, use these commands to deactivate the diagnostic partition.

To deactivate the diagnostic partition:

1. Remove the diagnostic partition using this command:
   
   # esxcli system coredump partition set -u
   
   
2. Run this command to configure the ESXi host to use another disk device for the diagnostic partition:
   
   # esxcli system coredump partition set -p mpx.vmhba2:C0:T0:L0:7

Additional Information

ダンプファイルの生成が次のエラーで失敗する： Couldn't dump header 0xbad001