Datastore shows inaccessible state in vCenter
search cancel

Datastore shows inaccessible state in vCenter

book

Article ID: 313878

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:

  • Virtual machines appeared as inaccessible in the vCenter UI.

  • Some VMs showed as running, but access to the web console was not possible.

  • Additionally, browsing files on the datastores was unsuccessful.

Environment

VMware vSphere ESXi(All Versions)

Cause

  • After a PDL happens on a LUN/Volume, all the applications running on that volume need to be closed and reopened so that the LVM/Datastore metadata gets reconfigured for the Volume.
  • In few scenarios where underneath device fails few IOs even after PDL is cleared, LVM metadata won't get updated, and the volume becomes inaccessible.
In var/run/log/vmkernel.log, triggers with "PDL and device is permanently unavailable"
2025-05-02T02:04:49.724Z cpu36:2098136)WARNING: NMP: nmp_PathDetermineFailure:3527: Cmd (0x2a) PDL error (0x5/0x25/0x0) - path vmhba1:C0:T14:L10 device naa.624a9370e84axxxxxxxxxxx - triggering path failover
2025-05-02T02:04:49.724Z cpu36:2098136)NMP: nmp_ThrottleLogForDevice:3867: Cmd 0x2a (0x45d9a53bdfc8, 2102896) to dev "naa.624a9370e84xxxxxxxxxxx" on path "vmhba1:C0:T14:L10" Failed:
2025-05-02T02:04:49.724Z cpu36:2098136)NMP: nmp_ThrottleLogForDevice:3875: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x25 0x0. Act:FAILOVER. cmdId.initiator=0x430d6821f580 CmdSN 0x8000002d
2025-05-02T02:04:50.700Z cpu17:2097624)VMW_SATP_ALUA: satp_alua_issueCommandOnPath:887: Path "vmhba2:C0:T18:L239" (PERM LOSS) command 0x12 failed with status Device is permanently unavailable. H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x25 0x0.
2025-05-02T02:04:50.700Z cpu17:2097624)WARNING: VMW_SATP_ALUA: satp_alua_getTargetPortInfo:160: Could not get page 83 INQUIRY data for path "vmhba2:C0:T18:L239" - Device is permanently unavailable (195887410)
2025-05-02T02:04:50.700Z cpu17:2097624)VMW_SATP_ALUA: satp_alua_issueCommandOnPath:887: Path "vmhba1:C0:T8:L239" (PERM LOSS) command 0x12 failed with status Device is permanently unavailable. H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x25 0x0.
2025-05-02T02:04:50.700Z cpu17:2097624)WARNING: VMW_SATP_ALUA: satp_alua_getTargetPortInfo:160: Could not get page 83 INQUIRY data for path "vmhba2:C0:T18:L239" - Device is in-accessible

In var/run/log/vobd.log there will be an error event with "lost connectivity to storage device"

2026-03-25T04:03:47.400Z: [scsiCorrelator] 19759076159151us:[vob. scsi. scsipath.pathstate.dead] scsiPath vmhbal:CO:T1:L2 changed state from on
2026-03-25T04:03:47.401Z: esx.problem. storage. connectivity. lost] Lost connectivity to storage device naa.600009xxxxxxxxxxxxxxxxx. Path vmhbal:CO:TO:L3 is down. Affected datastores: "VOL_xxxxxxxxxxxxx"
2026-03-25T04:03:47.401Z: [scsiCorrelator] 19758696379034us: [vob.scsi.scsipath.pathstate.dead] scsiPath vmhba0:CO:TO:L2 changed state from on
2026-03-25T04:03:47.413Z: [scsiCorrelator] 19759076171858us: [esx.problem.scsi.device.state.permanentloss] Device: naa.600009xxxxxxxxxxxxxxxxx. has been removed or is permanently inaccessible. Affected datastores (if any): "VOL_xxxxxxxxxxxxx"

Resolution

  • To fix this issue, please perform a storage rescan. For more details, see Performing a rescan of the storage on an ESXi host .
  • If the rescan does not resolve the issue, rebooting the host should restore access to the datastore.
  • A case should be opened with the array vendor to investigate the root cause of the reported PDL (Permanent Device Loss) condition.

Additional Information

Powered by Wolken Software