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

Virtual machines fail to power on with a "Bad address" error after rebooting the ESX host (1000881)

Last Updated: 1/9/2014Categories: TroubleshootingTotal Views: 29116Language:
English

5 like this article

Subscribe to get an email
newsletter with new updates

5 people found this helpful Please provide article feedback:

Details

After rebooting the ESX host, some virtual machines fail to power on and the VMDK files do not open

You see the error:

[2007-06-03 17:58:58.203 'vm:/vmfs/volumes/459bc363-204e26e4-a2bf-0018717988b8/My_Test_VM/My_Test_VM.vmx' 7977904 info] Question info: Cannot open the disk '/vmfs/volumes/459bc363-204e26e4-a2bf-0018717988b8/My_Test_VM/My_Test_VM-000002.vmdk' or one of the snapshot disks it depends on. Reason: Bad address., Id: 0 : Type : 2, Default: 0, Number of options: 1

Note: You see this error in VMware Infrastructure (VI) Client and in / var/log/vmware/hostd-0.log when you try to power on the virtual machines, and if you try to clone a virtual disk using vmkfstools -i.

/var/log/vmkernel contains the following entry, which identifies an inaccessible device:

Jun 3 21:04:08 my_esx_svr1 vmkernel: 0:00:14:38.197 cpu2:1034)ALERT: LVM: 1355: One or more devices not found (file system [My_VMFS_storage, 459bc363-204e26e4-a2bf-0018717988b8])

The output of the vmkfstools -P <datastore> command shows one or more extents are missing from the datastore:

#vmkfstools -P /vmfs/volumes/My_VMFS_Storage

VMFS-3.21 file system spanning 1 partitions.
File system label (if any): My_VMFS_Storage
Mode: public
Capacity 1174136684544 (1119744 file blocks * 1048576), 73270296576 (69876 blocks) avail
UUID: 459bc363-204e26e4-a2bf-0018717988b8
Partitions spanned:
vmhba0:0:1:1
(One or more partitions spanned by this volume may be offline)

Solution

This issue can occur if a VMFS volume is spanned over multiple LUNs and one or more of the extents is missing or corrupted.

In this scenario, if some LUNs go offline and only a few come back up again, the ESX host's /var/log/vmkernel log file identifies the LUNs that have LVM volumes missing. For example:

Jun 3 21:38:35 my_esx_svr1 vmkernel: 0:00:01:04.626 cpu3:1034)ALERT: LVM: 1355: One or more devices not found (file system [My_VMFS_Storage, 459bc363-204e26e4-a2bf-0018717988b8])

My_VMFS_storage is the VMFS datastore that is missing extents. Any virtual disks that are partially contained on missing extents are inconsistent. ESX hosts cannot open inconsistent virtual disk files. When you try to power on the virtual machine, you see the error:

[2007-06-03 17:58:58.203 'vm:/vmfs/volumes/459bc363-204e26e4-a2bf-0018717988b8/My_Test_VM/My_Test_VM.vmx' 7977904 info] Question info: Cannot open the disk '/vmfs/volumes/459bc363-204e26e4-a2bf-0018717988b8/My_Test_VM/My_Test_VM-000002.vmdk' or one of the snapshot disks it depends on. Reason: Bad address., Id: 0 : Type : 2, Default: 0, Number of options: 1

To check if a VMFS volume has all its VMFS extents, run the command:

# vmkfstools -P /vmfs/volumes/My_VMFS_Storage

The output appears similar to:

VMFS-3.21 file system spanning 1 partitions.
File system label (if any): My_VMFS_Storage
Mode: public
Capacity 1174136684544 (1119744 file blocks * 1048576), 73270296576 (69876 blocks) avail
UUID: 459bc363-204e26e4-a2bf-0018717988b8
Partitions spanned:
vmhba0:0:1:1
(One or more partitions spanned by this volume may be offline)

This output indicates that the VMFS volume My_VMFS_Storage spans across more than one extent and that they are missing. The extents can be VMFS partitions on this same LUN or other LUNs.

If vmkfstools -P shows that any extents are missing, do no reboot the host or perform a storage rescan. Rebooting the hosts that access the missing, inaccessible, or corrupted VMFS extents removes the virtual machines running in the missing extents from the cache. As long as the ESX host has not rebooted and as long as the SAN has not been rescanned, VMware Technical Support may be able to recover the data within the VMFS extent(s). VMware recommends that you migrate all working virtual machines away from the affected volume.

You must collect a dump of the first MB of the applicable device to give to VMware Technical Support.

To collect a dump:

Run the following command to identify the mapping of the vmhba name and the /dev node:

esxcfg-vmhbadevs -q

Note: In this example, the device is /dev/sda.

Create metadata dumps from the main LUN with the command:

dd if=/dev/sda of=/tmp/sda.bin bs=1k count=32768
md5sum /tmp/sda.bin > /tmp/sda.bin.md5sum

Collect the metadata dumps from the VMFS partition(s) on this LUN with the commands:

dd if=/dev/sda1 of=/tmp/sda1.bin bs=1k count=32768
md5sum /tmp/sda1.bin > /tmp/sda1.bin.md5sum

dd if=/dev/sda2 of=/tmp/sda2.bin bs=1k count=32768
md5sum /tmp/sda2.bin > /tmp/sda2.bin.md5sum

These commands create a binary dump image files and md5sum signature from the LUN any VMFS partitions in it. The md5sum signature is important to collect to insure the integrity of the binary dump files during the SFTP/FTP transfer to VMware Technical Support.

Provide this information to VMware Technical Support. For more information, see Uploading diagnostic information to VMware (1008525).

If the virtual machines are accessible via RDP, try using VMware Converter to move the virtual machines to another datastore. VMware Technical Support may be able to run backup software within the virtual machine to get data off.

To prevent this issue, implement two-member zoning on the Fabric Switch to ensure that you do not receive LIP / RSCN resets when any host accessing shared LUNs is rebooted. Excessive SCSI bus resets can cause LUN corruption. Two-member zoning is a zone that contains a single initiator and a single target. This means that a single ESX host with four paths to the array is contained in four zones, one per initiator/target pair.

For related information, see Virtual machine is unresponsive and Event IDs 11 and 15 occur in the Windows guest operating system Event log (1005204).

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
vNetwork Distributed Switch 上のプライベート VLAN (PVLAN) - コンセプトの概要 (1010691)

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 VirtualCenter

VMware ESX Server

Related Versions:

VMware VirtualCenter 2.0.x

VMware VirtualCenter 1.4.x

VMware ESX Server 3.0.x

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