Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Recreating a missing virtual disk (VMDK) descriptor file for disks split into 2GB files (1026266)

Last Updated: 3/20/2024Categories: How toTotal Views: 28403Language:
English

6 like this article

Subscribe to get an email
newsletter with new updates

6 people found this helpful Please provide article feedback:

Purpose

This article provides the instructions to recreate a virtual disk descriptor file for a virtual disk split up across several 2GB extents.

Resolution

A VMware ESX virtual machine disk that is split into several 2GB files consists of a single descriptor and multiple extent files, in sequence, based on the twoGbMaxExtentFlat or twoGbMaxExtentSparse disk format.

Note: For more information on virtual disk format, see VMware Virtual Disks: Virtual Disk Format v1.1.

To recreate the virtual disk descriptor file:

Create a virtual disk descriptor file for use as a base or template. For more information, see Recreating a missing virtual disk (VMDK) header/descriptor file (1002511).

Open the descriptor file using a text editor.

Modify the CreateType entry as:

createType="twoGbMaxExtentSparse"

Note: The CreateType value depends on the type of extent used when the virtual disk was created. It can either be twoGbMaxExtentFlat or twoGbMaxExtentSparse.

Locate the # Extent description section. Replace the contents in this section with a list of your extents:

RW 4192256 SPARSE "vmdisk0-s001.vmdk"
RW 4192256 SPARSE "vmdisk0-s002.vmdk"
RW 2101248 SPARSE "vmdisk0-s003.vmdk"

Modify the DDB entries as follows:

ddb.virtualHWVersion = "4"
ddb.geometry.cylinders = "652"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.adapterType = "lsilogic"

Locate and remove this line from the descriptor file, unless this was originally a thin-provisioned virtual disk before losing the descriptor file:

ddb.thinProvisioned = "1"

Related Information

Comparison of the base descriptor file and the tailored descriptor file

The following table provides a comparison of the base descriptor file and the tailored descriptor file:

Base Descriptor File

Tailored Descriptor File

# 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"

# Disk DescriptorFile
version=1
CID=fb183c20
parentCID=ffffffff
createType="twoGbMaxExtentSparse"

# Extent description
RW 4192256 SPARSE "vmdisk0-s001.vmdk"
RW 4192256 SPARSE "vmdisk0-s002.vmdk"
RW 2101248 SPARSE "vmdisk0-s003.vmdk"

# The Disk Data Base
#DDB

ddb.virtualHWVersion = "4"
ddb.geometry.cylinders = "652"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.adapterType = "lsilogic"

The extent description section in the tailored descriptor file has the following values:

RW 4192256 SPARSE "vmdisk0-s001.vmdk"
RW 4192256 SPARSE "vmdisk0-s002.vmdk"
RW 2101248 SPARSE "vmdisk0-s003.vmdk"

The RW value is the number of 512-Byte sectors for the extent or disk file. All but the final disk in the chain should be 4192256 512-Byte sectors, amounting to 2GB.

The sector count is determined by multiplying the number of cylinders, heads, and sectors. The number of cylinders, heads, and sectors are defined in the DDB section.

The total number of extents may deviate from the example above; append new lines containing information similar to the above, accounting for all the files in the chain.

In the above example, there are two 2GB files and a partial (or <2GB) disk file at the end of the chain. The total size of the disk did not reach or exceed 6GB.</li>

The DDB section in the tailored description file has the following values:

ddb.geometry.cylinders = "652"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.adapterType = "lsilogic"

The ddb.geometry.heads value is always 255 for virtual machine disks (in entirety) equal to, or larger than, 2GB.

The ddb.geometry.sectors value is always 63 for virtual machine disks (in entirety) equal to, or larger than 2GB.

The ddb.geometry.cylinders value requires special consideration.

Cylinder Calculations

The number of cylinders is determined by multiplying the number of heads (255) and sectors (63), which equals 16065.

This number is multiplied by 512, which equals 8225280.

Divide the total size of the virtual disk in bytes by 8225280, per the value above.

Round this off to the nearest integer to get the ddb.geometry.cylinders value.

For example:

5,368,709,120 / (255 * 63 * 512)
= 5,368,709,120 / 8225280
= 652.70837223778400248988484282602
= 652 cylinders

If the size of the disk is less than 1GB:

Set ddb.geometry.heads to 64.

Set ddb.geometry.sectors to 32.

Set ddb.geometry.cylinders to the integer portion of the value obtained when the size of the disk (in bytes) is divided by 1048576.

Note: This number (1048576) is generated by multiplying head and sector values, and 512, for the block size.

If the size of the flat file is 1GB or more but less than 2GB:

Set ddb.geometry.heads to 128.

Set ddb.geometry.sectors to 32.

Set ddb.geometry.cylinders to the integer portion of the value obtained when the size of the disk (in bytes) is divided by by 2097152.

If the size of the flat file is 2GB or more:

Set ddb.geometry.heads to 255.

Set ddb.geometry.sectors to 63.

Set ddb.geometry.cylinders to the integer portion of the value obtained when the size of the disk (in bytes) is divided by 8225280.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
ESX/ESXi ホスト上の物理ネットワーク アダプタの整合性の確認 (1003686)

KB
•
VMware Consolidated Backup を使用すると vCenter Server にディスク領域のマップ タスクが繰り返し表示される (1007331)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware ESX Server

Related Versions:

VMware vSphere ESXi 5.0

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESXi 3.5.x Installable

VMware ESXi 3.5.x Embedded

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

VMware ESX 4.1.x

VMware ESX 4.0.x

view all

Take Our Survey

Support Assistant