Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

Resignaturing VMFS3 volumes from the command line in ESXi/ESX (1005751)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 23080Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

This issue occurs if you recently changed the Host Mode setting on an HDS storage array.

VMFS3 volumes are seen as snapshot volumes.

Volumes are disabled or missing unexpectedly.

Datastores are missing unexpectedly.

You recently set the SPC-2 flag on the EMC Symmetrix storage array.

You recently downgraded the Perc 4e/Di firmware and local datastores are now missing.

The vmkernel.log file (located in /var/log/) contains the entry:

vmhba0:0:0:1 may be snapshot

This issue occurs if you recently performed the steps in On ESX Server Systems with Multiple PERC 4 Controllers, LUNs Become Temporarily Inaccessible After Upgrading the PERC 4 Firmware (5966817).

Resolution

Note: This article is specific to ESXi/ESX 3.x, even though the EnableResignature setting works in ESXi/ESX 4.x. For the supported method to handle snapshot LUN in ESX/ESXi 4.x and 5.x, see vSphere handling of LUNs detected as snapshot LUNs (1011387).

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 modified ports/FAs.

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:

Power off all virtual machines on all ESX hosts that are stored on the volume.

Run this 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.

Remove all the virtual machines on that volume from the inventory in the VirtualCenter server.

Warning: Do not delete the virtual machines from disk. Remove them from the inventory.

Log in to each host.

Run this command to verify which HBAs are providing access to the LUN:

# esxcfg-mpath -l | less

To set the ESX host to resignature all datastores detected as snapshots on the next rescan, run the following command:

For ESX:

# echo "1" > /proc/vmware/config/LVM/EnableResignature

For ESXi:

# esxcfg-advcfg -s 1 /LVM/EnableResignature

To rescan the storage and perform the resignature on volumes detected as a snapshot, run the command:

# vmkfstools -V

To disable the resignature flag, run the following command:

Warning: Do not skip this step.

For ESX:

# echo "0" > /proc/vmware/config/LVM/EnableResignature

For ESXi:

# esxcfg-advcfg -s 0 /LVM/EnableResignature

To ensure that the volumes stay mounted after resignaturing is turned off, run the command:

# vmkfstools -V

Reinventory the virtual machines.

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

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

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

Select the folder in which the virtual machines resides.

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

Click Add to Inventory.

Follow the wizard.

Related Information

For related information, see Resignaturing VMFS3 volumes on VMware ESX 3.x via the VMware Infrastructure Client (9453805).

To resignature LUNs on ESX/ESXi 4.0/4.1 for DR purposes:

Run this command and verify if the hosts are seeing the volumes as snapshots:

esxcfg-volume -l

If some of the hosts are seeing the LUNs and others are not, shut down and remove the virtual machines using these LUNs from inventory

Note: Ensure not to remove the virtual machines from the disk.

Run this command to enable resignaturing snapshot volumes on rescan:

esxcfg-advcfg -s 1 /LVM/EnableResignature

Run this command and re-read the volumes:

vmkfstools -V

Run this command and verify that the hosts do not see the volumes as snapshots:

esxcfg-volume -l

Run this command to disable resignaturing snapshot volumes on rescan:

esxcfg-advcfg -s 0 /LVM/EnableResignature

In vCenter Server, refresh datastores on each host that had the issue. for the resignatured datastores, you should see a display similar to:

snap-abc123-name

Rename the datastores as required.

Browse datastores and add virtual machines to the inventory.

vSphere handling of LUNs detected as snapshot LUNs
On ESX Server Systems with Multiple PERC 4 Controllers, LUNs Become Temporarily Inaccessible After Upgrading the PERC 4 Firmware
Resignaturing VMFS3 volumes on VMware ESX 3.x via the VMware Infrastructure Client

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
ESX/ESXi ドライバ モジュールがロードに失敗し、「不正なパラメータ」というエラーが表示される (1038247)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware ESX Server

Related Versions:

VMware ESXi 4.1.x Installable

VMware ESXi 4.0.x Installable

VMware ESXi 3.5.x Installable

VMware ESXi 3.5.x Embedded

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

VMware ESX 4.1.x

VMware ESX 4.0.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant