DataNumen logo Header Header
  Site Search:
 
  Home » Products » DataNumen SQL Recovery » SQL Server Errors and Problems » Sql Server Detected A Logical Consistency-Based I/O Error: Torn Page
 
         
 
Arrow DATANUMEN SQL RECOVERY
   
  News
  Recovery
  Download
  Order
  FAQ
  View Screenshot
  Awards
   
Arrow RELATED PRODUCTS
Arrow DataNumen Access Repair
Arrow DataNumen DBF Repair
Arrow DataNumen Database Recovery
Arrow DataNumen Oracle Recovery
 
Detailed Information about "Sql Server Detected A Logical Consistency-Based I/O Error: Torn Page"

Symptom:

When attaching a .MDF database in SQL Server, you see the following error message:

SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0x########; actual signature: 0x#######). It occurred during a read of page (#:#) in database ID # at offset ### in file 'xxxx.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

where 'xxx.mdf' is name of the MDF file being accessed.

Sometimes you the .MDF database may be attached successfully. However, when you try to execute a SQL statement, such as

SELECT * FROM [TestDB].[dbo].[test_table_1]

you will also get the above error message.

Screenshot of error message:

logical consistency-based I/O error: torn page

 

Precise Explanation:

The data in MDF file are stored as pages, each page is 8KB. SQL Server uses two mechanisms to make sure the consistency and integration of the data in the page, that is, checksum or torn page. Both are optional.

If SQL Server finds the torn pages for some of the data pages are invalid, then it will report this error.

You can use our product DataNumen SQL Recovery to recover the data from the corrupt MDF file and solve this error.

 

Sample Files:

Sample corrupt MDF files that will cause the error:

SQL Server version Corrupt MDF file MDF file fixed by DataNumen SQL Recovery
SQL Server 2005 Error5_1.mdf Error5_1_fixed.mdf
SQL Server 2008 R2 Error5_2.mdf Error5_2_fixed.mdf
SQL Server 2012 Error5_3.mdf Error5_3_fixed.mdf
SQL Server 2014 Error5_4.mdf Error5_4_fixed.mdf