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

Recovering a lost partition table on a VMFS volume (1002281)

Last Updated: 9/2/2014Categories: TroubleshootingTotal Views: 129084Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglish

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Details

A VMFS datastore is missing or inaccessible

The missing VMFS datastore's LUN is still presented and detected under the host's Configuration and Storage Adapters view in the VMware vSphere Client or VMware Infrastructure Client.

In the /var/log/vmkernel log file, you see one of these messages:

cpu0)WARNING: SCSI: 6011: SCSI IO to non-existent partition 1, np 5

cpu0)WARNING: SCSI: 5935: returns 0xbad0011 for vmhba0:0:68

cpu0:1031)LVM: 2294: Could not open device , vol [45e3ef74-706b3012-b730-000423cd, 45e3ef74-706b3012-b730-000423cd17ea, 1]: No such partition on target

cpu0:1031)FSS: 343: Failed with status 0xbad0012 for f530 28 1 45e3ef75 b000548 400d1b0 ea17cd23 0 0 0 0 0 0 0

cpu1:1039)WARNING: Vol3: 607: Couldn't read volume header from 4816d0dd-804c9a8c-2c76-001e0beb5f56: Address temporarily unmapped

Solution

Warnings:

This article guides you through recreating the partition table of a LUN that has a VMFS datastore. Ensure that you are familiar with the way VMware ESX identifies disks and LUNs before proceeding. For more information, seeIdentifying disks when working with VMware ESX (1014953).

The steps outlined here are potentially hazardous for your environment if they are not followed exactly. If you are not comfortable performing these steps, contact VMware Technical Support to resolve the issue. For more information, seeHow to Submit a Support Request.

If a LUN does not have a valid partition table, it may not meet the criteria for VMware vCenter and VMware VirtualCenter’s storage filtering safeguards. Refer to your storage configuration or SAN administrator before making any changes, such as creating a VMFS datastore or Raw Device Mapping (RDM), adding an extent, or increasing a VMFS datastore.

ESX 4.x

To recreate the partition table:

Log in to the ESX host service console. For ESXi, see Tech Support Mode for Emergency Support (1003677).

Run the command:

esxcfg-scsidevs -c

The output appears similar to:

Device UID Device Type Console Device Size Plugin Display Name
mpx.vmhba32:C0:T0:L0 CD-ROM /dev/sr0 0MB NMP Local USB CD-ROM (mpx.vmhba32:C0:T0:L0)
mpx.vmhba3:C0:T0:L0 CD-ROM /dev/sr1 0MB NMP Local PLDS CD-ROM (mpx.vmhba3:C0:T0:L0)
naa.50060160bce0383c50060160bce0383c Direct-Access /dev/sdj 0MB NMP DGC Fibre Channel Disk (naa.50060160bce0383c50060160bce0383c)
naa.60024e8056ca2100119f56f605695091 Direct-Access /dev/sdk 139392MB NMP Local DELL Disk (naa.60024e8056ca2100119f56f605695091)
naa.6006016045502500d0c748a4198bde11 Direct-Access /dev/sdh 512000MB NMP DGC Fibre Channel Disk (naa.6006016045502500d0c748a4198bde11)
naa.6006016045502500ec34346d188bde11 Direct-Access /dev/sdi 512000MB NMP DGC Fibre Channel Disk (naa.6006016045502500ec34346d188bde11)
naa.60060160d2ed18012eea2d1ce42ddf11 Direct-Access /dev/sdn 819200MB NMP DGC iSCSI Disk (naa.60060160d2ed18012eea2d1ce42ddf11)
naa.60060160d2ed180176d68215e42ddf11 Direct-Access /dev/sdo 819200MB NMP abcDGC iSCSI Disk (naa.60060160d2ed180176d68215e42ddf11)
naa.60060160d2ed18017ea10024e42ddf11 Direct-Access /dev/sdm 819200MB NMP DGC iSCSI Disk (naa.60060160d2ed18017ea10024e42ddf11)
naa.60060160d2ed180190df110ee42ddf11 Direct-Access /dev/sdp 819200MB NMP logical
naa.600a0b80002666d40000000000000000 Direct-Access /vmfs/devices/disks/naa.600a0b80002666d40000000000000000 20MB NMP IBM Fibre Channel Disk (naa.600a0b80002666d40000000000000000)
naa.600a0b80002666d400003a0a4b99f95c Direct-Access /dev/sdd 102400MB NMP IBM Fibre Channel Disk (naa.600a0b80002666d400003a0a4b99f95c)
naa.600a0b80002666d400003a114b99f9b4 Direct-Access /dev/sdc 102400MB NMP IBM Fibre Channel Disk (naa.600a0b80002666d400003a114b99f9b4)
naa.600a0b80002666d400003a184b99f9ee Direct-Access /dev/sdb 102400MB NMP IBM Fibre Channel Disk (naa.600a0b80002666d400003a184b99f9ee)
naa.600a0b80002901aa0000000000000000 Direct-Access /vmfs/devices/disks/naa.600a0b80002901aa0000000000000000 20MB NMP IBM Fibre Channel Disk (naa.600a0b80002901aa0000000000000000)
naa.600a0b80002901aa0000a11b4a3b51ad Direct-Access /dev/sdg 102400MB NMP IBM Fibre Channel Disk (naa.600a0b80002901aa0000a11b4a3b51ad)
naa.600a0b80002901aa0000a1214a3b51ef Direct-Access /dev/sdf 81920MB NMP IBM Fibre Channel Disk (naa.600a0b80002901aa0000a1214a3b51ef)
naa.600a0b80002901aa0000a1274a3b5231 Direct-Access /dev/sde 71680MB NMP IBM Fibre Channel Disk (naa.600a0b80002901aa0000a1274a3b5231)
naa.600a0b80002901aa0000a3774b99f77d Direct-Access /dev/sda 102400MB NMP IBM Fibre Channel Disk (naa.600a0b80002901aa0000a3774b99f77d)

