VMware Communities
jhonut
Contributor
Contributor

Unable top open .vmdk file. The system cannot find the file specified.

I know this issue has been post, but I still couldn't solve it.

I want to open a vm (VMware Workstation 15 PR 15.1.0)) but I get the message: Unable top open .vmdk file. The system cannot find the file specified. 

The file exists as you can see in the bellow photo.

jhonut_0-1686213834644.png

My log files are attached. I have seen on vmware.log on line 18382 that I get this error: recv error 10054: An existing connection was forcibly closed by the remote host.

How could I be able to open again the VM?

Labels (1)
Reply
0 Kudos
9 Replies
a_p_
Leadership
Leadership

It's "Windows 10 x64-0-s001.vmdk" which is missing.

According to the screenshot, this is an additional virtual disk, which does not seem to contain data and has not been touched since 2021 anyway!? In that case you may either remove that second virtual disk from the VM's configuration, or replace the missing file with a copy of e.g. "Windows 10 x64-0-s002.vmdk".

André

 

Reply
0 Kudos
jhonut
Contributor
Contributor

Thanks for reply, @a_p_ André!

I have tried to replace the missing file with a copy of e.g. "Windows 10 x64-0-s002.vmdk", but it didn't work. When I go to VM's settings, I get to hard disks(Hard Disck (SCSI) and Hard Disk 2 (SCSI)), but when I click on one of them, I get the error: "The system cannot find the file specified.". Which one should be deleted? "Windows 10 x64-0-s002.vmdk" is part of Hard Disk or Hard Disk 2?

Reply
0 Kudos
a_p_
Leadership
Leadership

Can you confirm that VMware Workstation, or at lease the VM's tab was closed and re-opened after replacing the file? Some data is cached, and needs to be re-read after manual modifications.

Anyway, as a workaround you may delete the  "scsi0:1" lines from the VM's .vmx file. Again, with the VM's tab closed!

scsi0:1.fileName = "Windows 10 x64-0.vmdk"
scsi0:1.present = "TRUE"
scsi0:1.redo = ""

André

Reply
0 Kudos
jhonut
Contributor
Contributor

This what I get if I delete those lines.

Yes, VMWare workstation is closed.

jhonut_1-1686223410291.png

 

Reply
0 Kudos
a_p_
Leadership
Leadership

Let's take a complete look at this.

Please run dir *.* /oen > filelist.txt in the VM's folder, then compress/zip filelist.txt along with the VM's .vmx and the vmware.log file,  and attach the .zip archive to your next reply.

André

Reply
0 Kudos
jhonut
Contributor
Contributor

 
Reply
0 Kudos
a_p_
Leadership
Leadership

I see two issues:

  1. It seems that you've not only deleted the "scsi0:1" lines for the second disk, but also those for the first disk "scsi0:0".
    Not a big deal, either add them back in, or attach the virtual disk from the GUI (once the virtual disk has been fixed).
  2. A much bigger issue is the fact that "Windows 10 x64-s005.vmdk" is missing. Looking at the other .vmdk files, this is likely a loss of about 4GB data. In many cases .vmdk files got detected as false positives from a virus scan application. So please check whether this file has been quarantined, and can be restored/released.
    If that's not the case, it will be possible to replace the missing file with a stub file that only contains the required metadata. Since the virtual disk looks like it has been resized, it may not be possible to simply replace it with one of the smaller files. If you cannot find/recover the missing file, then attach "Windows 10 x64.vmdk" which contains information needed to create a replacement file.

André

Reply
0 Kudos
jhonut
Contributor
Contributor

1. Sorry for the mistake! I have put back as you suggested, but it doesn't find the vmdk file eventhough it exists.

jhonut_0-1686294547470.png

Firstly I want to be able to open the VM.

2. I have checked the antivirus qurantine and the list it's empty.

"... it will be possible to replace the missing file with a stub file that only contains the required metadata". How could I do this?

Reply
0 Kudos
a_p_
Leadership
Leadership

As mentioned before:

"If you cannot find/recover the missing file, then attach "Windows 10 x64.vmdk" which contains information needed to create a replacement file."

What's needed is a .vmdk file that can hold the same capacity. The block sizes for all the "-s0xx.vmdk" are shown in the descriptor .vmdk file. So what's required as a replacement for the missing file, is file with the same number of blocks.
Hint: once the file exists, take a VM snapshot prior to powering on the VM. This way you can always revert back to the current state, in case you need to.

André

Reply
0 Kudos