{"id":93,"date":"2008-10-02T08:47:45","date_gmt":"2008-10-02T07:47:45","guid":{"rendered":"http:\/\/www.amikkelsen.com\/?p=93"},"modified":"2008-12-01T13:00:00","modified_gmt":"2008-12-01T12:00:00","slug":"recreating-a-missing-vmdk-descripter-file","status":"publish","type":"post","link":"https:\/\/www.amikkelsen.com\/?p=93","title":{"rendered":"Recreating a missing VMDK descripter file"},"content":{"rendered":"

A few weeks ago we were conducting a vRanger DR test of a VM (new host and new LUN).<\/p>\n

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.
\nIt had created two new 20GB VMDK’s instead.
\nWe searched the LUN and found the two orginal *-flatvmdk files but not the descripter files.<\/p>\n

Use Putty to identify the size of the *-flatvmdk file. ex. 100GB<\/p>\n

ls -lah<\/pre>\n
From a VM (not running) create a new disk with the same size as the one you are missing. The name is not important.<\/p>\n
Locate the newly created *.vmdk and *-flat.vmdk file. Copy the new *.vmdk file to the folder that contains the orginal *-flat.vmdk file.<\/p>\n
cp rescue_me.vmdk \/vmfs\/volumes\/mysan\/rescued\/rescued.vmdk<\/pre>\n
Use VI or NANO to change the following line as below from:
\nRW 419426200 VMFS \u00e2\u20ac\u0153rescue_me-flat.vmdk\u00e2\u20ac\u009d<\/span>
\nTo:
\nRW 419430500 VMFS \u00e2\u20ac\u0153rescued-flat.vmdk\u00e2\u20ac\u009d<\/span><\/p>\n
Make sure that the name of the .vmdk file correspond to the SCSI*:*.fileName in the vmx file.
\nNow just power on the VM and the orginal disks are intac.<\/p>\n
UPDATE<\/strong><\/span>
\nToday I found out that esXpress has created a website that can create a VMDK descriptor file.<\/span>
\nhttp:\/\/www.esxpress.com\/tools\/wrapgen.php<\/a><\/p>\n
Below is an exampel for the rescure_me-flat.vmdk file with a size of 100GB (107374182400 bytes)
\n\"esXpress<\/p>\n","protected":false},"excerpt":{"rendered":"
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\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19,17,18,16,10],"tags":[35,26,36,39,42,41,38,37,40],"class_list":["post-93","post","type-post","status-publish","format-standard","hentry","category-disaster-recovery","category-esx-i","category-vranger","category-esx-x","category-white-papers","tag-descipter","tag-esx","tag-esxi","tag-flat","tag-flatvmdk","tag-missing","tag-vmdk","tag-vmware","tag-vmx"],"_links":{"self":[{"href":"https:\/\/www.amikkelsen.com\/index.php?rest_route=\/wp\/v2\/posts\/93","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.amikkelsen.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.amikkelsen.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.amikkelsen.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.amikkelsen.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=93"}],"version-history":[{"count":0,"href":"https:\/\/www.amikkelsen.com\/index.php?rest_route=\/wp\/v2\/posts\/93\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.amikkelsen.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=93"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.amikkelsen.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=93"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.amikkelsen.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=93"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}