%1 (%2) %3Database %4: Page %5 failed verification due to a timestamp mismatch at log position %10. The 'before' timestamp persisted to the log record was %6 but the actual timestamp on the page was %7. The 'after' update timestamp %9 that would have updated the on page timestamp. Recovery/restore will fail with error %8. If this condition persists then please restore the database from a previous backup. This problem is likely due to faulty hardware "losing" one or more flushes on this page sometime in the past. Please contact your hardware vendor for further assistance diagnosing the problem. For more information, click http://www.microsoft.com/contentredirect.asp.
Database %4 requires logfiles %5-%6 in order to recover successfully. Recovery could only locate logfiles starting at %7. ...
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 ...