OPERATIONAL DEFECT DATABASE
...
...
A datastore is missing, though you can still see the LUN presented to the hostIn the vmkernel.log file, you see entries similar to: LVM: 8445: Device naa.0012345012345678:1 detected to be a snapshot:LVM: 8445: Device eui.0017380012020364:1 detected to be a snapshot:LVM: 8452: queried disk ID: <type 1, len 17, lun 36, devType 0, scsi 0, h(id) 7683208289187576905>LVM: 8459: on-disk disk ID: <type 1, len 17, lun 17, devType 0, scsi 0, h(id) 7683208289187576905> When forcing a LUN that is formatted as VMFS-5 or VMFS-6 to mount (either with the name or UUID), you see entries similar to: esxcli storage vmfs snapshot mount -l LUN No unresolved VMFS snapshots with volume label 'DEV-LUN' found.esxcli storage vmfs snapshot mount -u UUIDNo unresolved VMFS snapshots with volume UUID '4f1d6367-34a3d2d2-f46b-14feb5cc149a' found. Force mounting a VMFS datastore results in these symptoms: Other hosts in the same datacenter cannot mount that VMFS datastore from vCenter Server.The Resolve VMFS Volumes automatic task, seen in the task list of the vCenter Client, results in the entries similar to: Error: Cannot change the host configuration.Error StackCall "HostStorageSystem.ResolveMultipleUnresolvedVmfsVolumes" for object "storageVolume" on vCenter Server "VC" failed.
This article provides information on how snapshot LUN detection is handled by ESXi 6.x, 7.x and 8.x.
The snapshot LUNs issue occurs when the ESX host does not confirm the identity of the LUN with what it expects to see in the VMFS metadata. This issue occurs after replacing SAN hardware, firmware upgrades, SAN replication, DR tests, and some HBA firmware upgrades.Force mounting a VMFS datastore fails if: Multiple ESXi hosts are managed by the same vCenter Server and these hosts are in the same datacenter.A snapshot LUN containing a VMFS datastore is presented to all these ESXi hosts.One of these ESXi hosts force mounts the VMFS datastore that resides on this snapshot LUN.A second ESXi host is attempting to do an operation at the same time. When one ESXi host force mounts a VMFS datastore residing on a LUN is detected as a snapshot, an object is added to the datacenter grouping in the vCenter Server database to represent that datastore.When a second ESXi host attempts to do the same operation on the same VMFS datastore, the operation fails because an object already exists within the same datacenter grouping in the vCenter Server database.Because an object already exists, vCenter Server does not allow mounting the datastore on any other ESXi host residing in that same datacenter.
Notes: Keeping the existing signature will cause problems in the future, such as preventing the increase of the datastore size, and preventing the datastore from automatically mounting on new hosts, etc. So, "force mounting" (mounting the datastore while keeping the existing signature) is just a temporary step to gain immediate access. After that, please either schedule a maintenance window for the VMs on that datastore and assign the new signature, or migrate the VMs off the datastore so they are not affected by the maintenance.On resignature, in addition to assigning a new UUID, ESXi assigns a modified label (i.e. name) to the datastore. The default format of the new label assigned to the datastore is snap-snapID-oldLabel, where snapID is an integer and oldLabel is the label/name of the original datastore. ESXi 6.x, 7.x, and 8.x vSphere Client Log in to the vSphere Client and navigate to vCenter Home.Click Datastores in the menu on the left.In the Objects tab click the Create a new datastore icon in the top left.Type the datastore name and if required, select the placement location for the datastore.Select VMFS as the datastore type.From the list of storage devices, select the device that has a specific value displayed in the Snapshot Volume column. Note: The value present in the Snapshot Volume column indicates that the device is a copy that contains a copy of an existing VMFS datastore.Under Mount Options, select the desired option (Keep existing, Assign new, Format) for your volume and click Next.Review the datastore configuration information.Click Finish. Command line Connect to the ESXi host with an SSH session and root credentialsTo list the volumes detected as snapshots, run this command: esxcli storage vmfs snapshot list You see output similar to: 49d22e2e-996a0dea-b555-001f2960aed8Volume Name: VMFS_1VMFS UUID: 49d22e2e-996a0dea-b555-001f2960aed8Can mount: trueReason for un-mountability:Can resignature: trueReason for non-resignaturability:Unresolved Extent Count: 1 To (force) mount a snapshot/replica LUN that is persistent across reboots, run this command: esxcli storage vmfs snapshot mount -l label|-u uuid For example: esxcli storage vmfs snapshot mount -l "VMFS_1"esxcli storage vmfs snapshot mount -u "49d22e2e-996a0dea-b555-001f2960aed8" To (force) mount a snapshot/replica LUN that is not persistent across reboots, run this command: esxcli storage vmfs snapshot mount -n -l label|-u uuid For example: esxcli storage vmfs snapshot mount -n -l "VMFS_1" esxcli storage vmfs snapshot mount -n -u "49d22e2e-996a0dea-b555-001f2960aed8" To resignature a snapshot/replica LUN (the volume is mounted immediately after the resignature), run this command: esxcli storage vmfs snapshot resignature -l label|-u uuid For example: esxcli storage vmfs snapshot resignature -l "VMFS_1" esxcli storage vmfs snapshot resignature -u "49d22e2e-996a0dea-b555-001f2960aed8" To mount the volume without performing a resignaturing of that volume (this volume is mounted when the ESX host is rebooted), run this command: esxcfg-volume -M VMFS_UUID|label For example: esxcfg-volume -M "VMFS_1" esxcfg-volume -M "49d22e2e-996a0dea-b555-001f2960aed8" Note: To view the datastores again in vCenter Server, you may have to perform a rescan of the storage adapters on all ESXi hosts that the datastore is presented to or a refresh of the storage view. If you are having trouble identifying the affected datastore, in the vSphere client, check the storage view of another ESXi host that still has the datastore mounted correctly. This will then allow you to correlate VMFS datastore name with NAA LUN identifier.Note: Attempting to resignature an already mounted snapshot LUN fails: see fault.VmfsAlreadyMounted error when resignaturing a snapshot LUN
VMware Skyline Health Diagnostics for vSphere - FAQBest practices for mounting snapshot LUNs There must be no active I/O on the affected datastore(s). Any registered virtual machines on the volume prevent the datastore from being unmounted and the host database location record will be incorrect after the datastore is resignatured and the virtual machine within will not power on. You have two options to ensure no I/O occurs on the datastore: Storage vMotion: Either migrate all virtual machines off the datastore using Storage vMotion (from any and all hosts with) to another datastore by placing datastore into maintenance mode. OR Shutdown and unregister: Shutdown and unregister any virtual machines that reside on the affected datastore. Unmount the datastore on all hosts.Select the LUN with your VMFS volume data on it and add the storage to one host in the cluster with the Assign a New Signature option. Note: The snapshot datastore can be mounted to one host only until it is resignatured.This does not have to be host you have problems mounting it to.Rename the volume if required. By default, the datastore name appends with snap- after the resignature operation. Add any virtual machines from the resignatured datastore back to the inventory and power them on. Virtual machines which primarily reside on a different datastore but partly reside on the resignatured volume (they have one or more disks on the affected datastore) may need to have the virtual disk (vmdk) removed from the virtual machine configuration and re-added from the newly resignatured datastore location. Important notes to keep in mind when force mounting a VMFS volume on an ESXi host: A VMFS datastore is mounted only if it does not collide with an already mounted VMFS datastore that has the same UUID (that is, VMFS signature). In other words, if the original LUN that contains the original VMFS datastore together with its snapshot LUN are both presented to the ESXi host simultaneously, force mounting the VMFS datastore from the snapshot LUN on this same ESXi host is not allowed. In this case, the only way to mount that VMFS datastore from the snapshot LUN is to resignature and choose a new label for that datastore.In a datacenter that has multiple ESXi hosts, a VMFS datastore on a snapshot LUN is force mounted on any one of these hosts. When this datastore is mounted on a given host, that datastore cannot be force mounted on any other host using the vCenter Server user interface. To mount that datastore on other hosts, use the preceding steps.If the datastore will not mount correctly in vCenter Server, retry the mount while directly connected to the ESX host. Other hosts see the volume after the resignature operation. If you do not see the volume after the resignature operation, do a manual rescan from each host(s) as required, see Performing a rescan of the storage on an ESX/ESXi host (1003988). For translated versions of this article, see: Español: Manejo de unidades LUN detectadas como snapshots en ESX/ESXi 4.x (1033094)日本語: ESX および ESXi 4.x のスナップショットとして認識されている LUN の扱いについて (1039100) Tech Support Mode for Emergency SupportUnable to connect to an ESX host using Secure Shell (SSH)Performing a rescan of the storage on an ESX/ESXi hostSnapshot LUN detection in ESX and ESXiUsing Tech Support Mode in ESXi 4.1, ESXi 5.x, and ESXi 6.xManejo de unidades LUN detectadas como snapshots en ESX/ESXi 4.xスナップショット LUN として検出された vSphere の LUN 処理Configuring a diagnostic coredump partition on an ESXi 5.x/6.x hostPersistent mount of a snapshot LUN may not persist across reboots in VMware ESXi 5.0/5.1/5.5vSphere 处理检测为快照 LUN 的 LUNESXi 5.x ホストで LUN の強制マウントに失敗し、次のエラーが表示される： duplicate extents foundVMFS Volume Can Be Erroneously Recognized as a SnapshotResignaturing VMFS3 volumes on VMware ESX 3.x via the VMware Infrastructure Client
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
