Recreating a missing VMDK descriptor file

Recreating a missing VMDK descripter file
Posted on October 2nd, 2008 A. Mikkelsen 4 comments

A few weeks ago we were conducting a vRanger DR test of a VM (new host and new LUN).

The VM was restored succesfull, but when we powered it on we discovered that it for some unexplaned reason had lost the SCSI0:1 (100GB) and SCSI0:2(300GB) VMDK’s.
It had created two new 20GB VMDK’s instead.
We searched the LUN and found the two orginal *-flatvmdk files but not the descripter files.

Use Putty to identify the size of the *-flatvmdk file. ex. 100GB

ls -lah

From a VM (not running) create a new disk with the same size as the one you are missing. The name is not important.

Locate the newly created *.vmdk and *-flat.vmdk file. Copy the new *.vmdk file to the folder that contains the orginal *-flat.vmdk file.

cp rescue_me.vmdk /vmfs/volumes/mysan/rescued/rescued.vmdk

Use VI or NANO to change the following line as below from:
RW 419426200 VMFS “rescue_me-flat.vmdk”
To:
RW 419430500 VMFS “rescued-flat.vmdk”

Make sure that the name of the .vmdk file correspond to the SCSI*:*.fileName in the vmx file.
Now just power on the VM and the orginal disks are intac.

UPDATE
Today I found out that esXpress has created a website that can create a VMDK descriptor file.
http://www.esxpress.com/tools/wrapgen.php


http://www.amikkelsen.com/?p=93

Using 64 bit Virtual Machines with ESX 3.5

in order to set up and install 64 bit Windows servers as virtual machines in ESX 3.5, a bios setting change has to be made.

1. enable VT
a. in bios, select Advanced Options -> Processor Options -> Intel VT
b. change from "Disabled" to "Enabled"
2. if that doesn't work, try
a. Advanced Options -> Processor Options -> No-Execute Page-Protection
b. change from "Disabled" to "Enabled"