A read of the file ‘%ls’ at offset %#016I64x succeeded after failing %d time(s) with error: %ls. Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

Details
Product: SQL Server
Event ID: 825
Source: MSSQLServer
Version: 9.0
Component: SQLEngine
Symbolic Name: B_RETRYWORKED
Message: A read of the file ‘%ls’ at offset %#016I64x succeeded after failing %d time(s) with error: %ls. Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
   
Explanation

This message indicates that the read operation had to be reissued at least one time, and indicates a major problem with the disk hardware. This message does not currently indicate a SQL Server problem, but the disk problem could cause data loss or database corruption if it is not resolved. The system event log may contain related events that help to diagnose the problem. For more information about I/O errors, see
Microsoft SQL Server I/O Basics, Chapter 2http://go.microsoft.com/fwlink/?LinkId=69370
.

   
User Action

The following actions may help you identify and resolve the underlying problem:

Review the error log and the variable text in this message for clues that explain the problem.

Check your disk system. The problem could be related to the disks, the disk controllers, array cards, or disk drivers.

Contact the disk manufacturer for the latest utilities for checking the status of your disk system.

Contact the disk manufacturer for the latest driver updates.

Related:

Leave a Reply