fault.VmfsAlreadyMounted error when resignaturing a snapshot LUN
search cancel

fault.VmfsAlreadyMounted error when resignaturing a snapshot LUN


Article ID: 321421


Updated On:


VMware vCenter Server VMware vSphere ESXi


When resignaturing a snapshot LUN that is currently active/mounted using the vSphere UI or Resolve API, you experience these symptoms:
  • The resignature fails.
  • In the vpxd.log, you see the error:

    [VpxLRO] -- ERROR task-1640 -- host-9 -- vim.host.DatastoreSystem.resignatureUnresolvedVmfsVolume: vim.fault.VmfsAlreadyMounted::
  • In the vSphere Client event log, you see entries similar to:



VMware vCenter Server 6.0.x
VMware vSphere ESXi 5.5
VMware vSphere ESXi 8.0.x
VMware vCenter Server 5.0.x
VMware vCenter Server 7.0.x
VMware vSphere ESXi 6.7
VMware vSphere ESXi 6.5
VMware vCenter Server 6.7.x
VMware vSphere ESXi 5.0
VMware vSphere ESXi 6.0
VMware vCenter Server 8.0.x
VMware vCenter Server 5.5.x
VMware vSphere ESXi 7.0.x
VMware vCenter Server 6.5.x


This issue occurs when:

  • You attempt to re-signature a snapshot LUN which is already mounted/online. 
  • The hosts in the DR site don't have the identical copies of the same LUNs/volumes .   
This is by design and these restrictions are enforced by the vSphere client UI and the query/resolve API to avoid any chances of modifying the VMFS signature while the volume is actively in use. 


To resolve this issue, perform one or both of these options:

  • Unmount and detach the active/online volume prior to resignaturing the snapshot LUN. 
  • Ensure that the hosts on the DR site have only 1 copy of each snapshot LUN and avoid multiple copies/presentations.  

Additional Information

Once a VMFS backed LUN is detected as a snapshot, there are two options for mounting/interacting with them: 

  •  By force mounting the snapshot LUN, the LUN is enforced to register itself with the existing VMFS signature or UUID reference. 
  •  By resignaturing the snapshot LUN with this option, the volume is resignatured and essentially providing it with a new UUID reference. 

The first option, of force mounting, is to be utilized when the original volume is no longer visible as a datastore. By doing this, the VMs that were part of this datastore remain intact and there would not be any need for re-registering them. 

With the second option, of resignaturing, a new volume is created entirely. This would require the VMs on this datastore to be re-registered once again as the path the *.vmx file now has an updated UUID reference. 

In order to proceed with the resignaturing option, ensure that the volume in question is not already mounted/online on other hosts. It is by design that when a snapshot LUN is mounted to a host, the vCenter Server prevents the re-signature of same LUN.

For more information, see vSphere handling of LUNs detected as snapshot LUNs (1011387)