Capture VOMA Dump for VMFS Datastore

Products

• VMware vSphere ESX 8.x

Issue/Introduction

In order to know the cause for the corruption, VOMA dump is required to be analyzed. This can most likely give the reasons for the corruption.

 

Environment

vSphere 7.0.x

vSphere 8.0.x

vSphere 9.0.x

Resolution

Log a ticket with Broadcom Support to execute the following steps:

1. Unmount the corrupted datastore from all the Hosts

2. Run the below command:

[root@ESXihost:voma -f dump -d /vmfs/devices/disks/naa.xxxxxxxxxx -D /vmfs/volumes/Datastorename/xyxyxy.dmp        (xyxyxy.dmp is the name of the file for VOMA dump and /vmfs/volumes/Datastorename is the chosen path location for it to be saved)

Output Example:

Module name is missing. Using "vmfs" as default
   Successfully created dump file /vmfs/volumes/Corrupted_Datastore_Name/xyxyxy.dmp
Running VMFS Checker version 2.1 in dump mode
   Detected valid GPT signatures
   Number    Start          End                Type
   1         2048           4294967262         vmfs

Checking for filesystem activity
Phase 1: Dumping partition table header                      st activity (4096 bytes/HB, 1024 HBs).                                                        \
 ON-DISK ERROR: Invalid volume health state 1
   Detected VMFS-6 file system (labeled:'Corrupted_Datastore_Name') with UUID:123456789, Version 6:81
Phase 2: Dumping VMFS Header and HB Region.
Phase 3: Dumping System Files.
Phase 4: Dumping File system tree

Note: 

Corrupted_Datastore_Name (Name for the datastore that is corrupt)

123456789 (UUID for the corrupted datastore)

Refer screenshot: