Newly added datastore shows inaccessible while VASA Provider online

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• Newly added VVOL datastore shows inaccessible with 0 Bytes Capacity in vCenter.
  
  
• VASA Providers status is Online (under vCenter > Configure > Storage Providers).
  
  To check from CLI, run the command from ESXi host -
  
  # localcli storage vvol vasaprovider list
  

  <VASA Provider Name>-ct0:
   VP Name: <VASA Provider Name>-ct0
   URL: https://<VP IP>:8084
   Status: Online
   VASA Version: 8
   Max Concurrent Operations: 5
   Arrays:
         Arrays:
            ArrayId: com.purestorage:5396b343-4110-413e-87fc-############
            Is Active: true
            Priority: 210

     VirtualHost:
      VirtualHost:
         IP: <VP IP>
         Port: 0
         SNI: vasa-vhost-1c08627a-3911-40b5-a835-############.purestorage.com
   API Batch Size:
      APIBatchSize:
         BindVirtualVolume: 4
         Default: 4
         GetTaskUpdateEx: 4
         QueryVirtualVolumeInfo: 4
         SnapshotVirtualVolume: 4
         SpaceStatsVirtualVolume: 4
         UnbindVirtualVolume: 4
         UpdateVirtualVolumeMetdataEx: 4

  
  
  
• Unable to storage vMotion VM to VVOL datastore.
  
  Compatibility Issues:  

  Unable to access the virtual machine configuration: Unable to access file [VVOL Datastore]

  Unable to access virtual disk 'Hard disk 1' from the host. Either the host is disconnected from the datastore or has insufficient privilege. Details: Unable to access file [VVOL Datastore]



Environment

VMware vSphere ESXi 

VMware vCenter Server 

Cause

• VVOL Datastore is in "Not connected" status on the ESXi host.
  
  Steps: Select Datastore > Configure > Connectivity with Hosts.
  
  
• Presentation of Protocol Endpoint LUN to ESXi cluster is missing from the backend Storage Array.
  
  
• In "/var/run/log/vvold.log" on ESXi host, below log entries will be seen -
  
  2025-09-08T06:07:05.012Z Wa(164) VVold[2103298]: [Originator@6876 sub=Default IpcCtx=2099410-38] ProtocolEndpoint::GetPEInfo PE info (
2025-09-08T06:07:05.012Z Wa(164) VVold[2103278]: --> SCSI PE, ID (host: Not yet initialized, vasa: naa.####################################) (inaccessible, not configured))
  
  
• Output of the following command reflects the same state for the PE.
  
  # localcli storage vvol protocolendpoint list

naa.####################################:
   Host Id:
   Array Id: com.purestorage:5396b343-4110-413e-87fc-############
   Type: SCSI
   Accessible: false
   Configured: false
   Lun Id: naa.####################################
   Remote Host:
   Remote Share:
   NFS4x Transport IPs:
   Server Scope:
   Server Major:
   Auth:
   User:
   Storage Containers: 7ae505cf-44b6-c39e-fd77-############

Resolution

• Involve Storage vendor to assist in mapping Host Group (ESXi cluster) to Protocol Endpoint (PE LUN).
  
  
• Once done, run 'Rescan' on ESXi cluster to successfully mount VVOL datastore.