We started receiving these error messages suddenly
Error: 824, Severity: 24, State: 2.
Message
SQL Server detected a logical consistency-based I/O error: invalid protection option. It occurred during a read of page (7:8192) in database ID 2 at offset 0x00000004000000 in file 'X:\tempdb\tempdb_mssql_6.ndf'. 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.
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x31333637; actual: 0x9c88f38a). It occurred during a read of page (7:8216) in database ID 2 at offset 0x00000004030000 in file 'X:tempdb\tempdb_mssql_6.ndf'.
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.
An error occurred while processing the log for database 'tempdb'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
During undoing of a logged operation in database 'tempdb', an error occurred at log record ID (239:1702646:104). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or
repair the database.
SQL Server must shut down in order to recover a database (database ID 2). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore
the database.
------
After these messages, i had to start SQL services manually, however the errors continued
Error while allocating extent for a worktable. Extent (6:16248) in TEMPDB may have been lost.
-------
I ran DBCC CHECKDB(tempdb) --- no results.....
Checked with storage team for health checks, they say no issue.
However, i see many suspect_pages recorded for this DB and it even got recorded before the server crash too.
database_id | file_id | page_id | event_type | error_count |
2 | 7 | 40440 | 1 | 106 |
2 | 4 | 40440 | 1 | 4759 |
2 | 4 | 511232 | 1 | 1 |
2 | 7 | 8216 | 2 | 1 |
2 | 7 | 8192 | 1 | 1 |
2 | 6 | 16176 | 1 | 1935 |
2 | 7 | 8088 | 1 | 18 |
then i had to manually delete the tempdb files and restart SQL services. Errors stopped and DB health is OK.
Trying to investigate the root cause, any pointers/advise is really appreciable. Thanks in advance.