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

Unable to access the VMware virtual machine file system datastore when the partition is missing or is not set to type fb (1002168)

Last Updated: 1/16/2014Categories: TroubleshootingTotal Views: 19975Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

Unable to access the virtual machine file system (VMFS) datastore. The partition is not set to type fb.

Unable to access the VMFS datastore. No VMFS partition table on the LUN.

Affected volumes are showing up with a partition type of 42 (SFS). Verify this by running fdisk -l from the service console.

Error message in the log /var/log/vmkernel :

Aug 22 15:55:44 esx01 vmkernel: 145:20:59:19.562 cpu1:1037)WARNING: SCSI: 6693: Partition vmhba3:0:12:1 is active: partition table was not updated

Solution

The Consolidated Backup proxy server is the only Windows server that can see the VMFS volumes.

When the automatic drive letter assignment function (automount) is enabled within diskpart on the VMware Consolidated Backup (VCB) proxy (default setting), the Windows diskpart initializes the volume on discovery and autoassigns a driveletter to the volume which results in the change of the partition type to 42 (SFS) and ESX losing access to the datastore volume.

To setup VCB properly, see Virtual Machine Backup Guide.

After the VCB proxy configuration is corrected, log in to the ESX console and double-check which volumes are affected.

This example shows how the partition looks after being connected to VCB proxy where diskpart autoassigned the drive letter and changed the partition type to 42 (SFS):

[root@localhost root]# fdisk -lu

To correct this issue, change the partition type back to fb on all the LUNs that are supposed to be VMFS datastores.
For more information, see Recovering a lost partition table on a VMFS Volume (1002281).

Warning: The SFS volumes may be legitimate Dynamic Disks in windows presented as RDMs. Make sure to verify that they are not RDMs presented to Windows OS as Dynamic Disks.

The following step must be performed only after creating backups as the result might lead to complete data loss.

After this change, perform a rescan.

[root@localhost root]# esxcfg-rescan vmhba1

If the volume does not appear as VMFS datastore on the ESX, you may need to align the partition start to the block 128 as this is the default when ESX does create partitions and this is another aspect that Windows does change when initializing the discovered volume.

To set the starting sector to 128 instead of 63 (the default) on the ESX host.

First to confirm that the current Start is 63

This is how the actual change from 63 to 128 is performed.

This is the result after successfully changed.

Rescan at this point and the volume appears on the ESX as VMFS datastore.

[root@localhost root]# esxcfg-rescan vmhba1

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
ESXi/ESX エラー： デバイスに空き領域が残っていません (1007638)

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

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware ESX Server

VMware Consolidated Backup

Related Versions:

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

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