Searching: Power - 134 Results Found

VTrak Other How do I Resignature my LUN in VMware In ESX 4.0
Ken Chou posted this 03 May 2010

How do I Resignature my LUN in VMware

In ESX 4.0

 

Making this type of change on the storage array results in assigning a new LUN ID (UUID or Serial Number) to all LUNs presented via the HBA ports.


VMFS3 metadata identifies the volumes by several properties which include the LUN number and the LUN ID (UUID or Serial Number). Because the LUNs now have new UUIDs, the resulting mismatch with the metadata leads to LVM identifying the volumes as snapshots.

 

You must resignature the VMFS3 volumes to make them visible again.

 

Caution:

  • Before performing the steps in this article:
    • Wait for a maintenance window
    • Make sure all virtual machines are backed up properly
  • Do not deviate from these steps. 

To resignature the VMFS3 volumes from the command line:

  1. Power off all virtual machines on all ESX hosts that are stored on the volume.
  2. Run the following command to re-read the volume on each ESX host:

    # vmkfstools -V

    If this works, the problem is resolved. If this does not work, proceed to step 3.
  3. Remove all of the same virtual machines from the inventory in the VirtualCenter server.

    Warning: Do not delete the virtual machines from disk. Remove them from the inventory.
  4. Log in to each host.
  5. Run the following command to verify which HBAs are providing access to the LUN:

    # esxcfg-mpath -l | less
  6. To set the ESX host to resignature all datastores detected as snapshots on the next rescan, run the following command:

7.       

    • For ESX Classic:

      # echo "1" /proc/vmware/config/LVM/EnableResignature
    • For ESXi:

      # esxcfg-advcfg -s 1 LVM/EnableResignature
  1. To rescan the storage and perform the resignature on volumes detected as a snapshot, run the command:

    # vmkfstools -V
  2. To disable the resignature flag, run the following command:

    Warning:
    Do not skip this step.
    • For ESX Classic:

      # echo "0" /proc/vmware/config/LVM/EnableResignature
    • For ESXi:

      # esxcfg-advcfg -s 0 LVM/EnableResignature
  3. To ensure that the volumes stay mounted after resignaturing is turned off, run the command:

    # vmkfstools -V
  4. Reinventory the virtual machines.

a.       Open VI Client to the VirtualCenter Server. The virtual machines show as inaccessible.

b.      Right-click on the virtual machine and click Remove From Inventory.

c.       Double-click the datastore to bring up the datastore browser.

d.      Select the folder in which the virtual machines resides.

e.       Right-click the virtual machine file (extension .vmx) or template file (extension .vmtx)

f.        Click Add to Inventory.

g.       Follow the wizard.

Legacy Other SmartNAVI is not detecting the DS4600
Ken Chou posted this 20 April 2010

SmartNAVI is not detecting the DS4600.

If you connect the DS4600 to the host system and power it up before installing the SmartNAVI program, the SmartNAVI program will sometimes not detect the DS4600. The following instructions should get the DS4600 recognized in the SmartNAVI program:

1.       Unmount the DS4600 volume from the desktop if you have already configured your volume through the One-Touch button.

2.       Power down the DS4600

3.       Uninstall the SmartNAVI software.

4.       Reboot the host system. This will give us a fresh start to installing the DS4600.

5.       Install the SmartNAVI software.

6.       Startup the SmartNAVI software.

7.       Startup the DS4600. It should now be detected by the SmartNAVI.

You may want to attach the SmartNAVI program to your dock, and set it to start automatically when the host computer starts. If the SmartNAVI program is not running, it will not get status updates from the DS4600. The event log within the SmartNAVI program will not record any new errors from the DS4600 while the SmartNAVI program is inactive.

 

If the DS4600 is still not being detected by the SmartNAVI program, please contact Technical Support to further troubleshoot the issue.

Close