%1 (%2) %3The database page read from the file “%4” at offset %5 (database page %9) for %6 bytes failed verification. Bit %8 was corrupted and was corrected but page verification failed with error %7. This problem is likely due to faulty hardware and may continue. Transient failures such as these can be a precursor to a catastrophic failure in the storage subsystem containing this file. Please contact your hardware vendor for further assistance diagnosing the problem.

Details
Product: Exchange
Event ID: 398
Source: ESE
Version: 8.0
Symbolic Name: DATABASE_PAGE_CHECK_FAILED_ID
Message: %1 (%2) %3The database page read from the file “%4” at offset %5 (database page %9) for %6 bytes failed verification. Bit %8 was corrupted and was corrected but page verification failed with error %7. This problem is likely due to faulty hardware and may continue. Transient failures such as these can be a precursor to a catastrophic failure in the storage subsystem containing this file. Please contact your hardware vendor for further assistance diagnosing the problem.
   
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.

Related:

Leave a Reply