Eroor 823 SMB cluster

  • Hello,

     

    I'm in hectic problem-Heritage an SQL 2016 cluster with 2 VM's and SMB as shared files where data files and log files are hosted.

    Backup is done with ComVault.

    Errors  Message

    the operating system returned error 59(An unexpected network error occurred.) to SQL Server during a read at offset 0000000000000000 in file

    The operating system returned error 59(An unexpected network error occurred.) to SQL Server during a read at offset 0000000000000000 in file '\\yyyy\xxx_sqllog_1\MSSQL13.MSSQLSERVER\MSSQL\Data\l1.ldf'. 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.

    followed by Message

    Error: 823, Severity: 24, State: 1.

    Very often _ dive into a problem with instance becoming stuck  or   some databases remains in recovery_pending status.

     

    Checkdb no issues found.

     

    Do you any ideea how can I fix it?

    Thanks,

     

    Hadrian

  • Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • Please verify the following:

    Windows server event viewer application / system errors.   Please look for hardware issues.

    The SQL server error log and agent error log.

    The operating system returned error 59(An unexpected network error occurred.) to SQL Server during a read at offset 0000000000000000 in file.. (This could indicate some hard drive issue.  The following file has corruption:  '\\yyyy\xxx_sqllog_1\MSSQL13.MSSQLSERVER\MSSQL\Data\l1.ldf'

    Please try this:  Backup the database in simple recovery model.   Shrink the log file.  then try the application again.  This clears the transaction logical pointers.   It should fix the issue.   It this does work, try to delete the transaction log file, and recreate it.

     

     

     

     

     

    DBASupport

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply