Solved

VMware Virtual Machine has only VMDK file

Posted on 2014-09-22
7
1,183 Views
Last Modified: 2014-10-06
I recently upgraded to VMWare version 5.5 and then migrated my virtual machines from local storage to our new SAN.  All migration seemed to work fine except one.  I didn't get any errors indicating a problem, but when the migration was finished, I didn't see the VM anymore in the list.  So I went to the new location on our SAN and the folder for the VM was there.  However, the only file in the folder was the VMDK file and I don't see a way to add it back to inventory.  What happened and how do I recover this VM?
0
Comment
Question by:sfletcher1959
  • 4
  • 2
7 Comments
 
LVL 119
ID: 40336533
Check for the VMX file, on local or shared SAN storage.

You will need the VMX file to register to the inventory. (right click VMX file, select Add to Inventory).

if you cannot find the VMX file, create a new Virtual Machine with the same VM Settings as before, e.g. CPU, Memory, Windows version (Custom), and select and browse to the virtual disk in the datastore.

(no need to create a new disk, because you already have one!)
0
 

Author Comment

by:sfletcher1959
ID: 40337296
Okay, upon closer inspection I found more information.  Apparently when I migrated the VM it has the VMDK file in two location.  

The original location only has the VMDK file in the folder with the VM name.  The location it was supposed to migrate too seens to have all the appropriate files in a folder with the VM name .  See scree shot attached.  So I added the VM to inventory that appeared to have all the right files in the folder and tried to power it on.  It failed with the following error information:

An error was received from the ESX host while powering on VM ProData001.
Failed to start the virtual machine.
Module DiskEarly power on failed.
Cannot open the disk '/vmfs/volumes/541b38e7-c468edac-d975-0024817edd14/ProData001/ProData001-000001.vmdk' or one of the snapshot disks it depends on.
The parent virtual disk has been modified since the child was created. The content ID of the parent virtual disk does not match the corresponding parent content ID in the child

Screenshot
0
 

Author Comment

by:sfletcher1959
ID: 40337309
So to clarify, I migrated Prodata001 on Datastore 1 to Datastore 2.  No errors on the completed migration.  Datastore 1 still had a vmdk file for Prodata001.  Datastore 2 has all files, but will not power on.
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 

Author Comment

by:sfletcher1959
ID: 40337336
I have tried to migrate back from Datastore 2 to Datastore 1, but the migration fails with error:

error caused by file /vmfs/volumes/541b38e7-c468edac-d975-0024817edd14/prodata001/prodata001-000001.vdmk


 I am able to migrate between hosts successfully, but still get the same error when I try to power on.
0
 
LVL 119

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 40337637
Okay, firstly this VM appears to have a snapshot, which I think has caused the complications here.

Files got migrated and some files did not get migrated, then the VM and disk were powered on without it's snapshot attached, and hence the error.

You will need to move back all the files so there are in the same folder.

and then you will need to repair the VMDK file, so snapshot chain is valid....

see here

Resolving the CID mismatch error: The parent virtual disk has been modified since the child was created (1007969)
0
 

Author Closing Comment

by:sfletcher1959
ID: 40364110
Was able to resolve the CID mismatch error as suggest above.
0

Featured Post

The Eight Noble Truths of Backup and Recovery

How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Will try to explain how to use the VMware feature TAGs in the VMs and create Veeam Backup Jobs using TAGs. Since this article is too long, I will create second article for the Veeam tasks.
In this article, I will show you HOW TO: Create your first Windows Virtual Machine on a VMware vSphere Hypervisor 6.5 (ESXi 6.5) Host Server, the Windows OS we will install is Windows Server 2016.
Teach the user how to install vSphere Update Manager  Console to Windows system:  Install vSphere Update Manager: Configure vSphere Update Manager plug-in in vSphere Client: Verify vSphere Update Manager settings in vSphere Client:
This video shows you how to use a vSphere client to connect to your ESX host as the root user. Demonstrates the basic connection of bypassing certification set up. Demonstrates how to access the traditional view to begin managing your virtual mac…

773 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question