locked
SQLServerLogMgr::LogWriter: Operating system error 21(The device is not ready.) encountered. RRS feed

  • Question

  • Hi,

    I am getting below error with SQL Server 2012 (buid:12.0.4232).  This issue mostly comes when we load our data through Talend

    2017-05-04 01:04:08.19 spid4s      Error: 17053, Severity: 16, State: 1.
    2017-05-04 01:04:08.19 spid4s      SQLServerLogMgr::LogWriter: Operating system error 21(The device is not ready.) encountered.
    2017-05-04 01:04:08.19 spid4s      Write error during log flush.
    2017-05-04 01:04:08.19 spid65      Error: 9001, Severity: 21, State: 4.
    2017-05-04 01:04:08.19 spid65      The log for database 'ABCD' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
    2017-05-04 01:04:08.20 spid65      Database ABCD was shutdown due to error 9001 in routine 'XdesRMFull::CommitInternal'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.
    2017-05-04 01:04:08.22 spid44s     Error: 17053, Severity: 16, State: 1.
    2017-05-04 01:04:08.22 spid44s     fcb::close-flush: Operating system error (null) encountered.
    2017-05-04 01:04:08.22 spid44s     Error: 17053, Severity: 16, State: 1.
    2017-05-04 01:04:08.22 spid44s     fcb::close-flush: Operating system error (null) encountered.

    2017-05-04 01:04:09.79 spid51      Error: 823, Severity: 24, State: 2.
    2017-05-04 01:06:05.24 spid4s      Error: 17053, Severity: 16, State: 1.
    2017-05-04 01:06:05.24 spid4s      SQLServerLogMgr::LogWriter: Operating system error 21(The device is not ready.) encountered.
    2017-05-04 01:06:05.24 spid4s      Write error during log flush.
    2017-05-04 01:06:05.24 spid71      Error: 9001, Severity: 21, State: 1.
    2017-05-04 01:06:05.24 spid71      The log for database 'tempdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
    2017-05-04 01:06:05.24 spid71      Error wile committing a readonly or a TEMPDB XDES, Shutting down the server.
    2017-05-04 01:06:05.25 spid71      SQL Server shutdown has been initiated
    2017-05-04 01:06:05.25 spid71      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
    2017-05-04 01:06:05.39 spid16s     The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) 

    Regards

    Deepak Goyal


    Thursday, May 4, 2017 7:12 AM

All replies

  • That looks like a serious problem with the I/O subsystem. I don't know what Talend is, but if your log file is on a SAN, maybe you manage to saturate the network.

    • Proposed as answer by Riaon Monday, May 8, 2017 7:16 AM
    Thursday, May 4, 2017 8:59 PM