Knowledge Base
The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

|
Firmware upgrade on the storage array causes all LUNs to be detected as snapshots (1006756)
Symptoms
- All LUNs are detected as snapshots after upgrading the EMC Celerra from DART 5.5 to DART 5.6
-
Cannot access the datastore
-
Accessing the datastore fails
Resolution
The upgrade of the DART from 5.5 to 5.6 causes a fundamental change to how the array reports its LUNs to the ESX host.
With DART 5.5, Code Page 0x83 is present but does not correctly implement NAA. Therefore, an ESX host sets the LUN LVM header type to 1 and uses the LUN UUID as the unique identifier.
For example:
<date> <hostname> vmkernel: 0:00:01:51.444 cpu2:1035)LVM: 5583: on-disk disk ID: < type 1, len 44, lun 2, devType 0, scsi 6, h(id) 2658008255134635654>
DART 5.6 correctly implements Code Page 0x83, so the ESX host changes the LUN LVM header type to 2 and uses the NAA as the unique identifier.
For example:
<date> <hostname> vmkernel: 0:00:01:51.444 cpu2:1035)LVM: 5576: queried disk ID: < type 2, len 22, lun 2, devType 0, scsi 6, h(id) 1037829541695267663>
The identifier and LVM type are different from the values saved in the meta data of the LUN, therefore it is marked as a snapshot.
To regain access to the datastore, you must perform one of the following:
-
Resignature the LUNs: http://kb.vmware.com/kb/9453805
-
Instruct the ESX hosts to allow the datastore to mount even if the LUN is detected as a snapshot: http://kb.vmware.com/kb/6482648
Note: Review the associated articles for disallowing snapshot LUNs and Resignaturing carefully. If you are not familiar with these procedures and the possible side effects, contact VMWare Technical Support for assistance.
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.
Actions
KB:
- Updated:
- Categories:
- Languages:
- Product Family:
- Product(s):
- Product Version(s):

