Skip to main content


Failed to lock the file - Continue...

In our day to day operational activity into the vCenter we usually encounter with issue, like unable to power on the VM. VM failed to lock the file or file has been locked. To resolve the issue, I have some very usefull command which you can execute to immediatly idently where the .vmdk is being locked. As most of you know that vmkfstools -D is used to identify the lock on the .vmdk  where its gives the mac address of the VM or Host where the lock exist and we can identify the lock from Esxcli. ie (vmkfstools -D /vmfs/volumes/abcd.vmdk) Apart from this there is one beautiful command which we can use to identify the lock on the .vmdk. The command to identify the lock is "vmkfsfilelockinfo -p (location of .vmdk) vmfsfilelockinfo -p (/vmfs/volumes….) You see ouput similar to: vmfsflelockinfo Version 1.0 Looking for lock owners on "VM1_1-000001-delta.vmdk" "VM1_1-000001-delta.vmdk" is locked in Exclusive mode by host having mac address

Unable to poweron the VM. (Failed to lock the file)

I have encountered may issues like where after some upgrade or migration we were unable to power on the VM. Figure 1 An error was received from the ESX host while powering on VM HSSVSQL01. Failed to start the virtual machine. Cannot open the disk '/vmfs/volumes/578d835c-18b2c97a-9b0d-0025b5f13920/SAMPLE1_cloud/000000.vmdk' or one of the snapshot disks it depends on. Failed to lock the file In above Figure:1, where while powering on the VM, its prompt for an error. Well, there are several reason for where the VM unable to poweron and you can find many article on this. Here in this article we will discuss to resolve this issue. Please use below step to resolve the disk lock issue  C hecked that VM is running on snapshot if its getting error " VM Consolidation required". Checked the snapshot manager if its showing any snapshot. If yes, try to delete the  snapshot. Verified the same from Esxi cl

Installing vCenter Appliance 6.5

vCenter appliance 6.5 is one of the latest & stable release of vCenter . vSphere 6.5 adds an X-Large deployment size, the update manager and a fully supported migration assistant to the appliance. So it’s time to migrate your Windows based vCenters to appliance with vSphere 6.5. vSphere 6.5 is fully dependent on webclient. So no more vSphere client or C# client. VCSA 6.5 Enhancements Supports up to 2000 ESXi Hosts and 35.000 Virtual Machines Guided Installer (Interactive Installer, instead of OVF Template) Robust deployment (Separate Deployment and Configuration to prevent failed deployments Migration Assistant (Migrate vCenter Server 5.5 or 6.0 for Windows to vCenter Server Appliance) Native High Availability VMware Update Manager Built-In Backup+Restore Improved Appliance Management HTML5-based vSphere Client Photon OS (Replaces SUSE Enterprise 11) Compatibility  To view the compatibility of Esxi,

Unable to join VCSA to Domain

Issue: Cannot join a VMware vCenter Server Appliance (VCSA) to an Active Directory domai n While trying to connect to domain from VAMI page of VCSA, getting below error. Error: Invalid Active Directory domain. T o resolve this issue to join the VCSA to Active Directory domain, we can use domainjoin-cli join command Example: To join VCSA to Active Directory domain please follow below process Login to VCSA from SSH 2     Cd /opt/likewise/bin 3     Enter below domainjoin-cli command to join VCSA from command line ./domainjoin-cli join domain-name username password 4     Verify by login to VAMI page of VCSA about the Active directory connectivity by clicking Authentication tab. 5     You will see Active Directory Enabled Check box enabled. Happy Sharing

Issue: Operating System not found

                    Yesterday, I was working into my vsphere Lab where I have deployed one virtual machine into the environment. After deployment virtual machine was working perfectly fine. After some time, I have added 2 huge hdd of size 800 GB using PVSCSI. Once I added the hdd into the VM, and after accepting the change, I tried to open the console and found vm has rebooted and stuck at "Operating System not found" That’s look wired, as I have just added the hdd online and suddenly it rebooted and stuck at this stage. To troubleshoot this issue I tried to gracefully shutdown the VM and tried to bring online in hope, it will detect the changes, but again it stuck at same level "Operating System not found" I checked my OS drive which is  created with the LSI SCSI controller, and the 2 new hdd I created with PVSCSI controller. Here is what the problem exists!!!!! Basically, When the virtual machine is created with the LSI SCSI controller,