VmWare WS 7.1.5 - copied over VM, claims missing .vmdk files on target but files are not on source

TK-FOUR21
TK-FOUR21 used Ask the Experts™
on
Hello,

I needed to put in a new HD in my machine so I copied out the vmware folder housing my VM. I compared sizes and total files and all was well.
I installed a new host OS, installed VMware, copied over the files, started VM and pfft, missing vmdk files.
No problem right, I went back to the original to look for those files and they're not there!

The file VMWare claims it is missing file is vXP_1-000009.vmdk
The files on in folder are vXP_1-000001,2,3,5,7,8,11,12,13,14,17.vmdk

It worked prior to the copy, why would it be looking for files that aren't there?

Thoughts?
thanks,HT
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Have you tried cloning the VM instead of copying the directory? I think it is a much cleaner process.

Author

Commented:
Hi, I could try that in future "moves" but it doesn't help me in this one.
thanks,
Try creating a new VM and attaching the VHDs.
How to Generate Services Revenue the Easiest Way

This Tuesday! Learn key insights about modern cyber protection services & gain practical strategies to skyrocket business:

- What it takes to build a cloud service portfolio
- How to determine which services will help your unique business grow
- Various use-cases and examples

Author

Commented:
Hi,
I will try this, please confirm this is what you mean.

New VM --> Win XP, name it the same as the prior with the same options --> install OS later.
Copy out the working files from the new VM to a saved dir, then copy in the old working files into the new VM. Start the VM.

Is there anything else I'd need to do?
thanks,
You got it.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
the files you are missing are the snapshot files, do your vms have snapshots?

Author

Commented:
I used to use "autoprotect" snapshots but the sizing got unruly, so many months ago I disabled snapshots.
It has worked like a gem up until this copy over to a new drive.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017
Commented:
if you do not have the parent disks and the entire snapshot chain, your virtual machine disks will be corrupted.

Author

Commented:
Hi,
That makes sense, EXCEPT that apparently those files were not on the original machine either. I copied everything that was on the original machine to the target.
Bizarre no?
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
Moving virtual machines with snapshots, and re-registering with new system, can cause issues.

The best method is to ensure no snapshots are present before moving.

Author

Commented:
Hi,
I've tried this a few different ways and I only get "no operating system found".

I can't believe this!

any other thoughts before I scrap this VM?

thanks,
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
virtual machine disk is corrupted, you could check with BartPE cdrom boot disk for data.

Author

Commented:
Hi,
How would I use BartPE to get into a VM that doesn't power on?
thanks,
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
connect the bartpe iso to the cdrom and boot the vm.

then check for data, os partition

Author

Commented:
I see what you are saying, yes BPE sees only the new empty disk, so it is not taking the disks I placed in the directory into account. When I've removed the new disk and only leave the old disks, it comes up with the same error as before of "missing vXP_1-000009.vmdk"...

...Even though this file was not on the prior machine...

I've created a new VM and this time I'm only going to use a single hard drive image file.
That's how my servers are, I'm not even sure why I chose to use the separate files at this point.

I do plan on leaving this question open just in case someone has a silver bullet.
thanks,
Nagendra Pratap SinghDesktop Applications Specialist
Commented:
Make a copy of entire folder (vmdk,vmx etc) for backup.

copy vXP_1-000008.vmdk to vXP_1-000009.vmdk so it makes vmware happy.

Start the VM. if all is OK then report back else use the backup folder and keep troubleshooting.


BTW i have used this method once and I saw it here

http://www.vladan.fr/recreate-a-missing-vmdk-header-file/

Author

Commented:
hi singh,
That has had the greatest amount of progress but get this, after getting past the .vmdks is missing message, it then asked for the  vXP_1-Snapshot1.vmsn file and my first snapshot file is vXP_1-Snapshot71.vmsn. I looked back on the original drive to make sure there isn't a 1 and sure enough, no 1.
So, I don't know what this VM thinks it is trying to do, but I'll take this as lesson never to use the "split-disk" option.
All of my servers are in single-disk and my other VMs are single-disk and I can't even tell you why this one was in a split-disk configuration. (probably just because I'd never done it before).

I'll split up the points between the three who responded.
thanks you all for trying, HT

Author

Commented:
don't use VMWare's split-disk option!
make sure you have no snapshots before you move a VM!
Clone your VM to a new machine to be sure it moves correctly.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial