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

Skip to main content

Products and Accounts

Support

Knowledge

Communities

Success

Learning

My Subscriptions

Loading

Knowledge Base

A VMFS volume is not available and the VMkernel log reports the error: Device size mismatch or Device shrank or Device Expanded (1003133)

Last Updated: 12/11/2012Categories: TroubleshootingTotal Views: 20617Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Details

A VMFS volume is not available.

The VMkernel log contains messages similar to:

WARNING: LVM: 1650: [vmhba1:0:2:1] Device size mismatch (actual 16777083 blocks, stored 16777088 blocks)

WARNING: LVM: 2446: [naa.6090a018d094045259bf048f8a007041:1] Device shrank (actual size 2147504812 blocks, stored size 2147512192 blocks)

Solution

This issues occurs when the partition table geometry does not match the size of the partition table when the VMFS volume was created.

To correct the partition size:

Identify the device that contains the bad partition table. Run the command:

esxcfg-vmhbadevs | grep <vmhba device identified in the log>

Using the example from the Symptoms section, the command and resulting sample output would be:

# esxcfg-vmhbadevs | grep vmhba1:0:2
vmhba1:0:2 /dev/sdf

In ESX 3.5, the error message reported in /var/log/vmkernel looks like:

WARNING: LVM: 1625: [vml. 0200000000600601601d311f00f06679650293de11524149442035:1] Device size mismatch (actual 16777083 blocks, stored 16777088 blocks)

In ESX 4.x, the error message reported in /var/log/vmkernel looks like:

WARNING: LVM: 2446: [naa.6090a018d094045259bf048f8a007041:1] Device shrank (actual size 16777083 blocks, stored size 16777088 blocks)

This command provides the device and this sample output:

# esxcfg-mpath -lv | grep 0200000000600601601d311f00f06679650293de11524149442035
vmhba1:1:0 vml.0200000000600601601d311f00f06679650293de11524149442035 /dev/sdf (#####MB) has # paths and policy of XXXXX

Calculate the ending expected ending block of the partition table.

VMFS volumes on ESX 3 and ESX 4 hosts, when created using the VMware Infrastructure or vSphere Client (connected to the server directly or through vCenter Server) are aligned to sector 128.

VMFS volumes that were upgraded from an ESX 2 host or incorrectly created by hand on the command line are set to sector 63. The <starting offset> number is 128 (most likely) or 63.

To calculate the correct ending block, use this formula: <Stored> + <Starting offset> - 1

In this sample, the volume was originally created by an ESX 3 host using the VMware Infrastructure Client, so the starting sector is 128:

16777088 + 128 - 1 = 16777215

Recreate the partition so match the calculated geometry using fdisk:

Start fdisk on the device using -u to be able to set the starting block:

fdisk -u /dev/sdX

If the partition exists, remove it:

Note: This does not delete the data inside the partition.

Press d and press Enter.

Press 1 and press Enter.

Create the partition:

Press n and press Enter.

Press P to create primary partition.

Enter the calculated value of the starting offset (in this sample, 128) and press Enter.

Enter the calculated value of the ending block (in this sample, 16777215) and press Enter.

Change the partition to type FB:

Note:

Press t and press Enter.

Press 1 and press Enter.

Note: Check the option carefully for the partition type for particular ESX/ESXi version. In ESXi 4.1, option 1 creates FAT32 partition Type. Therefore, select appropriate value for the fb [VMFS] partition type.

Enter fb and press Enter.

Save the changes and exit.

Press w and press Enter.

If fdisk shows a negative number of sectors you can use the parted tool to create the partition:

partedUtil set <diskName> "<partitonNum> <startSector> <endSector> <type> <attribute>"

Using our sample values:

partedUtil set /dev/sdf "1 128 16777215 251 0"

251 is the decimal representation of fb, which is the partition type for VMFS.

Note: In some cases, you may not be able to modify the partition if the LUN is being accessed by virtual machine running on other hosts.

Perform a rescan to read in the new values using one of these methods:

From the ESX console, issue the command: vmkfstools -V

From the vSphere Client:

Click on the ESX host in the inventory.

Click the Configuration tab.

Click Storage adapters.

Rescan for new datastores. You can deselect Scan for New Storage Devices.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

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

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant