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

Missing SCSI journal on the VMFS-3 datastore (1003925)

Last Updated: 3/6/2010Categories: Total Views: 5239Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

A Windows 2003 virtual machine reports disk I/O errors in the event log. The ESX host VMkernel log contains the following entries:

vmkernel: 30:08:39:04.166 cpu1:1696)WARNING: J3: 1572: Failed to create new txn because journal is unavailable
vmkernel: 30:08:39:04.166 cpu1:1696)WARNING: VSCSI: 2916: Can't translate bad00a4/Host doesn't have a journal to SCSI: using MEDIUM ERROR

When the virtual machine is VMotioned to another ESX host, the I/O errors within the guest and the VMkernel journal errors stop.

If the virtual machine is VMotioned back to the original ESX host, the errors resume.

Resolution

The error bad00a4 means the ESX host can no longer access its journal for a LUN or the journal no longer exists on that LUN.

Every ESX host keeps a journal for each VMFS-3 volume it uses. The journal is written to the LUN. This means that a VMFS-3 volume that is shared by five ESX hosts has five journals written on it.

The bad00a4 errors appear when the journal has been overwritten by another ESX host or the host's journal is lost. The errors stop after the virtual machine has been VMotioned because the new ESX host still has a journal on that volume.

This issue is resolved in ESX 3.5 Update 5 and ESX 4.0.

To workaround the issue:

Migrate all the virtual machines away from the affected ESX host.

Reboot the ESX host. This action re-mounts the volume, which creates a new journal for the host.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware ESX Server

Related Versions:

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