Failed to mount database "Mailbox Database" in SBS2011

Do I run eseutil /mh "C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\Mailbox Database.edb" in Exchange Management Shell or Command window?

in the management shell

This is what I got:

Initiating FILE DUMP mode...
Error: Access to source database 'C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\Mailbox Databa
se.edb' failed with Jet error -1811.

Operation terminated with error -1811 (JET_errFileNotFound, File not found) after 0.78 seconds.

Did you try  to run  /P to repair?  Make sure you have a good backup before you run a repair though.

My bad ... I had exchange database in another Drive and folder  --->  E:\exchange\Mailbox\Mailbox Database.edb
I ran it again and this is the result:

[PS] C:\program files\microsoft\exchange server\v14\mailbox\mailbox database>eseutil /mh "E:\exchange\Mailbox\Mailbox Database.edb"

Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.01
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating FILE DUMP mode...
         Database: E:\exchange\Mailbox\Mailbox Database.edb


DATABASE HEADER:
Checksum Information:
Expected Checksum: 0x12da28e4
  Actual Checksum: 0x12da28e4

Fields:
        File Type: Database
         Checksum: 0x12da28e4
   Format ulMagic: 0x89abcdef
   Engine ulMagic: 0x89abcdef
 Format ulVersion: 0x620,17
 Engine ulVersion: 0x620,17
Created ulVersion: 0x620,17
     DB Signature: Create time:07/02/2012 13:27:25 Rand:21822536 Computer:
         cbDbPage: 32768
           dbtime: 134075366 (0x7fdd3e6)
            State: Dirty Shutdown
     Log Required: 311323-311343 (0x4c01b-0x4c02f)
    Log Committed: 0-311344 (0x0-0x4c030)
   Log Recovering: 311323 (0x4c01b)
  GenMax Creation: 12/21/2012 09:19:59
         Shadowed: Yes
       Last Objid: 33348
     Scrub Dbtime: 0 (0x0)
       Scrub Date: 00/00/1900 00:00:00
     Repair Count: 0
      Repair Date: 00/00/1900 00:00:00
 Old Repair Count: 0
  Last Consistent: (0x4BF77,8,1F)  12/21/2012 00:10:17
      Last Attach: (0x4BF78,9,86)  12/21/2012 00:10:18
      Last Detach: (0x0,0,0)  00/00/1900 00:00:00
             Dbid: 1
    Log Signature: Create time:05/20/2011 14:28:17 Rand:1158643 Computer:
       OS Version: (6.1.7601 SP 1 NLS ffffffff.ffffffff)

Previous Full Backup:
        Log Gen: 311131-311151 (0x4bf5b-0x4bf6f) - OSSnapshot
           Mark: (0x4BF6F,376,1B3)
           Mark: 12/20/2012 23:00:27

Previous Incremental Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Previous Copy Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Previous Differential Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Current Full Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Current Shadow copy backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

     cpgUpgrade55Format: 0
    cpgUpgradeFreePages: 0
cpgUpgradeSpaceMapPages: 0

       ECC Fix Success Count: none
   Old ECC Fix Success Count: none
         ECC Fix Error Count: none
     Old ECC Fix Error Count: none
    Bad Checksum Error Count: none
Old bad Checksum Error Count: none

  Last checksum finish Date: 00/00/1900 00:00:00
Current checksum start Date: 00/00/1900 00:00:00
      Current checksum page: 0


Operation completed successfully in 0.62 seconds.

[PS] C:\program files\microsoft\exchange server\v14\mailbox\mailbox database>

Ok, so you had a dirty shut down...
    DB Signature: Create time:07/02/2012 13:27:25 Rand:21822536 Computer:
         cbDbPage: 32768
           dbtime: 134075366 (0x7fdd3e6)
            State: Dirty Shutdown

make sure you have a clean backup and run.


eseutil /p "C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\Mailbox Database.edb"

Replace C: with your exchange drive...

