drabdoo
Contributor
Contributor

not enough permissions

VMware workstation 16 runs as administrator, the vm appears in the drop-down menu. After clicking power on -> "file not found: VM-bit.vmdk This file is required to power on this virtual machine. If this file was moved, specify the new location." -> "Browse", the VM is found in the folder and -> "Error while powering on: Error while replacing a missing file: Insufficient permission to access the file." Permissions for the entire folder are changed -> try again "power on" from the drop down menu ->

"Error while powering on: The file specified is not a virtual disk

Cannot open the disk 'C:\Users\...\VM-bit\Ubuntu 64-bit-s001 (2021_01_16 00_28_49 UTC).vmdk' or one of the snapshot disks it depends on.

Module 'Disk' power on failed.

Failed to start the virtual machine."

Have tried with several of the available ".vmdk" files in the VM folder and that error continues.

 

 

 

0 Kudos
5 Replies
scott28tt
VMware Employee
VMware Employee

@drabdoo 

Moderator: Please try and create a thread in the area for the product used - moved to Workstation Pro Discussions (though you may be using Workstation Player)


-------------------------------------------------------------------------------------------------------------------------------------------------------------

Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
0 Kudos
a_p_
Leadership
Leadership

>>> Have tried with several of the available ".vmdk" files in the VM folder and that error continues.
That's usually not a good idea, and can make things even worse.

The error mentioned message appears if one of the required .vmdk files are missing. By default, a virtual disk in VMware Workstation consists of one header/descriptor .vmdk file (<vmname>.vmdk), and multiple data .vmdk files (<vmname>-s00x.vmdk). The required .s00x.vmdk  files are all listed in the header/descriptor file. If one of them is missing it needs to be replaced by either a recent backup, or a new file that only contains metadata. In both cases you may experience data loss, and/or file system corruption within the guest OS.

In doubt, please post a list of files in the VM's folder, i.e. the text output of either dir *.* /oen (for Windows), or ls -lisa (for Linux).

André

0 Kudos
drabdoo
Contributor
Contributor

okay thank you. Yeah, I am trying with workstation pro.

0 Kudos
drabdoo
Contributor
Contributor

Ah ok, I have been trying to load it from the header. The backup is not loading, only managed to retreive the vm from the older volume, but not the backup copy. the list looks like this :

Ubuntu 64-bit (2021_01_16 00_28_49 UTC).vmdk
Ubuntu 64-bit-s001 (2021_01_16 00_28_49 UTC).vmdk
Ubuntu 64-bit-s002 (2021_01_16 00_28_49 UTC).vmdk
Ubuntu 64-bit-s003 (2021_01_16 00_28_49 UTC).vmdk
Ubuntu 64-bit-s004 (2021_01_16 00_28_49 UTC).vmdk
Ubuntu 64-bit-s005 (2021_01_16 00_28_49 UTC).vmdk
Ubuntu 64-bit-s006 (2021_01_16 00_28_49 UTC).vmdk
Ubuntu 64-bit-s007 (2021_01_16 00_28_49 UTC).vmdk
Ubuntu 64-bit-s008 (2021_01_16 00_28_49 UTC).vmdk
Ubuntu 64-bit-s009 (2021_01_16 00_28_49 UTC).vmdk
Ubuntu 64-bit-s010 (2021_01_16 00_28_49 UTC).vmdk
Ubuntu 64-bit-s011 (2021_01_16 00_28_49 UTC).vmdk
Ubuntu 64-bit-s012 (2021_01_16 00_28_49 UTC).vmdk
Ubuntu 64-bit-s013 (2021_01_16 00_28_49 UTC).vmdk
Ubuntu 64-bit-s014 (2021_01_16 00_28_49 UTC).vmdk
Ubuntu 64-bit-s015 (2021_01_16 00_28_49 UTC).vmdk
Ubuntu 64-bit-s016 (2021_01_16 00_28_49 UTC).vmdk
Ubuntu 64-bit-s017 (2021_01_16 00_28_49 UTC).vmdk
0 Kudos
a_p_
Leadership
Leadership

Not exactly what I asked for, but it looks like you may simply need to remove "(2021_01_16 00_28_49 UTC)" from the file names to make the virtual disk work again. Check for the correct/required file names within the header file "Ubuntu 64-bit (2021_01_16 00_28_49 UTC).vmdk".

André

0 Kudos