SQL Server I/O device Error !!!, Sqlserver
In the file 'd: \ data \ BooksDB. during the read operation at the offset of 0x0000011d10400 in mdf, the operating system has returned error 1117 to SQL Server (unable to run this request due to an I/O device error) the SQL Server Error Log and other messages in the System Event Log may provide more details. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Perform a complete database consistency check (dbcc checkdb ). This error can be caused by many factors. For more information, see SQL Server books online.
Result of dbcc checkdb:
Message 8966, level 16, status 2, 1st rows
You cannot use the lock type SH to read and lock the page (1: 583810 ). 1117 (unable to run this request due to an I/O device error .) Failed.
Message 8978, level 16, state 1, 1st rows
Table error: Object ID 1690489101, index ID 22, partition ID 72057594089570304, allocation unit ID 72057594094288896 (type: In-row data ). Page (1: 470146) does not reference the previous page (1: 583810. It may be because of link problems.
Message 2533, level 16, state 1, 1st rows
Table error: unable to see the page (1: 1690489101) allocated to the Object ID 72057594089570304, index ID 22, partition ID 72057594094288896, allocation unit ID 583810 (type: In-row data ). This page may be invalid, or the page header may contain incorrect allocation unit ID.
Message 8976, level 16, state 1, 1st rows
Table error: Object ID 1690489101, index ID 22, partition ID 72057594089570304, allocation unit ID 72057594094288896 (type: In-row data ). No page (1: 583810) was found during the scan, but its parent level (1: 70834) and previous page (1: 685949) both referenced it. Check previous error messages.
There are 1089 rows in the 66867 page of the object 't_in_top.
CHECKDB finds 0 allocation errors and 3 consistency errors in the table 't_in_top '(Object ID 1690489101.
Please help me!
Copyright Disclaimer: This article is an original article by the blogger and cannot be reproduced without the permission of the blogger.