VMFS datastore shows 0 bytes. Cannot change the host configuration. Failed to update disk partitions for /vmfs/devices/disks/naa.xxxx

Products

• VMware vSphere ESXi

Issue/Introduction

• When running the esxcli storage filesystem list command, the "Mounted" status shows as false and both Size and Free fields display as 0 for certain datastores
  
  Mount Point                                                                      Volume Name                                 UUID                                                      Mounted  Type             Size           Free
  -------------------------------------------------                             ------------------------------------------  -----------------------------------                          -------      ------             -------------  -------------
                                                                                                <Datastore name>             ########-########-####-############    false        VMFS-6              0              0
                                                                                                <Datastore name>             ########-########-####-############    false        VMFS-6              0              0
  /vmfs/volumes/########-########-####-############  <Datastore name>             ########-########-####-############     true         VMFS-6   107105746944   100403249152
  
  
• Rebooting the host does not resolve the issue
  
  
• When attempting to mount the datastore via vCenter, an error is encountered: 'An error occurred during host configuration'. 'Failed to update disk partitions for /vmfs/devices/disks/naa.xxxx'
  
  
• When attempting to mount the datastore from Host Client, the task completes successfully, but the mount status remains unchanged
  

 

Environment

VMware vSphere Esxi 7.x

VMware vSphere Esxi 8.x

Cause

• The issue occurs because the LUN from the storage array is presented in read-only mode. This prevents the datastore from properly mounting and reporting the correct size and free space
  
  
• In vmkernel logs, the following entries are observed:
  YYYY-MM-DDTHH:MM:SS cpu#:#######)LVM: 16104: Failed to open device naa.########################:1 : Read only
  YYYY-MM-DDTHH:MM:SS cpu#:#######)ScsiDeviceIO: 4176: Cmd(0x45b901efc948) 0x89, CmdSN 0x4 from world ####### to dev "naa.########################" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x7 0x27 0xc7
  YYYY-MM-DDTHH:MM:SS cpu#:#######)LVM: 16104: Failed to open device naa.########################:1 : Read only
  YYYY-MM-DDTHH:MM:SS cpu#:#######)ScsiDeviceIO: 4176: Cmd(0x45b901f2a848) 0x89, CmdSN 0x4 from world ####### to dev "naa.########################" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x7 0x27 0xc7
  
  Sense Key = 0x7 = DATA PROTECT
  0xc7 is vendor-specific, but typically when paired with 0x27 it implies write operations are blocked

Resolution

• Change the LUN presentation to read-write mode from the storage array, instead of read-only
  
  
• Contact your storage vendor for further support with LUN configuration