Running fdisk -l Fails to Display Local Storage in Some Situations
Details
If gatekeeper LUNs or other special LUNs are presented to the ESX Server host as pseudo-LUNs, and if you then run fdisk -l in the service console, the output might not include details for all the LUNs. This is because fdisk stops when it encounters a pseudo-LUN that does not have partition table information.
Solution
Don't present pseudo-LUNs to the the ESX Server host, either by hiding them at the storage array itself, or by using LUN masking in the VMkernel. If you must present pseudo-LUNs to the ESX Server host, specify disk names explicitly when calling fdisk , for example:
