﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2008 / Data Corruption (SS2K8 / SS2K8 R2)  / SQL Server detected a logical consistency-based I/O error / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Wed, 22 May 2013 14:23:16 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: SQL Server detected a logical consistency-based I/O error</title><link>http://www.sqlservercentral.com/Forums/Topic1401754-2893-1.aspx</link><description>Thank you very much ...--Krishna</description><pubDate>Fri, 11 Jan 2013 03:03:45 GMT</pubDate><dc:creator>krishnaprasad14</dc:creator></item><item><title>RE: SQL Server detected a logical consistency-based I/O error</title><link>http://www.sqlservercentral.com/Forums/Topic1401754-2893-1.aspx</link><description>Please check this article: http://support.microsoft.com/kb/2015756</description><pubDate>Thu, 10 Jan 2013 22:11:28 GMT</pubDate><dc:creator>prettsons</dc:creator></item><item><title>RE: SQL Server detected a logical consistency-based I/O error</title><link>http://www.sqlservercentral.com/Forums/Topic1401754-2893-1.aspx</link><description>Hi Gail Shaw,I did restore from healthy backup and it's fine now...Thank you --Krishna</description><pubDate>Thu, 03 Jan 2013 03:29:00 GMT</pubDate><dc:creator>krishnaprasad14</dc:creator></item><item><title>RE: SQL Server detected a logical consistency-based I/O error</title><link>http://www.sqlservercentral.com/Forums/Topic1401754-2893-1.aspx</link><description>Restore from a clean backup, that's not repairable in any way.</description><pubDate>Wed, 02 Jan 2013 06:27:41 GMT</pubDate><dc:creator>GilaMonster</dc:creator></item><item><title>RE: SQL Server detected a logical consistency-based I/O error</title><link>http://www.sqlservercentral.com/Forums/Topic1401754-2893-1.aspx</link><description>You are right. Thank you. I miss two lines ..Here is the complete error message...Please let me know if you need any other details........Msg 8946, Level 16, State 12, Line 1Table error: Allocation page (1:145584) has invalid PFS_PAGE page header values. Type is 0. Check type, alloc unit ID and page ID on the page.Msg 8921, Level 16, State 1, Line 1Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.Msg 8998, Level 16, State 2, Line 1Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 46 pages from (1:145584) to (1:153671). See other errors for cause.Msg 8909, Level 16, State 1, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594050707456 (type Unknown), page ID (1:145584) contains an incorrect page ID in its page header. The PageId in the page header = (1:70728).Msg 8909, Level 16, State 1, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594050707456 (type Unknown), page ID (1:145584) contains an incorrect page ID in its page header. The PageId in the page header = (1:70728).CHECKDB found 2 allocation errors and 1 consistency errors not associated with any single object.CHECKDB found 2 allocation errors and 1 consistency errors in database 'WSS_Content_HeartyLivesV2'.Thank you,Krishna</description><pubDate>Wed, 02 Jan 2013 05:26:23 GMT</pubDate><dc:creator>krishnaprasad14</dc:creator></item><item><title>RE: SQL Server detected a logical consistency-based I/O error</title><link>http://www.sqlservercentral.com/Forums/Topic1401754-2893-1.aspx</link><description>You are right. Thank you. I miss two lines ..Here is the complete error message...Please let me know if you need any other details........Msg 8946, Level 16, State 12, Line 1Table error: Allocation page (1:145584) has invalid PFS_PAGE page header values. Type is 0. Check type, alloc unit ID and page ID on the page.Msg 8921, Level 16, State 1, Line 1Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.Msg 8998, Level 16, State 2, Line 1Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 46 pages from (1:145584) to (1:153671). See other errors for cause.Msg 8909, Level 16, State 1, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594050707456 (type Unknown), page ID (1:145584) contains an incorrect page ID in its page header. The PageId in the page header = (1:70728).Msg 8909, Level 16, State 1, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594050707456 (type Unknown), page ID (1:145584) contains an incorrect page ID in its page header. The PageId in the page header = (1:70728).CHECKDB found 2 allocation errors and 1 consistency errors not associated with any single object.CHECKDB found 2 allocation errors and 1 consistency errors in database 'WSS_Content_HeartyLivesV2'.Thank you,Krishna</description><pubDate>Wed, 02 Jan 2013 05:26:10 GMT</pubDate><dc:creator>krishnaprasad14</dc:creator></item><item><title>RE: SQL Server detected a logical consistency-based I/O error</title><link>http://www.sqlservercentral.com/Forums/Topic1401754-2893-1.aspx</link><description>Please post the full and complete, unedited output of that command (you've left out at least one line, possibly more)</description><pubDate>Wed, 02 Jan 2013 05:11:09 GMT</pubDate><dc:creator>GilaMonster</dc:creator></item><item><title>SQL Server detected a logical consistency-based I/O error</title><link>http://www.sqlservercentral.com/Forums/Topic1401754-2893-1.aspx</link><description>--Error Number 824DESCRIPTION:	SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:845407; actual 1:607839). It occurred during a read of page (1:845407) in database ID 46 at offset 0x0000019ccbe000 in file ‘xx.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.--If run this , I am getting below specified error message DBCC CHECKDB ('DBname') WITH NO_INFOMSGS, ALL_ERRORMSGS--Error message:Msg 8946, Level 16, State 12, Line 1Table error: Allocation page (1:145584) has invalid PFS_PAGE page header values. Type is 0. Check type, alloc unit ID and page ID on the page.Msg 8921, Level 16, State 1, Line 1Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.Msg 8998, Level 16, State 2, Line 1Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 6 pages from (1:145584) to (1:153671). See other errors for cause.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594050707456 (type Unknown), page (1:145584). Test (IS_OFF (BUF_IOERR, pBUF-&amp;gt;bstat)) failed. Values are 62916617 and -4.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594050707456 (type Unknown), page (1:145584). Test (IS_OFF (BUF_IOERR, pBUF-&amp;gt;bstat)) failed. Values are 62916617 and -4.Can you suggest me to resolve this please….Can you please let me know if you need any other details….Thank you in Advance…..Krishna</description><pubDate>Wed, 02 Jan 2013 04:04:59 GMT</pubDate><dc:creator>krishnaprasad14</dc:creator></item></channel></rss>