after it completes run the first step again and make sure you have a clean shutdown then try to mount

It looks like it is "Dirty Shutdown". Therefore I need to run "Repair"?
I checked the backup overnight and it was done, but just in case, can I copy the entire database folder to another location to be safe?

You do not want to copy the corrupted database.  Why don't you do a test restore just to make sure your exchange DB is there.  What backup are you using?  If you are using something like symantec BU exec, you can test a restore down to an individual email to see its there.

I am using Windwos Server Backup - incremental backup.
I have never tried "restore" from either Backupexec or Windows Server Backup before.
BTW, I do use Symantec Backupexec only to backup Exchange once a week. So the last good one is this past weekend and the exchange system went down early this morning.

Well backup exec does granular backups, meaning if i wanted to restore one email out of the entire exchange DB i can do it with backup exec.  If you have 2 backups, one with win server and one with backup exec.  I would say it's safe to run the repair.  You can at least get the DB back in the proper state and check for data loss.  I'm not saying you will lose anything at all, but theres always a chance.

so run : eseutil /p "E:\exchange\Mailbox\Mailbox Database.edb" ?

another question. per screenshot of mailbox, why do I see two of "mailbox database.edb" ?

Is that where your Db is?  Run it the same way you did the firs command just with /p  if it was on the C: drive, it's typically

eseutil /p "C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\Mailbox Database.edb"

Yes. that is where the exchange database is located. I moved it from default location.

Another question. per screenshot (ID: 38713951) of mailbox, why do I see two of "mailbox database.edb" ?

I'm not sure why there are 2 but they are the same size...try the repair and see what happens.

OK. I will run a repair and keep you posted.

The repair was successful, but when I tried to mount, it gave me this error:

Should I have restarted Exchange related services or should I run repair again?

Run the repair again...but before you mount you need to make sure it's not in a dirty restart still by running the

eseutil /mh E:\exchange\Mailbox\Mailbox Database.edb

analyze the results and be sure its in a clean restart state

Here is bottom part of the same error message screenshot.

ok I will.

I ran eseutil /mh "E:\exchange\Mailbox\Mailbox Database.edb" and it say "Clean Shutdown" like below. I will run Repair again.

DATABASE HEADER:
Checksum Information:
Expected Checksum: 0x1cd061c0
  Actual Checksum: 0x1cd061c0

Fields:
        File Type: Database
         Checksum: 0x1cd061c0
   Format ulMagic: 0x89abcdef
   Engine ulMagic: 0x89abcdef
 Format ulVersion: 0x620,17
 Engine ulVersion: 0x620,17
Created ulVersion: 0x620,17
     DB Signature: Create time:12/21/2012 14:15:51 Rand:16103406 Computer:
         cbDbPage: 32768
           dbtime: 137869024 (0x837b6e0)
            State: Clean Shutdown
     Log Required: 0-0 (0x0-0x0)
    Log Committed: 0-0 (0x0-0x0)
   Log Recovering: 0 (0x0)
  GenMax Creation: 00/00/1900 00:00:00

Also, this error is disk related.  I would reboot and run a chkdsk

Why do I still have two databases?

One has gotten bigger too.  Reboot, run a check disk..make sure the disk is in good shape and repair anything that needs repairing.  Then try to mount the DB.  I don't know why you have  2 DB's...what happened that caused all this anyway?

[PS] C:\Users\admin\Desktop>eseutil /p "E:\exchange\Mailbox\Mailbox Database.edb"

Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.01
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating REPAIR mode...
        Database: E:\exchange\Mailbox\Mailbox Database.edb
  Temp. Database: TEMPREPAIR14144.EDB

Checking database integrity.

                     Scanning Status (% complete)

          0    10   20   30   40   50   60   70   80   90  100
          |----|----|----|----|----|----|----|----|----|----|
          ...................................................


Integrity check successful.

