rollbahn
Contributor
Contributor

The system cannot find the file specified - Windows 2000-0.vmdk

I'm having a weird issue with a VM that I copied over from a Time Machine backup where I open the VM in Fusion and it says "Windows 2000-0.vmdk" is missing but I checked and it is definitely there (although only a 2k file).

Just for some background that might matter in figuring out the issue - I also had some weird issues with this VM on the original computer before the backup, where if I tried to copy the VM to another drive it always got stuck when it was trying to copy "Windows 2000-0.vmdk" - it said it was in use...which it wasn't.

Thanks for any help you can offer.

I am using VM Fusion 8.5.10 on OSX 10.13.6.

Thanks

Jason

0 Kudos
4 Replies
RDPetruska
Leadership
Leadership

Attach a complete directory file listing of the VM's folder - detail mode (names, dates, sizes).

Also, the latest vmware.log for that VM.

FYI note - Time Machine backups are not a good method for backing up virtual machines if they are running.  Refer to other threads in this forum for examples.

0 Kudos
a_p_
Leadership
Leadership

Welcome to the Community,

by default, virtual disks in Fusion consist of multiple files, a header/descriptor .vmdk file, and data .vmdk files.

The descriptor file contains metadata, including a list of data files which make up the virtual disk. These data files are usually names "...-s00x.vmdk". Please chech whether all of these files exist in the VM's package/folder.

"The system cannot find the file specified" usually means that one, or more of these files are missing.

André

0 Kudos
rollbahn
Contributor
Contributor

Thanks everyone - I have taken a closer look at the Package contents of the VM and it looks as though the actual culprit is "Windows 2000-0-s022.vmdk" which I found is missing by comparing to the list in the Windows 2000-0.vmdk file. I have 113GB in there but I guess I am out of luck if I am missing this file?

0 Kudos
a_p_
Leadership
Leadership

If you can't find/restore this file, it's at least possible to replace it with an "empty" one that just contains the required metadata. This won't bring back the data, but it will allow to to open the virtual disk, and backup important contents.

If this is what you'd like to do, then please provide a complete list of the VM's files (the output of ls -l from the command line), and attach the descriptor .vmdk to a reply post, so that I can take a look at this, and let you know how to proceed.


André

0 Kudos