Vmware ESXI vmdk Tanım Dosyasını Yeniden Oluşturma

Vmware ESXI Vmname-disk-1.vmdk Tanım Dosyasını Yeniden Oluşturma

# cd /vmfs/volumes/myvmfsvolume/mydir
# ls -l vmdisk0-flat.vmdk

-rw------- 1 root root 4294967296 Oct 11 12:30 vmdisk0-flat.vmdk

# vmkfstools -c 4294967296 -d thin temp.vmdk
# vi temp.vmdk
change line  "temp.vmdk"  to "vmname-flat.vmdk"
Rename temp.vmdk to the name that is required to match the orphaned -flat file (or vmdisk0.vmdk , in this example):

# mv -i temp.vmdk vmdisk0.vmdk

 

Log in to the terminal of the ESXi host via SSH or DCUI.
Navigate to the directory that contains the virtual machine disk with the missing descriptor file using the command:

# cd /vmfs/volumes/myvmfsvolume/mydir
Identify the type of SCSI controller the virtual disk is using by examining the virtual machine configuration file (.vmx ). The controller is identified by the line scsi#.virtualDev , where # is the controller number. There may be more than one controller and controller type attached to the virtual machine, such as lsisas1068 (which is the LSILogic SAS controller), lsilogic , or buslogic.

This example uses lsilogic :

scsi0.present = “true”
scsi0.sharedBus = “none”
scsi1.present = “true”
scsi1.sharedBus = “virtual”
scsi1.virtualDev = “lsilogic”

Identify and record the exact size of the -flat file using a command similar to:

# ls -l vmdisk0-flat.vmdk

-rw——- 1 root root 4294967296 Oct 11 12:30 vmdisk0-flat.vmdk

Use the vmkfstools command to create a new virtual disk:

# vmkfstools -c 4294967296 -d thin temp.vmdk

The command uses these flags:

Note: To save disk space, we create the disk in thin-provisioned format using the type thin. The only consequence, however, is that the descriptor file contains an extra line that must be manually removed in a later step if the original disk is not Thin provisioned.

The temp.vmdk and temp-flat.vmdk files are created as a result.

-c size
This is the size of the virtual disk.
-d thin
This creates the disk in thin-provisioned format.
Delete temp-flat.vmdk, as it is not needed. Run the command:

# rm -i temp-flat.vmdk

Rename temp.vmdk to the name that is required to match the orphaned -flat file (or vmdisk0.vmdk , in this example):

# mv -i temp.vmdk vmdisk0.vmdk

Edit the descriptor file using “vi” text editor ( vi vmdisk0.vmdk, in this example)

Under the Extent Description section,

Use command “Shift + r” to enter replace mode.
Locate and change the name of the -flat file to match the orphaned -flat, Press “Esc” to exit replace mode.

Find and remove the line ddb.thinProvisioned = “1” if the original .vmdk was not a thin disk. If it was, retain this line. Use command “Shift + zz” to save and exit “vi” editor.

Example

# Disk DescriptorFile
version=1
CID=fb183c20
parentCID=ffffffff
createType=”vmfs”

# Extent description
RW 8388608 VMFS “vmdisk0-flat.vmdk”

# The Disk Data Base
#DDB

ddb.virtualHWVersion = “4”
ddb.geometry.cylinders = “522”
ddb.geometry.heads = “255”
ddb.geometry.sectors = “63”
ddb.adapterType = “lsilogic”
ddb.thinProvisioned = “1”

The virtual machine is now ready to power on. Verify your changes and ensure Disk chain is consistent before starting the virtual machine.

To check the disk chain for consistency, run this command against the disk descriptor file:

# vmkfstools -e filename.vmdk

For a complete chain, you see output similar to:
Disk chain is consistent

For a broken chain, you see a summary of the snapshot chain and then an output similar to:
Disk chain is not consistent : 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 (18)

Bir cevap yazın

E-posta hesabınız yayımlanmayacak. Gerekli alanlar * ile işaretlenmişlerdir

This site uses Akismet to reduce spam. Learn how your comment data is processed.