Unable to Access File Since It Is Locked Consolidate

Consistently while destroying reviews or cementing circles of virtual machines running on VMWare ESXi has. I see the “Unsuitable to get to a record since it is locked” error. This consistent issue is related to errors in VM support programming (I ran over the issue in Veeam, HPE/Micro Focus Data Protector, Veritas.)

If the review of the virtual plate is locked. “Unable to Access File Since It Is Locked Consolidate”, you won’t have the choice to harden circles (when you see the goof ‘Virtual machine circles association is required). Move a circle to one more data store using Storage vMotion back up a VM or delete the current portrayal.

Sometimes you can’t turn on a locked virtual machine. “Unable to Access File Since It Is Locked Consolidate” Removing portrayals or consolidating plates of the virtual machines often triggers the “Inadequate to get to an archive since it is locked”. Error on VMWare ESXi has. As a piece of our Server Running Services.

Around here at ARZHOST, “Unable to Access File Since It Is Locked Consolidate” we help our Customers with fixing VMWare-related mistakes reliably. Permit us today to discuss the expected causes and fixes for this error.

What is VMWare Error: Unable to get to a record since it is locked?

While removing a review or consolidating plates of virtual machines running on VMWare ESXi has. It regularly triggers the misstep message “Inadequate to get to a record since it is locked”.

Unable to Access File Since It Is Locked Consolidate” A typical misstep message may look like this:

  • Ill-suited to get to the record since it is locked.
  • An error occurred while setting plates: no less than one circle is involved.

Ordinary clarifications behind this error include:

  1. Filled up virtual machine contains a couple of records with names showing that they are being utilized by other ESXi has.
  2. The maintenance meeting bombs right after adding virtual plates to the maintenance mechanical assembly.

VMware Snapshot Consolidation screw up: Unable to get to the record since it is locked.

Directly following removing representations on a VM either by deleting a particular review or picking “Delete All” sneak peeks. You may see the going with reprobation for the VM. “Unable to Access File Since It Is Locked Consolidate”, communicating that plate mix is required.

“Virtual machine plates mix is required”

This can happen when a see has been eradicated from the web console yet the principal circle reports in the VM coordinator exist. This issue can routinely happen when a virtual machine support course of action makes a lock on a VMDK and fails to adequately convey it.

You can have a go at joining the Virtual Machine plate archives from Consolidate decision under Snapshot Menu. Exactly when I started the Consolidate communication. It got back with an Unable to get to the record since it is locked screw up.

During this stage – SSH into the ESXi have and on the off chance that you don’t realize which circle might be secured you can follow it from the hostd.log report (tail – f/var/log/hostd.log)

“Unable to Access File Since It Is Locked Consolidate”, Then again you can run the under request against all the virtual machine circle records.

  • vmkfstools - D/vmfs/volumes/your volume/your/yourlockedVM.vmdk

Directly following running the request we could see a single area for “RO Owner” which had the lock and the MAC address of the ESXi which has the lock on the VMDK record.

“Unable to Access File Since It Is Locked Consolidate”, the Ensuing stage is to notice the ESXi have in your gathering which is holding up the virtual machine plate.

At the point when we attest the ESXi have we can place the host in upkeep mode, DRS will vMotion all VMs to another host in the pack and restart the host organization on the host using the underneath request.

  • /, etc/init.d/hostd restart

“Unable to Access File Since It Is Locked Consolidate”, Once the hosted organization has been restarted play out a Snapshot – > Consolidate on the VM and it should complete adequately.



People Frequently Ask

Question # 1: Has failed been unable to access the file since it is locked?

Answer: The most often the “Unable to access file since it is locked” error appears when: Some files of a powered-on virtual machine contain tags indicating that they are locked by other ESXi hosts; When virtual disks are added to the backup appliance and the backup session fails.

Question # 2: How do I manually consolidate virtual machines?

Answer: Right-click any of the virtual machines and click Snapshot Manager/Manage snapshots, it would show “Needs Consolidation/Delete Snapshots”. Note: A Configuration Issue warning is also displayed in the Summary tab of the virtual machine indicating that virtual machine disk consolidation is needed.

Question # 3: How do I release a locked file in VMware?

Answer: To delete the .lck-xxxx file:

  1. Ensure the virtual machine is powered off
  2. Connect to the ESXi/ESX host using Secure Shell (SSH)
  3. Go to the virtual machine folder, run the command
  4. List all files including the hidden files, run the command
  5. Remove the lock file, run the command
  6. Power on the virtual machine

Read More—-

Question # 4: How do I unlock a VMware virtual machine?

