locked
offline defrag error RRS feed

  • Question

  • I ran an offline defrag on an exchange 2003 database it stopped with the following error:"Operation terminated with error -1018 (JET_errReadVerifyFailure, Checksum error
    on a database page) after 389.31 seconds."

    Intergrity check also failed with checksum error. How can I repair this

    Saturday, February 25, 2012 12:58 PM

Answers

  • thanks. that was very informative. Base on error and subsequent scan with eseutil /k, it looks the database is corrupt beyound repair. It had 150 page errors none repairable. Previously had run eseutil /p and 75GB database decreased in size to .98GB. Looks like we will try to pst all mailboxes hen try to rebuild exchange db.
    • Marked as answer by emma.yoyo Monday, March 5, 2012 1:55 AM
    Monday, February 27, 2012 4:52 PM

All replies

  • Hi there,

    Please have a look on this..

    http://support.microsoft.com/kb/314917


    Kottees : My Blog : Please mark it as an answer if it really helps you.

    Saturday, February 25, 2012 2:02 PM
  • Hi davidjc52,

    Any updates?

    Please also check whether the eseutil is compatible with the current Exchange server database:

    Operation terminated with error -1018 (JET_errReadVerifyFailure, Checksum error on a database page)

    http://support.microsoft.com/kb/555524

    If the issue still occurs, please run the Eseutil /P first.

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Frank Wang

    TechNet Community Support

    Monday, February 27, 2012 7:54 AM
  • thanks. that was very informative. Base on error and subsequent scan with eseutil /k, it looks the database is corrupt beyound repair. It had 150 page errors none repairable. Previously had run eseutil /p and 75GB database decreased in size to .98GB. Looks like we will try to pst all mailboxes hen try to rebuild exchange db.
    • Marked as answer by emma.yoyo Monday, March 5, 2012 1:55 AM
    Monday, February 27, 2012 4:52 PM
  • We previously had run eseutil /p and the edb went from 75GB down to .98GB The previous kb was very helpful in explaining what the 1018 error meant. Looks like the db is beyond repair, although still mountable.

    Monday, February 27, 2012 4:54 PM
  • Hi davidjc52,

    If you are running Exchange 2003 Enterprise version, you can also try to create a new database then move mailboxes to the new one.


    Frank Wang

    TechNet Community Support

    Wednesday, February 29, 2012 1:55 AM
  • Thanks. It is exchange 2003 standard on sbs 2003 and that seems to be our only option as the db is badly damaged, although mountable. We will try to export each mailbox to a pst then move them in to new db.
     
    Wednesday, February 29, 2012 11:28 AM