Quantcast
Channel: SQLServerCentral » SQL Server 2008 » Data Corruption (SS2K8 / SS2K8 R2) » Latest topics
Viewing all articles
Browse latest Browse all 223

Incorrect checksum error information describes a correct checksum?

$
0
0
I've been hitting a problem where a CREATE INDEX is failing. The debug error exception shows the error is invalid because expected and actual are a match, not a miss-match. This is killing me. I've flattened and re-created the entire database (file groups, files, tables) and can't get past this. Any tips on how to handle this? The server is Windows 2012 R2, Sql Server 2014 Enterprise w/sp1. Vertex 3 SSD's..NET Exception Message:The operating system returned error incorrect checksum ([b]expected: 0x2ca0d355; actual: 0x2ca0d355[/b]) to SQL Server during a read at offset 0x0000007605c000 in file 'h:\SqlSvr\Data\ClusterIdx.ndf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level 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.Could not create constraint or index. See previous errors.The statement has been terminated.Output from CHECKDB"CHECKDB found 0 allocation errors and 0 consistency errors in database 'EVRoute'.DBCC execution completed. If DBCC printed error messages, contact your system administrator."

Viewing all articles
Browse latest Browse all 223

Trending Articles