Identify the disk in question, and note the value under the Console Device column.

Note: There are no Linux console device names in ESXi. In ESXi you use the NAAs, for example: /vmfs/devices/disks/naa.600a0b80002666d40000000000000000.

If you need to map an NAA ID to a VMFS datastore name use the following command:

esxcfg-scsidevs -m

Run the command:

fdisk -l <dev>

Where <dev> is the value recorded in step 2

The output appears similar to:

Disk /dev/sde: 268.4 GB, 268440698880 bytes
255 heads, 63 sectors/track, 32636 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

Start fdisk with this command and press Enter.

fdisk -u <dev>

Where <dev> is the value recorded in step 2.

Create the partition:

Press n and press Enter to create a new partition.

Press p and press Enter to select that this is a primary partition.

Press 1 and press Enter to make the first partition.

Press 128 and Enter to align the partition to sector 128.

Press Enter again to retain the default value.

Change the partition to type fb (VMFS):

Press t and press Enter. Partition 1 is automatically selected.

Enter fb and press Enter.

Press w and press Enter to save.

Run vmkfstools -V and press Enter to discover the VMFS.

ESX 3.x

To recreate the partition table:

Log in to the ESX host service console. For ESXi, seeTech Support Mode for Emergency Support (1003677).

Type esxcfg-vmhbadevs -q and press Enter to get a list of Linux devices and their VMkernel name.

Type fdisk -lu /dev/sdX and press Enter to confirm that the partition is no longer here.

Recreate the partition table:

Start fdisk with the command fdisk -u /dev/sdX and press Enter.

Create the partition:

Press n and press Enter to create a new partition.

Press p and press Enter to select that this is a primary partition.

Press 1 and press Enter to make the first partition.

Press 128 and press Enter to align the partition to sector 128.

Note: If the volume was upgraded from an ESX 2.x , the partition should be aligned to 63, which is the default when using fdisk.

Press Enter to retain the default value.

Change the partition to type fb (VMFS):

Press t and press Enter. Partition 1 is automatically selected.

Enter fb and press Enter.

Type w and press Enter to save. This command exits fdisk and returns you to the command prompt.

Type vmkfstools -V and press Enter to discover the VMFS.

ESX 2.x

To recreate the partition table:

Log in to the ESX host service console.

Typevmkpcidivy -q vmhba_devsand press Enter to get a list of Linux devices and their VMkernel name.

Typefdisk -l /dev/sdXand press Enter to confirm that the partition is no longer here.

Recreate the partition table:

Start fdisk with the commandfdisk /dev/sdXand press Enter.

Create the partition:

Type n and press Enter to create a new partition.

Type p and press Enter to create a primary partition.

Type 1 and press Enter to create the first partition.

Press Enter to keep the default value.

Press Enter to keep the default value.

Change the partition to type fb (VMFS):

Type t and press Enter to change the type of partition.

Type fb and press Enter to set the partition as VMFS.

Type w and press Enter to save.
This command will exit fdisk and returns you to the command prompt.

Typevmkfstools -Vand press Enter to discover the VMFS.

Note: This procedure may not work on VMFS volumes that are participating in a spanned set (extents). Contact VMware Technical Support and work with them to resolve the issue.

If the VMFS datastore does not appear, seeA VMFS volume is not available and the VMkernel log reports the error: Device size mismatch (1003133).

Additional Information

For translated versions of this article, see:

Español : Recuperación de la tabla de particiones de un volúmen VMFS ( 2003927 )

日本語：失われた VMFS ボリュームのパーティション テーブルの復元 （1033156）

Português: Como recuperar uma tabela de partição perdida em um volume VMFS (2039062)

简体中文: 在 VMFS 卷上还原丢失的分区表 (2075631)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglish

Attachments

Additional Resources

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

Result 1 of 1

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 ESX Server 3.5.x

VMware ESX Server 3.0.x

VMware ESX Server 2.5.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