vmware failed to lock file module diskearly power on failed

I can only find info via google that say 'add your group to this permission and it'll work' I also can't seem to find a reference to where the shell configuration file is on the VCSA. The shell is indeed enabled, and I can access it via root. Now start the Virtual Machine and it will start without any error or warning. Command> shell Failed to read configuration file.Select the Hard Disk 5 and click on the Remove button to remove this LUN from this Virtual Machine. Please disable 'Autoprotect' in the VMs settings (alternatively delete all lines with 'rollingTier' in the.Select the Hard Disk 5 and click on the Manage Path button it will give you the error message “There is no multiparty configuration for this LUN” because this LUN is no more mapped anywhere.Identify the disk from the error log, in my case, it is BACKUPSERVER_8.vmdk which is Hard disk 5.Right-click on the Virtual Machine (VM) and click on the Edit Settings.To remove the above error we need to remove the disk (which was mapped from the SAN) from the VM and after removing the disk VM will start successfully. So VM was giving the disk error for this LUN while we were trying to start the VM.

During some activity on SAN, we unmapped that LUN from VM because that was no more required.

Reason:Ī LUN from SAN was mapped with this VM through RAW Device Mapping for backup of some data. Cannot open the disk ‘/vmfs/volumes/52b66ab4-8c801b45-fd7a-a0d3c10119c0/BACKUPSERVER/BACKUPSERVER_8.vmdk’ or one of the snapshot disks it depends on.19 (No such device)“. When we have not found any solution then we have tried to reboot that VM but it not starting and was showing the error “ Failed to start the virtual machine. One day suddenly Windows Server 2008 R2 stopped working and we were not able to take the console or remote of that VM.

In these Virtual Machines, we have RHEL 5.8, RHEL 6.8, Windows Server 2003, and Windows Server 2008 R2. We have a server in which some Virtual Machines (VM) are running on VMware Esxi 5.5.

Vmware failed to lock file module diskearly power on failed