Datastore or LUN missing after reboot
Article ID: 409405
Updated On:
Products
Issue/Introduction
After a host is rebooted, a once mounted LUN or datastore, is no longer seen by the ESXi host.
Environment
ESXi 7.0
ESXi 8.0
Cause
This can happen if the LUN was presented to a host or cluster that is not ESXi. The LUNs partition table or more could have been overwritten by the different host.
You can also see messages such as this in the vmkernel, vmkwarning or vodb logs.
YYYY-MM-DDT15:08:48.722Z Wa(180) vmkwarning: cpu87:2099471)WARNING: FS3: 636: VMFS volume #######/########-########-####-############ on naa.################################:1 has been detected corrupted
Resolution
If these symptoms are seen, please contact Broadcom support so a metadata check using the vSphere On-disk Metadata Analyzer can be performed.
In certain cases, the LUN is still seen by other hosts and data can be migrated off of it. If that is the case, move all data off and reformat the LUN.
Feedback
