A read operation failed after attempting to correct a single-bit error
Topic Last Modified: 2007-11-16
The Microsoft Exchange Server 2007 Management Pack for Microsoft Operations Manager (MOM) monitors the Windows Event log on computers that are running Exchange Server 2007 and generates this alert when the event or events specified in the following Details table are logged.
To learn more about this event, do one or more of the following:
Review the description of the event that includes the variables specific to your environment. From the MOM Operator Console, select this alert, and then click the Properties tab.
Review all events that have been logged that meet the criteria of this MOM alert. From the MOM Operator Console, click the Events tab, and then double-click the event in the list for which you want to review the event description.
Details
Product Name |
Exchange |
Product Version |
8.0 (Exchange Server 2007) |
Event ID |
398 |
Event Source |
ESE |
Alert Type |
Critical Error |
MOM Rule Path |
Microsoft Exchange Server/Exchange 2007/Common Components/Extensible Storage Engine |
MOM Rule Name |
A read operation failed after attempting to correct a single-bit error. This is often caused by driver, firmware, or hardware issues. Run diagnostic tests on your storage hardware. |
Explanation
This Error event indicates that a database page read failed after attempting to correct a single-bit error. The particular database page referenced within the Exchange store file such as priv1.edb is corrupt. Event 398 is always associated with a -1018 error in the Description section of the Event.
Here are possible symptoms:
Online backups fail to complete and report a -1018 error.
Online defragmentation reports a -1018 error.
Occurrence of event 398 indicates damage at the page level of the database. Damage at the page level is caused by driver, firmware, or hardware issues 99% of the time.
User Action
To resolve this Error event, 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 only appears under very complex loads.
Consider migrating to different hardware.
Upgrade disk controller BIOS and firmware to the latest vendor revisions.
Refer to Microsoft Knowledge Base article 314917, Understanding and Analyzing -1018, -1019, and -1022 Exchange database errors.
Repair the database by running eseutil /P, eseutil /D, and then isinteg -fix.
For More Information
To search the Microsoft Knowledge Base articles based on criteria that generated this alert, visit the Search the Support Knowledge Base (KB) Web site.
To review Exchange 2007 event message articles that may not be represented by Exchange 2007 MOM alerts, see the Events and Errors Message Center.
If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.