A read operation failed after trying to correct a single-bit error
Applies to: Operations Manager Management Pack for Exchange 2010
Topic Last Modified: 2011-08-22
The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.
To learn more about this alert, in Operations Manager, do one or more of the following:
From the Operations Console, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.
From the Operations Console, double-click this alert, and then click the Alert Context tab. Review the logged events that meet the criteria of this Operations Manager alert.
Details
Product Name |
Exchange |
Product Version |
14.0 (Exchange 2010) |
Event ID |
398 |
Event Source |
ESE |
Category |
KHI |
Alert Type |
Error |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Common Components/Extensible Storage Engine |
Rule Name |
A read operation failed after attempting to correct a single-bit error. This is often caused by driver, firmware, or hardware issues. |
Explanation
This Error event indicates that a database page read failed after the database tried to correct a single-bit error. This event also indicates that the database page that is referenced in the Exchange store file, such as priv1.edb, is corrupted. Event 398 is always associated with a -1018 error.
When this event occurs, you may experience the following symptoms:
Online backups fail to complete, and they report a -1018 error.
Online defragmentation reports a -1018 error.
The occurrence of event 398 indicates damage at the page level of the database. Damage at the page level is almost always caused by driver, firmware, or hardware issues.
User Action
To resolve this problem, do one or more of the following:
Run system diagnostic tests. These tests may not be conclusive if the problem is infrequent and transient, or if the problem occurs only under very complex loads.
Consider migrating to different hardware.
Upgrade the disk controller BIOS and firmware to the latest vendor versions.
Refer to Microsoft Knowledge Base article 314917, Understanding and Analyzing -1018, -1019, and -1022 Exchange database errors.
To repair the database, run the following commands:
eseutil /P
eseutil /D
isinteg -fix
For More Information
If you are not already doing so, consider running the Exchange tools, which have been created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues and improve mail flow. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.