Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

Datastore will not mount or LUN resignaturing fails with error "Invalid datastore format" (68135)

Last Updated: 2/22/2024Categories: TroubleshootingTotal Views: 16981Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Datastore will not mount

Datastore re-signature fails with error "Invalid datastore format"

hostd.log shows

2019-02-07T05:34:17.300Z info hostd[2099664] [Originator@6876 sub=Vimsvc.TaskManager opID=AddDatastoreWizard-add-23584-ngc:70002264-ec-44-a114 user=vpxuser:Administrator] Task Created : haTask-ha-host-vim.host.DatastoreSystem.resignatureUnresolvedVmfsVolume-1817572049
2019-02-07T05:34:17.300Z info hostd[2395423] [Originator@6876 sub=Libs opID=AddDatastoreWizard-add-23584-ngc:70002264-ec-44-a114 user=vpxuser:Administrator] UnresolvedVmfsVolumeNoSnapShotCache::_Populate: Getting list of UnresolvedVmfsVolume
2019-02-07T05:34:17.315Z info hostd[2395423] [Originator@6876 sub=Libs opID=AddDatastoreWizard-add-23584-ngc:70002264-ec-44-a114 user=vpxuser:Administrator] UnresolvedVmfsVolume: deviceName=naa.600000e00d2c0000002c043b00030000:1,lvmName=5c4446e4-cb507084-911e-4c526214afa0,label=DatastoreName(VMFS),fsUuid=5c4446e4-d9d9fa4a-9dc1-4c526214afa0
2019-02-07T05:34:17.384Z warning hostd[2395423] [Originator@6876 sub=Libs opID=AddDatastoreWizard-add-23584-ngc:70002264-ec-44-a114 user=vpxuser:Administrator] VmFileSystem: Unable to get device properties for volume / device
2019-02-07T05:34:17.385Z info hostd[2395423] [Originator@6876 sub=Vimsvc.TaskManager opID=AddDatastoreWizard-add-23584-ngc:70002264-ec-44-a114 user=vpxuser:Administrator] Task Completed : haTask-ha-host-vim.host.DatastoreSystem.resignatureUnresolvedVmfsVolume-1817572049 Status error
2019-02-07T05:34:17.329Z info hostd[2100090] [Originator@6876 sub=Hostsvc.DatastoreSystem] LvmUpdate: got LVM message [N11HostdCommon17VmkernelUpdateLvmE:0x000000bc825341d0] timestamp=944676853788 discovered=true name=[LikewiseGetDomainJoinInfo:354] QueryInformation(): ERROR_FILE_NOT_FOUND (2/0):

vmkernel.log shows

2019-02-07T05:34:17.362Z cpu50:2395423 opID=40e292ac)WARNING: NFS: 1227: Invalid volume UUID snap-06c78f99-5c4446e4-cb507084-911e-4c526214afa0
2019-02-07T05:34:17.367Z cpu50:2395423 opID=40e292ac)WARNING: Vol3: 3102: DatastoreName/5c4446e4-d9d9fa4a-9dc1-4c526214afa0: Invalid physDiskBlockSize 512
2019-02-07T05:34:17.373Z cpu50:2395423 opID=40e292ac)WARNING: Vol3: 3102: DatastoreName/5c4446e4-d9d9fa4a-9dc1-4c526214afa0: Invalid physDiskBlockSize 512
2019-02-07T05:34:17.376Z cpu50:2395423 opID=40e292ac)WARNING: Vol3: 3102: DatastoreName/5c4446e4-d9d9fa4a-9dc1-4c526214afa0: Invalid physDiskBlockSize 512
2019-02-07T05:34:17.380Z cpu50:2395423 opID=40e292ac)WARNING: Vol3: 3102: DatastoreName/5c4446e4-d9d9fa4a-9dc1-4c526214afa0: Invalid physDiskBlockSize 512
2019-02-07T05:34:17.384Z cpu50:2395423 opID=40e292ac)FSS: 6092: No FS driver claimed device 'snap-06c78f99-5c4446e4-cb507084-911e-4c526214afa0': No filesystem on the device

vCenter vpxd.log shows

2019-02-07T13:34:23.079+08:00 info vpxd[12272] [Originator@6876 sub=Default opID=AddDatastoreWizard-add-23584-ngc:70002264-ec] [VpxLRO] -- ERROR task-1147 -- datastoreSystem-29 -- vim.host.DatastoreSystem.resignatureUnresolvedVmfsVolume: vim.fault.InvalidDatastore:
-- > Result:
-- > (vim.fault.InvalidDatastore) {
-- > faultCause = (vmodl.MethodFault) null,
-- > faultMessage = < unset >,
-- > datastore = < unset >,
-- > name = ""
-- > msg = "Invalid datastore format ''."
-- > }
-- > Args:
-- >
-- > Arg resolutionSpec:
-- > (vim.host.UnresolvedVmfsResignatureSpec) {
-- > extentDevicePath = (string) [
-- > "/vmfs/devices/disks/naa.600000e00d2c0000002c043b00030000:1"
-- > ]
-- > }

Running esxcli storage core device capacity list shows  similar to below

Device                                                 Physical Blocksize    Logical Blocksize        Logical Block Count        Size Format          Type

-------------------- ------------------ ----------------- ------------------- ----------- -----------

naa.600000e00d2800000028087800030000     512                           512                               209715200                102400 MiB             512n
naa.600000e00d2800000028087800010000     4096                         512                               734003200                358400 MiB             512e
naa.600000e00d2800000028087800080000     4096                         512                               209715200                102400 MiB             512e

Note: The preceding log excerpts are only examples. Date,time and environmental variables may vary depending on your environment.

Cause

This happens when original LUN and Backup LUN physical block size/sector format  is different.

Impact / Risks

ESXi host reboot is required once upgraded.

Resolution

This issue is  fixed in ESXi6.7U1. Upgrade the ESXi hosts to 6.7 U1 or later.

To  download  ESXi 6.7 U1 go to Customer Connect download

Related Information

For more information on device sector formats refer to VMware documentation
For more  information on LUN resignaturing refer to vSphere handling of LUNs detected as snapshot LUNs

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
•
因 pod-startup.log 文件过多，导致 vCenter Appliance /storage/log 分区过满 (80803)

KB
•
Download and Install VMware Fusion (2014097)

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 ESXi

Related Versions:

VMware vSphere ESXi 6.7

VMware ESXi 6.7.x

Take Our Survey

Support Assistant