The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Snapshot LUN detection in ESX 3.x and ESX 4.x (1011385)
How a LUN is detected as a snapshot in ESX 3.0.x
When an ESX 3.x server finds a VMFS-3 LUN, it compares the SCSI_DiskID information returned from the storage array with the SCSI_DiskID information stored in the LVM Header.
If the two IDs do not match, the VMFS-3 volume is not mounted.
A VMFS volume on ESX 3.x can be detected as a snapshot for a number of reasons:
- LUN ID change
- SCSI version supported by array changed (firmware upgrade)
- Identifier type changed – Unit Serial Number vs NAA ID
How a LUN is detected as a snapshot in ESX 3.5.x and ESX 4.x
When trying to determine if a device is a snapshot in ESX 3.5.x and ESX 4.x, the ESX uses a globally unique identifier to identify each LUN, typically the Network Addressing Authority (NAA) ID.
NAA IDs are unique and are persistent across reboots.
There are many different globally unique identifiers. If the LUN does not support any of these globally unique identifiers, ESX falls back to the serial number + LUN ID used in ESX 3.x.
For more information on how to resolve the above issue, see VMFS Volume Can Be Erroneously Recognized as a Snapshot (6482648) or Resignaturing VMFS3 volumes from VMware Infrastructure Client (9453805).
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.