Missing vmdk file but the file is in the directory

[hstony]

Hi all,

Would like to seek advice on the issue that I have today on vmware workstation pro 16. Was still working fine yesterday night, and just when I wanted to start up, it throws me an error::

"File not found: C:\Users\ths46\OneDrive\Desktop\Kali\kaliVM\kali-linux-2021.3-vmware-amd64.vmwarevm\Kali-Linux-2021.3-vmware-amd64-000016.vmdk

This file is required to power on this virtual machine. If this file was moved, specify the new location."

I browse to my folder directory, and saw that the000016.vmdk file is still there. So after browse, select the folder location, it then throws me another error::

"

The parent of this virtual disk could not be opened

Cannot open the disk 'C:\Users\ths46\OneDrive\Desktop\Kali\kaliVM\kali-linux-2021.3-vmware-amd64.vmwarevm\Kali-Linux-2021.3-vmware-amd64-000018.vmdk' or one of the snapshot disks it depends on.

Module 'Disk' power on failed.

Failed to start the virtual machine."

Any advise is really greatly appreciated. Thanks.

[hstony]

to add on, I tried reverting to the previous snapshot, and the error states:: "An error occurred while reverting to a snapshot: The system cannot find the file specified.

[bluefirestorm]

I don't have any specific advice to fix the problem but I do have an advice to AVOID such a problem.

It appears the VM is stored on OneDrive. It is best to store the VM on local storage on your PC/laptop and not be syncing with some cloud-based storage.

[a_p_]

By default, virtual disks, and snapshots consist of a descriptor .vmdk file plus a number of data .vmdk files. The required data files are listed in the descriptor file. Please check if all data files are present.
If files are missing, post a complete file listing (e.g. dir *.*) to find out what can be done.

Hint: I've seen cases where A/V applications detected single .vmdk files as infected, and quarantined them. That's why I usually exclude *.vm* files from being scanned.

André

[hstony]

Thank you so much for the prompt response!!

I open the vmdk file using notepad, and the following was observed::
"

# Disk DescriptorFile
version=1
encoding="windows-1252"
CID=ea5ff782
parentCID=ffffffff
createType="twoGbMaxExtentSparse"

# Extent description
RW 8323072 SPARSE "Kali-Linux-2021.3-vmware-amd64-s001.vmdk"
RW 8323072 SPARSE "Kali-Linux-2021.3-vmware-amd64-s002.vmdk"
RW 8323072 SPARSE "Kali-Linux-2021.3-vmware-amd64-s003.vmdk"
RW 8323072 SPARSE "Kali-Linux-2021.3-vmware-amd64-s004.vmdk"
RW 8323072 SPARSE "Kali-Linux-2021.3-vmware-amd64-s005.vmdk"
RW 8323072 SPARSE "Kali-Linux-2021.3-vmware-amd64-s006.vmdk"
RW 8323072 SPARSE "Kali-Linux-2021.3-vmware-amd64-s007.vmdk"
RW 8323072 SPARSE "Kali-Linux-2021.3-vmware-amd64-s008.vmdk"
RW 8323072 SPARSE "Kali-Linux-2021.3-vmware-amd64-s009.vmdk"
RW 8323072 SPARSE "Kali-Linux-2021.3-vmware-amd64-s010.vmdk"
RW 8323072 SPARSE "Kali-Linux-2021.3-vmware-amd64-s011.vmdk"
RW 8323072 SPARSE "Kali-Linux-2021.3-vmware-amd64-s012.vmdk"
RW 8323072 SPARSE "Kali-Linux-2021.3-vmware-amd64-s013.vmdk"
RW 8323072 SPARSE "Kali-Linux-2021.3-vmware-amd64-s014.vmdk"
RW 8323072 SPARSE "Kali-Linux-2021.3-vmware-amd64-s015.vmdk"
RW 8323072 SPARSE "Kali-Linux-2021.3-vmware-amd64-s016.vmdk"
RW 8323072 SPARSE "Kali-Linux-2021.3-vmware-amd64-s017.vmdk"
RW 8323072 SPARSE "Kali-Linux-2021.3-vmware-amd64-s018.vmdk"
RW 8323072 SPARSE "Kali-Linux-2021.3-vmware-amd64-s019.vmdk"
RW 8323072 SPARSE "Kali-Linux-2021.3-vmware-amd64-s020.vmdk"
RW 1310720 SPARSE "Kali-Linux-2021.3-vmware-amd64-s021.vmdk"

# The Disk Data Base
#DDB

ddb.adapterType = "lsilogic"
ddb.geometry.cylinders = "10443"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.longContentID = "9e8f02c9478181567bade1d7ea5ff782"
ddb.toolsInstallType = "4"
ddb.toolsVersion = "11333"
ddb.uuid = "60 00 C2 9e 99 5c 72 b7-c2 ca 08 3c e8 78 f6 8e"
ddb.virtualHWVersion = "8"

"

and I saw the missing file!! Sheessh...so how do i put back the s018.vmdk?

07/12/2021 09:45 am 6,815,744 Kali-Linux-2021.3-vmware-amd64-000016-s017.vmdk
07/12/2021 09:45 am 155,123,712 Kali-Linux-2021.3-vmware-amd64-000016-s019.vmdk
07/12/2021 09:45 am 422,903,808 Kali-Linux-2021.3-vmware-amd64-000016-s020.vmdk
07/12/2021 12:10 am 670,171,136 Kali-Linux-2021.3-vmware-amd64-000016-s021.vmdk

[a_p_]

If this file cannot be recovered, you may replace it with another "empty" .vmdk file, that just contains the required metadata. In your case that's a .vmdk file with a size of 524.288 Bytes. In case you don't have one, you can use the one that I've attached to this reply.

Once replaced, I suggest that you create a new snapshot, so that the current files will not get modified, and you can revert to the current state.

The lost data from this file will cause more, or less data corruption/loss, and possible file system issues, depending on the lost data. If this is the latest snapshot in the snapshot chain, you may consider to revert to the last snapshot (if that is an option for you), which will of course discard the current snapshot's changes, but will result in a healthy file system.

André

[hstony]

godsend! Thanks much! Really appreciate your help!