Testing and Production db's have lost connection to the translog 2 days in a row now. Today, my prod db was marked suspect after the issue - SCARY. The other db's did not lose connection. Possibly because there was no activity at that moment.
No errors in SQL log, only windows. Server Resources were not necessarily be hammered. I will be scouring the web, but wanted to reach out to all of you as well. See info and errors below.
Plenty of available drive space for Log, db, and tempdb partitions. 144gb RAM
SQL Server 2008 SP1; Enterprise (64-bit)
OS: Win Server 2008 R2 EnterpriseWin app logs:
error1- LogWriter: Operating system error 21(The device is not ready.) encountered.
error2 - The log for database (testing) is not available. Check the event log for related error messages. Resolve any errors and restart the database.
info mess3- Database 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.2 seconds later prod db goes down:
The log for database is not available. Check the event log for related error messages. Resolve any errors and restart the database.
error5 - During undoing of a logged operation in database, an error occurred at log record ID (86400:39070:17). 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.
error6 - fcb::close-flush: Operating system error (null) encountered.
error7 - An error occurred during recovery, preventing the database (PRODUCTION :w00t
from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
info mess8 -CHECKDB for database finished without errors on 2011-03-14 12:12:41.503 (local time). This is an informational message only; no user action is required.