Using virtual host drivers could lead to data consistency problems with the SQL Server Database Engine


Symptoms


On an instance of SQL Server, one or more of the following errors may be logged in the SQL Server error log or in the Application log:

Error1:

Error 824 : SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:425920; actual 65535:0). It occurred during a read of page (1:425920) in database ID 2 at offset 0x000000cff80000 in file 'D:\DBName.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.

Error 2:

2011-02-24 00:20:32.55 spid65      Error: 605, Severity: 21, State: 3.
2011-02-24 00:20:32.55 spid65      Attempt to fetch logical page (1:17479052) in database 8 failed. It belongs to allocation unit 0 not to 72057610609819648.

Error 3:

Error 823   The operating system returned error incorrect pageid (expected 1:306208; actual 65535:0) to SQL Server during a read at offset 0x00000095840000 in file 'R:\DBName.mdf'. 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.

Error 4:

Error 18400  The background checkpoint thread has encountered an unrecoverable error. The checkpoint process is terminating so that the thread can clean up its resources. This is an informational message only. No user action is required.

Error 5:

Backup detected log corruption in database DBName. Context is FirstSector. LogFile: 2 'R:\DBName.LDF' VLF SeqNo: x3c1c3 VLFBase: x6a850000 LogBlockOffset: x6bbcde00 SectorStatus: 2 LogBlock.StartLsn.SeqNo: x560053 LogBlock.StartLsn.Blk: x2d0043 Size: x53 PrevSize: x5c.

Additionally, if you run the DBCC CHECKDB command, it may indicate database consistency problems.

Cause


This problem may occur if you use the following virtual host driver:

Driver Name: [C:\WINDOWS\SYSTEM32\DRIVERS\XGVHBA.SYS] 
Vendor Name:      Xsigo Systems

The driver's vendor has determined that the problem with versions 2.6.0.0 and 2.7.1.0.

Resolution


Contact the vendor of this driver to obtain the fixed version 2.7.3.0 or a later version. Update the drivers for the Xsigo Virtual HBA adapters.

More Information


The following table provides more information on the products or tools that automatically check for this condition on your instance of SQL Server and the versions of the SQL Server product that the rule is evaluated against.

 

Rule softwareRule titleRule descriptionProduct versions  against which the rule is evaluated
System Center AdvisorVirtual host driver detected that this can cause stability problems for SQL ServerSystem Center Advisor checks if the driver is present in the system. If it is present, then Advisor generates an alert if the file version of the driver is earlier than the fixed version.SQL Server 2008
SQL Server 2008 R2


For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

2015756 How to troubleshoot Msg 824 in SQL Server

2015755 How to troubleshoot a Msg 823 error in SQL Server 

 

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

The information and the solution in this document represents the current view of Microsoft Corporation on these issues as of the date of publication. This solution is available through Microsoft or through a third-party provider. Microsoft does not specifically recommend any third-party provider or third-party solution that this article might describe. There might also be other third-party providers or third-party solutions that this article does not describe. Because Microsoft must respond to changing market conditions, this information should not be interpreted to be a commitment by Microsoft. Microsoft cannot guarantee or endorse the accuracy of any information or of any solution that is presented by Microsoft or by any mentioned third-party provider.

Microsoft makes no warranties and excludes all representations, warranties, and conditions whether express, implied, or statutory. These include but are not limited to representations, warranties, or conditions of title, non-infringement, satisfactory condition, merchantability, and fitness for a particular purpose, with regard to any service, solution, product, or any other materials or information. In no event will Microsoft be liable for any third-party solution that this article mentions.