TK-FOUR21
asked on
VmWare WS 7.1.5 - copied over VM, claims missing .vmdk files on target but files are not on source
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,
It worked prior to the copy, why would it be looking for files that aren't there?
Thoughts?
thanks,HT
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,
It worked prior to the copy, why would it be looking for files that aren't there?
Thoughts?
thanks,HT
motnahp00
Have you tried cloning the VM instead of copying the directory? I think it is a much cleaner process.
ASKER
Hi, I could try that in future "moves" but it doesn't help me in this one.
thanks,
thanks,
Try creating a new VM and attaching the VHDs.
ASKER
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,
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,
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
the files you are missing are the snapshot files, do your vms have snapshots?
ASKER
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.
It has worked like a gem up until this copy over to a new drive.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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?
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?
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.
The best method is to ensure no snapshots are present before moving.
ASKER
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,
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,
virtual machine disk is corrupted, you could check with BartPE cdrom boot disk for data.
ASKER
Hi,
How would I use BartPE to get into a VM that doesn't power on?
thanks,
How would I use BartPE to get into a VM that doesn't power on?
thanks,
connect the bartpe iso to the cdrom and boot the vm.
then check for data, os partition
then check for data, os partition
ASKER
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,
...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,
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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
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
ASKER
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.
make sure you have no snapshots before you move a VM!
Clone your VM to a new machine to be sure it moves correctly.