%1 (%2) %3Database %4: Page %5 failed verification due to a timestamp mismatch at log position %10. The remote ("before") timestamp persisted to the log record was %6 but the actual timestamp on the page was %7 (note: DbtimeCurrent = %9). This indicates the active node lost a flush (error %8). This problem is likely due to faulty hardware "losing" one or more flushes on this page sometime in the past on the active node. Please contact your hardware vendor for further assistance diagnosing the problem.
For more information, click http://www.microsoft.com/contentredirect.asp.
Database %4 was partially detached. Error %5 encountered updating database headers. For more information, click http://w ...
Database %4: Page %5 (objid %6) has a logical corruption of type '%7'. For more information, click http://www.microsoft.com/contentredirect.asp. ...
Database %4: Page %5 failed verification due to a flush-order dependency mismatch. This page should have flushed before page ...
Database %4: Page %5 failed verification due to a timestamp mismatch at log position %10. The 'before' timestamp persisted ...
Database %4: Page %5 failed verification due to a timestamp mismatch at log position %10. The remote ("before") timestamp ...
Database %4: Page %5 failed verification due to a timestamp mismatch at log position %10. The remote ("before") timestamp ...
Database %4: Page %5 logical data checksum %6 failed to match logged scan check %7 checksum (seed %8) at log position %9. ...
Database %4: Page %5 was shown to be uninitialized at log position %8, while the remote ("before") timestamp persisted to ...
Database %6: Index %4 of table %5 is corrupted (%7). For more information, click http://www.microsoft.com/contentredirect.asp. ...