VMware Cloud Community
Ale666
Contributor
Contributor

.vmdk big problem! vmware phone support not find solution

hi, every two weeks I have this problem on different VDI machines. to solve the problem I have to restart the hosts and reconfigure the virtual machine. I've already change a backup system.

Task Details:

Name:powerOn
Status:File system specific implementation of LookupAndOpen[file] failed
Description:Powering on the new Virtual Machine
Start Time:Feb 23, 2018 12:24:21 PM
Completed Time:Feb 23, 2018 12:24:26 PM
State:error
Error Stack:

An error was received from the ESX host while powering on VM VDI3D04.

Failed to start the virtual machine.

Module 'Disk' power on failed.

Cannot open the disk '/vmfs/volumes/59a81884-3ee744fa-1b84-9cdc716fb958/VDI3D04/VDI3D04-000002.vmdk' or one of the snapshot disks it depends on.

Failed to lock the file

File system specific implementation of LookupAndOpen[file] failed

File system specific implementation of LookupAndOpen[file] failed

File system specific implementation of LookupAndOpen[file] failed

File system specific implementation of LookupAndOpen[file] failed

File system specific implementation of LookupAndOpen[file] failed

File system specific implementation of LookupAndOpen[file] failed

File system specific implementation of LookupAndOpen[file] failed

File system specific implementation of LookupAndOpen[file] failed

File system specific implementation of LookupAndOpen[file] failed

File system specific implementation of LookupAndOpen[file] failed

File system specific implementation of LookupAndOpen[file] failed

Additional Task Details:
VC Build:4602587
Error Type:GenericVmConfigFault
Task Id:Task
Cancelable:true
Canceled:true
Description Id:VirtualMachine.powerOn
Event Chain Id:288913
Reply
0 Kudos
3 Replies
lpapaleo
Contributor
Contributor

Maybe something is going wrong with your backup software?

It doesn't delete correctly snapshot?

Luca

Reply
0 Kudos
Ale666
Contributor
Contributor

it's not the backup's fault. I tried with two different systems.

Reply
0 Kudos
a_p_
Leadership
Leadership

According to the build number you posted, you're on the GA version of vSphere 6.5!?

Not sure what this is related (https://kb.vmware.com/s/article/2152006), but it may be worth considering updating/patching your environment.

André

Reply
0 Kudos