Possible Corruption

  • We had a disk drop and come back today that holds filestream files. I ran a DBCC CheckDB and it reported no allocation errors and no consistency errors in the database, but I am unable to do a log backup or differential backup. I get the errors...

    Msg 3634, Level 16, State 1, Line 1

    The operating system returned the error '21(The device is not ready.)' while attempting 'FsFileHeader::Read' on ''.

    Msg 5172, Level 16, State 70, Line 1

    The header for file '' is not a valid database file header. The File Header property is incorrect.

    Msg 3013, Level 16, State 1, Line 1

    BACKUP DATABASE is terminating abnormally.

    I am able to open the database and return query results from it. Anyone come across this before?

    Thanks,

    Josh

  • Once SQL Server lost connection to that drive - it doesn't check again. You can try taking the database offline and bringing it back online, but you may actually need to restart SQL Server before it will recognize the drive is back online and available.

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • Thanks for the reply! We're going to do a restart of services this evening and I'm hoping that will do that trick!

  • Restart SQL or take that DB offline and bring it back online (make absolutely sure the files really are there first). Once SQL detects that a file is missing, it won't retry.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Thank you Gail! I'm going to try to get thru the business day and perform a restart tonight. At that point I'm going to fire off a tran log backup and see if it succeeds.

  • After the restart, the DB will either be entirely available or you'll get errors in the errorlog on startup (and possibly even the DB not coming online). If the latter, you have more serious problems.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • I'll watch the SQL Log to see how it recovers and verify that I don't see any errors there and that it's come fully online...if not, off to backups I will go! Thanks again Gail!

Viewing 7 posts - 1 through 6 (of 6 total)

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