Consider the following:
Error message 1
Error message 2
Error message 3
Furthermore, the issue is sporadic and follows no observable pattern or trend. At times the above I/O errors can occur when SQL Server sends an I/O request as part of the Transaction Log Flush operation. A failure in that operation could cause the database to go offline and to start the database recovery process.
- You have VMWare ESX Virtual machine that is running either Windows Server 2008 or Windows Server 2008 R2 as guest OS.
- You have configured guest VM to use PVSCSI (Paravirtual SCSI) adapters from VMware. Paravirtual SCSI configurations use PVSCSI.sys driver in ESX environments.
Error message 1
Error: 17053, Severity: 16, State: 1.
LogWriter: Operating system error 1117(The request could not be performed because of an I/O device error.) encountered.
Write error during log flush.
Error: 9001, Severity: 21, State: 4.
The log for database 'DBNAME' is not available
spid51 Error: 9001, Severity: 21, State: 4.
spid51 The log for database 'DBNAME' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
spid12s Error: 9001, Severity: 21, State: 4.
spid12s The log for database 'DBNAME' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
spid51 Database DBNAME was shutdown due to error 9001 in routine 'XdesRMFull::Commit'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.
LogWriter: Operating system error 1117(The request could not be performed because of an I/O device error.) encountered.
Write error during log flush.
Error: 9001, Severity: 21, State: 4.
The log for database 'DBNAME' is not available
spid51 Error: 9001, Severity: 21, State: 4.
spid51 The log for database 'DBNAME' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
spid12s Error: 9001, Severity: 21, State: 4.
spid12s The log for database 'DBNAME' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
spid51 Database DBNAME was shutdown due to error 9001 in routine 'XdesRMFull::Commit'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.
Error message 2
Error: 823, Severity: 24, State: 3.
The operating system returned error 1117(The request could not be performed because of an I/O device error.) to SQL Server during a write at offset 0x000000b5940000 in file 'H:\MSSQL\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.
spid10s Error: 18400, Severity: 16, State: 1.
spid10s 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.
The operating system returned error 1117(The request could not be performed because of an I/O device error.) to SQL Server during a write at offset 0x000000b5940000 in file 'H:\MSSQL\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.
spid10s Error: 18400, Severity: 16, State: 1.
spid10s 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 message 3
spid13s Error: 17053, Severity: 16, State: 1.
spid13s ReadFileHdr: Operating system error 1117(The request could not be performed because of an I/O device error.) encountered.
spid13s Error: 5159, Severity: 24, State: 3.
spid13s Operating system error 1117(The request could not be performed because of an I/O device error.) on file "H:\MSSQL\DBNAME_log.LDF" during ReadFileHdr.
spid13s ReadFileHdr: Operating system error 1117(The request could not be performed because of an I/O device error.) encountered.
spid13s Error: 5159, Severity: 24, State: 3.
spid13s Operating system error 1117(The request could not be performed because of an I/O device error.) on file "H:\MSSQL\DBNAME_log.LDF" during ReadFileHdr.
Furthermore, the issue is sporadic and follows no observable pattern or trend. At times the above I/O errors can occur when SQL Server sends an I/O request as part of the Transaction Log Flush operation. A failure in that operation could cause the database to go offline and to start the database recovery process.