HELP I LOST MY M: DRIVE!

[xtremist5150]

We just had a power outage for over an hour, my UPS was messed up so I didn't get a chance to shut the servers down in time before they rebooted. Everything works web-wise now except that my M: drive is GONE! I try to access OWA and it gives me a HTTP/1.1 503 Service Unavailable error. Connecting to Exchange through Outlook I have outgoing mail hanging in the Outbox and no incoming messages.

Checked the mail server's IIS and the following virtual directories show red errors: Exchange and public. Have tried restarting IIS but no effect. I don't know what else to do!

Am running Exchange 2000 on SBS200 OS. All other web services work perfectly. Thanks.

 

[Marcs41]

Exchange is probably not started properly.
Check the services and try a clean restart if in doubt.

Marc
[sub]If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all. Please specify details.
Free Tip: The F1 Key does NOT destroy your PC!
How Do I Get Great Answers To my Tek-Tips Questions? [/sub]See faq222-2244

 

[xtremist5150]

That didn't work. In Internet Services Manager my public and Exchange boxes are flagged in red. I've tried remounting the database but says it won't let me gives error c1041739 something about being inconsistent.

ARGH!?!?!?!?

 

[Marcs41]

Check the Event logs, and post the events

Marc
[sub]If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all. Please specify details.
Free Tip: The F1 Key does NOT destroy your PC!
How Do I Get Great Answers To my Tek-Tips Questions? [/sub]See faq222-2244

 

[Marcs41]

Have a look here;

http://www.experts-exchange.com/Networking/Email_Groupware/Exchange_Server/Q_20947674.html#10789870

Marc
[sub]If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all. Please specify details.
Free Tip: The F1 Key does NOT destroy your PC!
How Do I Get Great Answers To my Tek-Tips Questions? [/sub]See faq222-2244

 

[Simonchtan]

you may need to recovery your edb and stm file try esutil.exe should come with the exchange CD. it can do off-line recovery and softrecovery to inconsistent database.

I know no voice, I knew nothing about systems,
i know NUTS on networking, Therefore I dont know anything!
-----------------------------------
©2003,2004 SCHT.

 

[Haleon]

Oh god, I've had to do this many times before.

Here are your two options (which are pretty much mutually exclusive anyway).

1.) Restore from a recent backup.

2.) Use eseutil to repair the database. Here's a quick tutorial on how to do that.

Go into the exchange bin directory. It's probably:

c:\program files\exchsrvr\bin

Run eseutil with the repair option. Run it on both the private and public databases. It'll look something like this:

eseutil /p "c:\program files\exchsrvr\mdbdata\priv1.edb"

and

eseutil /p "c:\program files\exchsrvr\mdbdata\pub1.edb"

If your database files are located on a different drive, change the drive letter.

After those run (it will take a while), you're going to want to run isinteg on both databases again. Do the following from the exchsrvr\bin directory:

isinteg (exchange server name) -fix -test alltests

When isinteg starts it will ask you to choose which database you want to run it on. Run it on the mailbox store first, then the public store. Here's the thing, you have to run it AT LEAST twice. The first time it will report a bunch of errors and fixes. The second time it hopefully won't report anything out of the ordinary. If it still reports errors the second time, run it a third time.

The third step is optional, though highly recommended. It's an offline defragmentation of the database. To do this, use that eseutil command again, but this time with the /d switch added on to it. That will defrag the databases. Again, do this to the public and the private store.

If this doesn't work, you're pretty much screwed. You'll HAVE to restore from backup. Also, a fair word of warning, you WILL lose some email doing this process. Chances are good that it'll be some unimportant crap from 1 year ago, but you will lose something. Potentially, you could lost a lot of email, though I haven't seen that happen yet. Just be careful with the tool.

 

[Haleon]

Typo alert:

When you run isinteg, make sure you use the -s switch to identify the server. I left that out. So it should look like:

isinteg -s "server name, leave out the quotes" -fix -test alltests

That should take care of it.

 

[xtremist5150]

Thanks everyone, took your advice and came up again perfectly. Appreciate all the help!