Can't mount database after power failure
We were doing a shutdown during the second power failure of the day when the battery backup, not recovered from the first, ran out of power. Now when I try to bring Exchange 2007 up, it can't mount the private store. The first error in the event log is:
MSExchangeIS (2992) First Storage Group: Database C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\Mailbox Database.edb: Page 355498 (0x00056caa) failed verification due to a flush-order dependency mismatch. This page should have flushed before page 355497 (0x00056ca9), but the latter page has instead flushed first. Recovery/restore will fail with error -255.
Then right after, I get this:
Error 0xffffff01 starting Storage Group /DC=local/DC=xxx/CN=Config
Storage Group - Initialization of Jet failed.
and then this:
Error 0xffffff01 starting Storage Group /DC=local/DC=xxx/CN=Config
<NULL>.
The exchange management console gives me a "Dirty Shutdown" from a manual examination of the private store and shows this:
Lowest required log file is: 0x1A1E
Highest required log file is: 0x1A23
Lowest log file found in the log directory is: E00.log
Highest log file found in the log directory is: E00.log (0x1A23)
Missing or mismatched log files: E0001A1E.log-E0001A22.log
Problems with the log files listed above must be resolved before this database can be recovered.
The files it lists are in the directory and the first log file after the first power outage is 1a1d (the next one is where it has problems). But the power outages were 12 hours apart and everything was working until the second one, so only the last couple of log files are near that second outage/shutdown window.
I tried running the repair in the exchange management utility (I backed up all the files first). It said it finished with a positive action code (595) but then showed an error performing the first isinteg run and that it couldn't open the database. It also said it successfully defragmented it.
Using the database analysis, it says it's now in a clean shutdown state but shows a "log signature discrepancy" (no details).
I tried restarting the store and now I get error -1216 and it says the database isn't there (even though it is).
I actually just deleted all the log files and mounted the database and recovered all but a handful of messages!
I actually started typing this as I went along and the problem is now resolved. I just wanted to finish posting for the benefit of others.
Don
MSExchangeIS (2992) First Storage Group: Database C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\Mailbox Database.edb: Page 355498 (0x00056caa) failed verification due to a flush-order dependency mismatch. This page should have flushed before page 355497 (0x00056ca9), but the latter page has instead flushed first. Recovery/restore will fail with error -255.
Then right after, I get this:
Error 0xffffff01 starting Storage Group /DC=local/DC=xxx/CN=Config
Storage Group - Initialization of Jet failed.
and then this:
Error 0xffffff01 starting Storage Group /DC=local/DC=xxx/CN=Config
<NULL>.
The exchange management console gives me a "Dirty Shutdown" from a manual examination of the private store and shows this:
Lowest required log file is: 0x1A1E
Highest required log file is: 0x1A23
Lowest log file found in the log directory is: E00.log
Highest log file found in the log directory is: E00.log (0x1A23)
Missing or mismatched log files: E0001A1E.log-E0001A22.log
Problems with the log files listed above must be resolved before this database can be recovered.
The files it lists are in the directory and the first log file after the first power outage is 1a1d (the next one is where it has problems). But the power outages were 12 hours apart and everything was working until the second one, so only the last couple of log files are near that second outage/shutdown window.
I tried running the repair in the exchange management utility (I backed up all the files first). It said it finished with a positive action code (595) but then showed an error performing the first isinteg run and that it couldn't open the database. It also said it successfully defragmented it.
Using the database analysis, it says it's now in a clean shutdown state but shows a "log signature discrepancy" (no details).
I tried restarting the store and now I get error -1216 and it says the database isn't there (even though it is).
I actually just deleted all the log files and mounted the database and recovered all but a handful of messages!
I actually started typing this as I went along and the problem is now resolved. I just wanted to finish posting for the benefit of others.
Don
ASKER
I already fixed it using the exchange management utility. Then it was necessary to delete the log files because they were still a problem.
To reiterate: I only posted this for informational purposes. The problem and solution are all actually in my original question.
To reiterate: I only posted this for informational purposes. The problem and solution are all actually in my original question.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
http://www.msexchange.org/tutorials/Exchange-ISINTEG-ESEUTIL.html