Cannot access the LUN on EMC Clariion storage as it is marked as a deactivated snapshot
search cancel

Cannot access the LUN on EMC Clariion storage as it is marked as a deactivated snapshot

book

Article ID: 341056

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
If you are using a EMC CLARiiON storage array and your ESX host is rebooted, you may experience these symptoms:
  • You cannot access LUNs
  • The LUNS are marked as deactivates snapshots
  • All affected LUNs show up in the multipath output:
    • VMFS-3 datastores do not mount.
    • RDM LUNs are inaccessible to the guest operating system they are presented to. They are reported as Unallocated in the computer management view.
  • In the vmkernel or messages log file you see messages similar to the following for each LUN experiencing this issue:

    In ESX 3.5:

    Aug 1 03:12:53 esx vmkernel: 10:19:07:07.881 cpu3:1034) SCSI: 8043: vmhba1:0:6:0 status = 2/0 0x5 0x25 0x1
    Aug 1 03:12:53 esx vmkernel: 10:19:07:07.881 cpu3:1034) SCSI: 8120: vmhba1:0:6:0 is a deactivated snapshot.
    Aug 1 03:12:53 esx vmkernel: 10:19:07:07.881 cpu3:1034) WARNING: SCSI: 5637: status SCSI LUN is in snapshot state, rstatus 0xc0de00 for vmhba1:0:6. residual R 999, CR 80, ER 3
    Aug 1 03:12:53 esx vmkernel: 10:19:07:07.881 cpu3:1034) SCSI: 6624: Device vmhba1:0:6 is a deactivated snapshot

    In ESX 4.0:

    Sep 24 05:05:07 system-name vmkernel: 0:00:01:25.953 cpu1:4097)NMP:
    nmp_CompleteCommandForPath: Command <###>
    (0x4100070dfa40) to NMP device "naa.60060160d56e1b000e696c75b9a8de11"
    failed on physical path "vmhba1:C0:T0:L22" H:0x0
    D:0x2 P:0x0 Valid sense data: 0x5 0x25 0x1.

    In ESXi 5.x:

    2013-03-27T15:03:04.905Z cpu3:2674)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x28 (0x41240075a480, 2095893) to dev "naa.6006016040c12200c69e241b9960e211" on path "vmhba3:C0:T1:L14" Failed: H:0x0 D:0x2 P:0x2 Possible sense data: 0x5 0x25 0x1. Act:NONE

    The SCSI sense code returned in all of these examples can be translated to:

    Device D:0x2 = Check Condition
    Plugin P:0x2 = VMK_SCSI_PLUGIN_SNAPSHOT
    Sense 0x5 = Illegal Request
    ASC/ASQ = 25/01 = LOGICAL UNIT NOT SUPPORTED - Command was directed to an un-activated snapshot

    For more information on SCSI sense codes see: Understanding SCSI host-side NMP errors/conditions in ESX 4.x and ESXi 5.0 (1029039).

  • The option LVM.DisallowSnapshotLun is set to 1 (the default). Changing it to 0 and performing a rescan does not return visibility to the content of the LUNs.

    For more information, see     VMFS Volume Can Be Erroneously Recognized as a Snapshot (6482648).
  • The Navisphere manager reports that there are snapshots sessions of a source LUN in place and some of them are currently inactive.
  • Those inactive sessions match the UUID of the missing data stores/RDMs.
    • In ESX 3.5, you can find these at /proc/vmware/scsi/vmhba1/X:Y .
    • In ESX 4.0 and above, run this command:

      esxcfg-scsidevs -l


Environment

VMware ESX Server 2.5.x
VMware ESX 4.1.x
VMware ESX 4.0.x
VMware ESXi 4.1.x Embedded
VMware ESX Server 3.0.x
VMware ESX Server 3.5.x
VMware ESXi 4.0.x Installable
VMware ESXi 3.5.x Installable
VMware vSphere ESXi 5.1
VMware ESXi 4.1.x Installable
VMware vSphere ESXi 5.0
VMware ESXi 4.0.x Embedded
VMware ESXi 3.5.x Embedded

Resolution

To access a LUN that is marked as a deactivated snapshot:

  1. Go to the Navisphere Manager and activate the inactive SnapView sessions. Wait until the SnapView reports those sessions as Active.
  2. Remove the RDM from the Windows virtual machines.
  3. Perform a rescan on the ESX host.
  4. Add the RDM back to the virtual machines.
  5. Power on the virtual machine.
  6. Perform a rescan form the Computer management view, if necessary. The RDMs come up as available and NFTS formatted. Full data access. For more information, see http://www.vmware.com/pdf/clariion_wp_eng.pdf.


Additional Information

Powered by Wolken Software