VSAN-Troubleshooting-Reference-Manual

Diagnostics and Troubleshooting Reference Manual – Virtual SAN
capacity is available, including any newly inserted disks claimed by Virtual
SAN.
If the VM Storage Policy has NumberOfFailuresToTolerate=0, the VMDK will
be inaccessible if one of the VMDK components (think one component of a
stripe or a full mirror) exists on the pulled disk. To restore the VMDK, the
same disk has to be placed back in the ESXi host. There is no option to
recover the VMDK.
Expected behaviors – UI view and log entries:
Removal of a disk will result in the following messages similar to the following
appearing in the vmkernel.log:
2014-09-30T09:44:55.312Z cpu20:32849)WARNING: ScsiPath: 7028: Path lost for adapter
vmhba0 target 1 channel 0 pun 0 2014-09-30T09:44:55.312Z cpu22:33441)WARNING:
LSOMCommon: IORETRY_NotifyAPD:1647: Got APD event 1 on 0x410c0285ca90
2014-09-30T09:44:55.312Z cpu20:32849)WARNING: ScsiDevice: 8820: PDL set on VSAN device
path "vmhba0:C0:T1:L0" [...]
2014-09-30T09:44:59.317Z cpu22:33506)WARNING: LSOM: LSOMEventNotify:4581: VSAN device
527cfbf5-ae7a-33f6-78bc-beed2f1730dd has gone offline.
It will also result in the following messages appearing in the vobd.log:
2014-09-30T09:44:59.317Z: [VsanCorrelator] 59865017530us: [vob.vsan.pdl.offline] VSAN
device 527cfbf5-ae7a-33f6-78bc-beed2f1730dd has gone offline.
2014-09-30T09:44:59.317Z: [VsanCorrelator] 59867627549us:
[esx.problem.vob.vsan.pdl.offline] VSAN device 527cfbf5-ae7a-33f6-78bc-beed2f1730dd has
gone offline.
Removal of a disk will trigger an event in the vSphere Web Client, under ESX host ->
Monitor -> Events. You will find a "VSAN device XYZ has gone offline" similar to
what was observed in vobd.log:
V M W A R E S T O R A G E B U D O C U M E N T A T I O N / 63