Logical consistency-base I/O error

Question

An error occur as below. Run "DBCC checkDB ([tempdb]) with no_infomsgs" couldn't detect any system error. Everything works as expected. Should we worry about this error? How to troubleshoot it? The SQL version is 2017

SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x0aadf1fa; actual: 0x0aadf1fa). It occurred during a read of page (5:9751051) in database ID 2 at offset 0x00001299416000 in file 'T:\Data\tempdb_mssql_4.ndf'. Additional messages in the SQL Server error log or operating system error 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.

Answer 1

The good news: this is tempdb, so it is less likely that you will get any data corruption persisteed.

But it is still a checksum error. SQL Server some bits to disk and got back some other disks. This suggests that your I/O subsystem is not in best shape, but needs service/replacement. And particularly then then T drive.

Answer 2

Hi @szh8866-8371
Please find below detailed Microsoft document about this event, cause and possible resolution. https://learn.microsoft.com/en-us/sql/relational-databases/errors-events/mssqlserver-824-database-engine-error?view=sql-server-ver16 Thank you!

Answer 3

Hi @szh8866-8371,

Please follow the blog to see if it is helpful.

How to Fix SQL Database Logical Consistency Based I/O Error

Regards，

Zoe Hui

---

If the answer is helpful, please click "Accept Answer" and upvote it.

Answer 4

Bom dia. Td BEm !!!

Estamos com problema de banco corrompido, gera msg :

Object ID 351340316, index ID 0, partition ID 72057594102874112, alloc unit ID 72057594136494080 (type In-row data): Page (1:6598600) could not be processed. See other errors for details.

Msg 8928, Level 16, State 1, Line 7

Executamos o DBCC CHECKDB (nomeDB,REPAIR_REBUILD) WITH NO_INFOMSGS, ALL_ERRORMSGS; porem não foi possivel a reparação. Gera msg :

Object ID 351340316, index ID 0, partition ID 72057594102874112, alloc unit ID 72057594136494080 (type In-row data): Page (1:6598600) could not be processed. See other errors for details.

    The repair level on the DBCC statement caused this repair to be bypassed.

Msg 8928, Level 16, State 1, Line 9

Os backups que temos é do banco ja com problemas. Tentamos fazer o importe das tabelas para um novo banco porem gera a msg :

Msg 824, Level 24, State 2, Line 2

SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x790f37e5; actual: 0x781b37e5). It occurred during a read of page (1:6598584) in database ID 14 at offset 0x00000c95f70000 in file 'E:\SQLData\CHECKDB\DB_DW_CHECKDB.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.

Tem alguma outra forma de recuperação desse banco sem ser executando o REPAIR_ALLOW_DATA_LOSS