Note:
  It is recommended that you immediately perform a full backup
  of this database. If you restore a backup made before the
  repair, the database will be rolled back to the state
  it was in at the time of that backup.

Operation completed successfully in 323.687 seconds.

When I tried to mount the database, I get the same error as below:
The repair was very short 2nd time compared to first time.

--------------------------------------------------------
Microsoft Exchange Error
--------------------------------------------------------
Failed to mount database 'Mailbox Database'.

Mailbox Database
Failed
Error:
Couldn't mount the database that you specified. Specified database: Mailbox Database; Error code: An Active Manager operation failed with a transient error. Please retry the operation. Error: Database action failed with transient error. Error: A transient error occurred during a database operation. Error: MapiExceptionJetErrorDiskIO: Unable to mount database. (hr=0x80004005, ec=-1022)
 [Database: Mailbox Database, Server: DC1.DC.local].

An Active Manager operation failed with a transient error. Please retry the operation. Error: Database action failed with transient error. Error: A transient error occurred during a database operation. Error: MapiExceptionJetErrorDiskIO: Unable to mount database. (hr=0x80004005, ec=-1022)
 [Database: Mailbox Database, Server: DC1.DC.local]

An Active Manager operation failed with a transient error. Please retry the operation. Error: MapiExceptionJetErrorDiskIO: Unable to mount database. (hr=0x80004005, ec=-1022)
 [Server: DC1.DC.local]

MapiExceptionJetErrorDiskIO: Unable to mount database. (hr=0x80004005, ec=-1022)

Error: MapiExceptionJetErrorDiskIO

This is a hard disk error.  Try to run the check disk utility from the cmd prompt

In fact, when I logged on to the SBS2011, there was a popup windows about "RAID" error. Let me look into it. But the file server is up and running right now and people are accessing files and creating documents as we speak.

then you probably can't restart the server right now since people are working, but i would go to disk management and see if any disks are in an unhealthy state.

Try to run the check disk utility from the cmd prompt  ---> what is the command ?

chkdsk E:

I will try that. Here is the RAID status screen.

C:\Users\admin>chkdsk E:
The type of the file system is NTFS.
Volume label is New Volume.

WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
 1 percent complete. (59879 of 598784 file records processed)
Attribute record (128, "") from file record segment 96348
is corrupt.
Attribute record (128, "") from file record segment 96451
is corrupt.
  598784 file records processed.
File verification completed.
  59 large file records processed.

Errors found.  CHKDSK cannot continue in read-only mode.

C:\Users\admin>

ok

C:\Users\admin>chkdsk /f E:
The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another
process.  Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N)


If I answer "YES" then this will kick people off the files that are open?

yea, thats the problem with doing it while logged in.  I think once you are able to fix the disk, you should be able to mount the DB though

OK. I think users are pretty much gone now. I will do that in about 30 min. or so.

I talked to RAID support person at LSI and they recommended against running CHKDSK /f.
Based on their request, I sent RAID controller diagnostic tool log to them and they said that their CARD memory is faulty. That is the reason it caused the problem with Exchange database. They are going to replace the card next week.
I scheduled "consistency" check in their RAID software program and I like to see if it will solve the problem.
At the same time I opened the case with Microsoft because I am concerned that there are two exchange databases and one of them is not going away.
I will keep you posted.

My windows backup starts at 11PM and I like to stop it because I do not want to backup corrupted exchange database and at the same time preserve a good backup.How do you stop scheduled windows server backup? I looked around, but I can't seem to find it in either Task Scheduler or Windows Server Backup program.

Go to the sbs console from start menu

I ended up calling Microsoft Exchange Support engineer for help knowing the severity of the issue on my customer's server. I finally got the issue resolved.
In a nutshell, the support engineer did what you suggested that I do based on the link you provided.
http://www.virtualhelp.me/windows/579-exchange-2010-error-unable-to-mount-database

Thank you for your help.

good to hear...happy holidays