VMware Communities
cbtom
Contributor
Contributor
Jump to solution

VM restart then errors - cant find vmdk which actually exist

I was working on my VM and just restarted my Debian client. On restart it wont start. 

This is the error I am getting: 

 

 

 

 

 

VMware Workstation cannot find the virtual disk "D:\Virtual Machines\Debian\Debian2022-000002.vmdk". Verify the path is valid and try again.

The system cannot find the file specified

Cannot open the disk 'D:\Virtual Machines\Debian\Debian2022-000002.vmdk' or one of the snapshot disks it depends on.

Module 'Disk' power on failed.

Failed to start the virtual machine.

 

 

If I browse to that directory all the files exist and this one is there. 

 

Reply
0 Kudos
1 Solution

Accepted Solutions
a_p_
Leadership
Leadership
Jump to solution

"Debian2022-000002-s014.vmdk"

is missing.

André

View solution in original post

Reply
0 Kudos
7 Replies
continuum
Immortal
Immortal
Jump to solution

Open

"D:\Virtual Machines\Debian\Debian2022-000002.vmdk"

in a texteditor - it very likely is a 500 byte file.
Check if all slices listed in the textfile are present.
Attach vmware.log to make troubleshoooting easier.
Post list of files in the directory of the VM if you are in a hurry.

 


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
a_p_
Leadership
Leadership
Jump to solution

The mentioned file is most likely only a descriptor file which contains the list of .vmdk files that make up the virtual disk, which in this case is a snapshots. Please verify that all .vmdk files in that list exist, and also the ones from the snapshot's parent .vmdk's.

In doubt, run ls -lisa to list all of the VM's files, and post the results.

In cases like this, users found the missing file(s) in the lost&found folder.

André

Reply
0 Kudos
cbtom
Contributor
Contributor
Jump to solution

The attached descriptor is the 000002.vmdk and the log entries. I confirmed that the files exist all them. Also confirmed the other vmdk for the snapshots and  they all seem to exist as well. 

cbtom_0-1653770065062.png

 

 

Reply
0 Kudos
a_p_
Leadership
Leadership
Jump to solution

"Debian2022-000002-s014.vmdk"

is missing.

André

Reply
0 Kudos
cbtom
Contributor
Contributor
Jump to solution

Oh my, you are right. I counted them twice. 

I wonder where it could have gone. I do have these two

 

cbtom_0-1653770492079.png

 

cbtom_1-1653770509738.png

 

 

Reply
0 Kudos
cbtom
Contributor
Contributor
Jump to solution

I found it in my windows quarantined files and didnt even get an alert on win11. 

Reply
0 Kudos
cbtom
Contributor
Contributor
Jump to solution

Thanks for the help

Reply
0 Kudos