Failed to migrate the VM to with the error: File system specific implementation- Cannot open the disk '/vmfs/volumes/UUID/VM/VM.vmdk' or one of the snapshot disks it depends on. 14 (Bad address)

Products

• VMware vSphere ESXi

Issue/Introduction

Attempting to migrate the VM fails with the error:

• File system specific implementation of GetObject[fs] failed The source detected that the destination failed to resume. YYYY-MM-DDTHH:MM:SS The VM failed to resume on the destination during early power on. Module Disk power on failed. Cannot open the disk '/vmfs/volumes/UUID/VM/VM.vmdk' or one of the snapshot disks it depends on. 14 (Bad address)

Changing directory/browsing the datastore via CLI/UI shows the below output:

can't cd to /vmfs/volumes/UUID: Bad address

 

Environment

VMware vSphere ESXi 7.x
VMware vSphere ESXi 8.x

 

Cause

 “Bad Address” error may indicate that one or more LUNs, or specific LBAs within them, are inaccessible or inconsistent. In such cases, ESXi may fail when attempting to read or open the affected block regions, resulting in the reported error.

• An output of vmkfstools -Ph -v10 /vmfs/volumes/DATASTORE gives the below results:

Could not open /vmfs/volumes/DATASTORE

Error: Bad address

OBJLIB-LIB: ObjLib cleanup done.

WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0

 

Resolution

1. Engage the storage vendor to restore full and consistent access to the affected LUN, ensuring that all paths and device blocks (LBAs) are healthy and readable.

2. If any ESXi hosts still have stable access to the datastore, attempt to migrate all virtual machines (VMs) off the datastore using Storage vMotion.

Note: Ensure that valid backups of all VMs exist before performing Storage vMotion. The process may fail due to inconsistent addressing, which could require recovery from backup.

3. Once the datastore is fully evacuated, delete and recreate it as a single, clean extent, ensuring it is provisioned correctly before placing workloads back onto it.