Error: "vSphere HA failed to create a configuration vVol for this datastore and will not be able to protect virtual machines on the datastore until the problem is resolved. Error: (vim.fault.InaccessibleDatastore)."
search cancel

Error: "vSphere HA failed to create a configuration vVol for this datastore and will not be able to protect virtual machines on the datastore until the problem is resolved. Error: (vim.fault.InaccessibleDatastore)."

book

Article ID: 395104

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • vSphere HA configuration fails in a cluster and we see a vVOL datastore being inaccessible in the UI and logs indicate the same. 
  • vpxd logs 

2025-04-10T08:42:45.044Z In(166) Hostd[2099115]: [Originator@6876 sub=Libs] 2099115:VVOLLIB : VVolLibIpcToStorageContainerInfo:3231: SC name: <vVOL Datastore Name>_VVol-Container, VP URL: https://######################.9997/vasa, MaxVVolSize: 67108864MB, Unaccessible None.

2025-04-10T08:42:46.298Z In(166) Hostd[2099118]: [Originator@6876 sub=Libs opID=26931f8a-bf-1aa5 sid=5203d1f3 user=vpxuser:#############: Failed to open '/vmfs/devices/vvol/naa.xxxxxxxxxxxxxxxxxxxxxxxxxxx' : Could not find the file (60003) (0x4011).

2025-04-10T11:23:04.105Z Er(163) VVold[2099021]: [Originator@6876 sub=Default OpId=Session] GetContainerAccessibility, No NVMe subsystemNQN found for array: com.hpe.alletra.storage.mp:0x2BDD2:array:0x2BDD2
2025-04-10T11:23:06.926Z Er(163) VVold[9942424]: [Originator@6876 sub=Default OpId=Session] GetContainerAccessibility, No NVMe subsystemNQN found for array: com.hpe.alletra.storage.mp:0x2BDD2:array:0x2BDD2

  • We do not see the protocol endpoint for the storage array

esxcli storage vvol storagecontainer list

VvolFileSystemImpl: No PEs for array (############/com.hpe.alletra.storage.mp:0x2BDD2:array:0x2BDD2)

   StorageContainer Name: ########
   UUID: vvol:##########################################
   Size(MB): 80560128
   Free(MB): 72167424
   Accessible: false
   Default Policy:
   Stretched: No

Environment

7.x, 8.x

Cause

This issue occurs when there is an inaccessible vVOL datastore in the inventory. 

 

Resolution

Fix the storage issue and make the vVol datastore accessible. If the vVol datastore is no longer needed, delete the datastore from the inventory. 

Procedure to delete the vVOL Datastore

  1. Log in to the vCenter UI
  2. Navigate to the Datastores list view.
  3. Right-click the vVol datastore you want to delete > Unmount Datastore > Delete VVol Datastore.
  4. In the Delete VVol Datastore dialogue, click Delete.


Disable HA and then re-enable it if the error occurs after creating a new VVOL.