Cannot increase DataStore from ESXI vSphere Client

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• Datastore seen as inaccessible in vCenter UI.

• Unable to expand the datastore from ESXi host and vCenter server.

• Logs on ESXi host /var/run/log/vmkernel.log, /var/run/log/vmkwarning.log and /var/run/log/vobd.log shows corrupted messages.

2025-04-14T01:05:29.002Z: Successfully sent event(esx.problem.vmfs.resource.corruptondisk) after 4 failures
2025-04-14T01:05:29.002Z: Successfully sent event(esx.problem.vmfs.resource.corruptondisk) after 4 failures

Environment

VMware vSphere ESXi 7.x

Cause

• The issue is seen where there is VMFS corruption (heartbeat or metadata) observed. The events in the logs would show as below.

• When checking /var/run/log/vmkernel.log, you will see the below events.

2025-04-14T01:32:55.830Z cpu2:2098594) WARNING: HBX: 751: 'Datastore': HB at offset 16053357117517168998 - Volume 5bb680f0-8fd9b1de-ecca-###### may be damaged on disk. Corrupt heartbeat detected:
2025-04-14T01:32:55.830Z cpu2:2098594) WARNING: FS3: 608: VMFS volume Datastore/5bb680f0-8fd9b1de-ecca-0017a47738c8 on naa.6#############51:1 has been detected corrupted

• Unable to query the partition details: Partition table showing as unknown.

[root@esxi :~ ] partedutil getptbl /vmis/devices/disks/naa.####################
unknown
534698 255 63 8589934592

• LVM magic not found at expected offset, while running voma on the affected devices.

[root@esxi:~ ] voma -m vmfs -f check -d /vmfs/devices/disks/naa.#####6487
Running VMFS Checker version 2.1 in check mode
Initializing LVM metadata, Basic Checks will be done
Initializing LVM metadata ..-
IVM magic not found at expected Offset.
It might take long time to search in rest of the disk.

VMware ESXi Question:
Do you want to continue (Y/N) ?

0) Yes
1)

Select a number from 0-1: 0

Resolution

Refer the below document for the assistane on this issue.

VMs show inaccessible and shared datastores missing from ESXi hosts.

Additional Information