Answer: On a physical computer using the VMware View access, if the screen says “Press CTRL + ALT + DELETE to unlock this computer,” and the virtual desktop toolbar is visible at the top of the screen, click “Send Ctrl-Alt-Delete” on the virtual desktop toolbar instead of pressing those keys.

Question # 5: What is.LCK file in VMware?

Answer: lck-xxx file located in the virtual machine folder holds a lock on the vmdk file. When an ESXi/ESX host accesses a virtual machine disk file on an NFS-based datastore a . lck-xxx lock file is generated in the same directory as the disk file. This file prevents other ESXi/ESX hosts from accessing the virtual disk file.



How to fix VMWare Error: Unable to get to a record since it is locked?

To fix this mistake, we truly need to track down the wellspring of a lock and transport it. For this, “Unable to Access File Since It Is Locked Consolidate”, the fundamental development is to perceive the locked records.

1: In any case, using an SSH client, partner with the ESXi have for the issue VM.

2: By and by, go to the list with the virtual machine records:

  • collection/vmfs/volumes/VMFS_DATASTORE_NAME/LOCKED_VM

3: Quest for hardening and record getting errors vmware.log:

  • cat vmware.log | grep lock

The log will contain errors like:

  • VigorSnapshotManagerConsolidateCallback: snapshot Err = Failed to lock the record (5:4008)
  • 2020-09-09T05:07:11.432Z| vmx| I125: DISK: Cannot open circle "/vmfs/volumes/5121c3ff-2303a3a-33bb-12345678221/mun-web01/mun-web01_1-000002.vmdk": Failed to lock the record (16392).
  • 2020-09-09T05:07:11.432Z| Worker#1| I125: DISKLIB-LIB: Failed to open '/vmfs/volumes/5121c3ff-2303a3a-33bb-12345678221/mun-web01/mun-web01-000002.vmdk' with standards 0xa Failed to lock the record (16392).
  • 2020-09-09T05:07:11.432Z| Worker#1| I125: DISK: Cannot open plate "/vmfs/volumes/5121c3ff-2303a3a-33bb-12345678221/mun-web01/mun-web01-000002.vmdk": Failed to lock the record (16392).

4: 2020-09-09T05:07:11.432Z| vmx| I125: [msg. fileio. lock] Failed to lock the report

5: Here, the report mun-web01_1-000002.vmdk is locked. “Unable to Access File Since It Is Locked Consolidate” Use the request under to show the current portrayal chain starting with the foreordained one to a level circle:

  • vmkfstools - qv10 mun-web01_1-000002.vmdk
  • Then, get the information about the review and its owner (RO owner):
  • vmkfstools - D mun-web01-000001-delta. vmdk
  • Lock [type 10c000021 offset 242835456 v 856, hb offset 3153920
  • gen 3, mode 1, owner 5cbac61a-4b6e32b7-0480-d06726ae7900 mtime 5199410
  • num 0 gblnum 0 gblgen 0 gblbrk 0]
  • RO Owner [0] HB Offset 3153920 5cbac61a-4b6e32b7-0480-d06726ae7900

6: Add <4, 532, 83>, gen 859, joins 1, type reg, standards 0, uid 0, gid 0, mode 600

The RO Owner line shows the MAC address of the ESXi have network connector that locked the review report. “Unable to Access File Since It Is Locked Consolidate” Moreover, note the Mode regard:

  • mode 1 – a read/make lock (for example, of a turned-on VM)
  • mode 2 – virtual circle locked by the support application.

As of now, to find an ESXi server from the MAC address obtained. “Unable to Access File Since It Is Locked Consolidate” we can use the going with Powerlift orders:

  • Import-Module VMware.VimAutomation. Core – Error Action Silently Continue
  • partner server mun-center
  • Get-Vmhosts | Get-VMHostNetworkAdapter | Where-Object {$_. Mac-like “d0:67:26:ae: 79:00”} | Format-List – Property *

“Unable to Access File Since It Is Locked Consolidate” will show the ESXi hostname in the Vmhosts field. Further, we can show the ARP table clearly from the ESXi have and get IP and MAC areas of any leftover ESXi servers in the Kernel association:

  • excel network IP neighbor list

To open a VM report, just restart the ESXi have we found. In case we can’t restart the host, we can restart the Management Agent (hosted) in the Maintenance Mode from the host’s SSH console:

  • sh restart

Then, “Unable to Access File Since It Is Locked Consolidate” effort to join plates or delete a VM picture again.

Conclusion

In this way, restarting the ESXi host or Management Agent can help with fixing. “Unable to get to a record since it is locked” error. Today, “Unable to Access File Since It Is Locked Consolidate”. We saw how our Hosting Expert Planners fix this error.

Share:

70%OFF

Flash Sale

Hurry Up! Offer ends in
02 days
20 hrs
47 mins
17 secs
Buy Now