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

My Subscriptions

Loading

Knowledge Base

ESX VMkernel log and ESXi messages log contain the messages: WRITE10/READ 10 past end of virtual device (1008661)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 20428Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

The /var/log/vmkernel log on ESX or /var/log/messages log on ESXi contains entries similar to:

Feb 5 15:44:46 <hostname> vmkernel: 63:05:31:58.181 cpu3:1129)WARNING: VSCSI: 5292: WRITE10 past end of virtual device with 33554432 numBlocks, offset 33554351, length 128

Feb 12 17:03:04 <hostname> vmkernel: 156:05:50:47.889 cpu0:1174)WARNING: VSCSI: 3430: READ10 past end of virtual device with 20971520 numBlocks, offset 20980737, length 16

Cause

These messages indicate that I/O outside the boundaries of the virtual disk is being attempted. Specifically, this issue may occur if the end value in the partition table exceeds the number of cylinders set in the descriptor file. The messages do not indicate an error, but if data is written beyond the limits of the disk, it is possible that you may experience data loss.

Impact / Risks

Small possibility of data loss, if data is written beyond the limits of the disk.

Resolution

While this issue is not resolved in VMware ESXi 5.1, Patch ESXi510-201304201-UG: Updates VMware ESXi 5.1 esx-base vib (2041612) it does identify which virtual machine is causing the error by writing the virtual machine name in the error log.

The virtual machine causing the issue is noted in the error message in the /var/log/vmkernel log.

To find out the virtual machine is causing error messages in older builds, generate the log bundle from the ESXi/ESX host on the virtual machine is running. Then contact VMware Technical Support.

Once the virtual machine causing the messages found out by VMware Technical Support, verify the source of the error:

Open the descriptor file for the virtual machine that is triggering the messages.

Look for the entry that lists the number of cylinders for the virtual disk. In this example, the virtual disk has 5221 cylinders:

ddb.geometry.cylinders = "5221"

Run this command against the flat file of the virtual disk:

fdisk -l

Note: To ensure that the -flat file is not locked, only run this command on a virtual machine that is powered off or has at least one snapshot.

The output appears similar to:

Disk ANSGOOD-flat.vmdk: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
ANSGOOD-flat.vmdk1 * 1 5222 41940992 7 HPFS/NTFS
Partition 1 has different physical/logical endings:
phys=(1023, 254, 63) logical=(5221, 137, 36)

In this example, the end value for the partition table is 5222. This value exceeds the number of cylinders set in the descriptor file (in this case, 5221).

To resolve this issue, extend the disk with the vmkfstools -X command to, or beyond, the discovered boundary from above. For more information, see Adding space to an ESX host virtual disk (994).

Alternatively if there has been no perceivable data loss or problems in the guest operating system, you may opt to create a new virtual disk of the intended size, attach it to the virtual machine, and migrate data to the new disk manually within the Guest operating system.

This issue commonly occurs with Windows 7 and Windows 2008 virtual machines. If you run the command msinfo32., and expand Components > Storage and highlight Disks, you can see results similar to this for the same virtual machine:

Size: 39.99 Gb (42,944,186,880 bytes)

Total Cylinders: 5,221

Total Sectors: 83,875,365

Total Tracks: 1,331,355

Tracks/Cylinder: 255

Partition: Disk #0, Partition #0

Partition Size: 40.00 Gb (42,947,575,808 bytes)

Partition Starting Offset: 1,048,576 bytes

You can work out the over allocation by adding the Partition Starting Offset to the Partition Size and subtracting this from the Size. For example:

42,944,186,880 - (1,048,576+42,947,575,808) = -4,437,504 bytes

Related Information

VMware ESXi 5.1, Patch ESXi510-201304201-UG: Updates VMware ESXi 5.1 esx-base vib

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
•
损坏的 esx.conf 文件阻止显示网络设置 (1004451)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
VMware Consolidated Backup のインストール手順 (1010092)

Results 1-4 of 4

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 vSphere ESXi 5.1

VMware vSphere ESXi 5.0

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