Corrupted exchange database

Ouch, sounds like your file-level antivirus ate your logs. Happens on Monday fi you're using Norton or Symantec stuff, it installs a default scheduled scan for the whole computer. If the database is corrupted, it's most likely because the AV moved the log file to the quarantine directory, if you have one. Search for it. In the meantime, exclude your \exchsrvr directories to avoid further losses. Let me know if you find that log(s), they will be sequential to the ones in the mdbdata directory now.

D

Thats not it i have checked the quarantine and there is nothing in there.

OK, then, look in the applog and see when the databases went offline. Post the event IDs here, in order, let's see what happened.

D

Here they are in order from first to last events

Error 0x3ed occurred during folder background cleanup on database "First Storage Group\Mailbox Store (SERVER)".

Error 0x3ed occurred during folder background cleanup on database "First Storage Group\Mailbox Store (SERVER)".

Thats pretty much all i could gather

http://support.microsoft.com/default.aspx?scid=kb;en-us;288648

This isn't the problem. try to mount the stores again, and then check the logs for the event IDs. And look farther back in the logs, the errors are there unless you dumped the logs or overwrote them

D

This is from trying to startup the stores again

Error 0xfffffea8 starting Storage Group /DC=COM/DC=SEAWESTINC/CN=CONFIGURATION/CN=SERVICES/CN=MICROSOFT EXCHANGE/CN=SEAWEST/CN=ADMINISTRATIVE GROUPS/CN=FIRST ADMINISTRATIVE GROUP/CN=SERVERS/CN=SERVER/CN=INFORMATIONSTORE/CN=FIRST STORAGE GROUP on the Microsoft Exchange Information Store.

Error 0xfffffea8 starting database "First Storage Group\Public Folder Store (SERVER)" on the Microsoft Exchange Information Store.

The latest logs i have are what i sent you.  I did clean out the events in hopes of cleaing up the server.  It was very low on disk space which was initially what i believe caused the problem.  

Also got this error

Information Store (3360) Database C:\Program Files\Exchsrvr\mdbdata\pub1.edb is partially attached. Attachment stage: 4. Error: -344.

http://support.microsoft.com/default.aspx?scid=kb;en-us;312873

It suggests you need to defrag the store. How big is the pub, and did the mailbox store give the same error?

D

I tried to defrag and got an error, will try to remake and send in a bit.  The size is 160MB on the pub and 10.9 GB on the priv.

These are the errors i get from the private store.

Error Database is in inconsistent state starting Storage Group /DC=COM/DC=SEAWESTINC/CN=CONFIGURATION/CN=SERVICES/CN=MICROSOFT EXCHANGE/CN=SEAWEST/CN=ADMINISTRATIVE GROUPS/CN=FIRST ADMINISTRATIVE GROUP/CN=SERVERS/CN=SERVER/CN=INFORMATIONSTORE/CN=FIRST STORAGE GROUP on the Microsoft Exchange Information Store.

Error Database is in inconsistent state starting database "First Storage Group\Mailbox Store (SERVER)" on the Microsoft Exchange Information Store.

ok well, the defrag won't work on the mailbox store when its inconsistent. To work with it, you're going to need some space, at least 11 or 12 GB. I'm off here for the eve, but if you have a space to copy the database files to, along with the ese.dll and eseutil, you can repair it afterwards in needed. If you have good backups, you should start planning on a restore. The repair of the database should be a last resort option. If no good backup exists from recently, then a repair may be all you get.

Are you sure you don't have logs somewhere else? Logs usually don't just disappear, they get taken or you have a hardware failure. System log show any disk or scsi errors? If so, hardware may be the culprit.

D

So how did this turn out, do you still need assistance?

D

Thats a negative.  It didnt turn out nor do i need assistance.  I had to mount brand new databases and import the data using a utility.  Its all working now so thats the good thing.  I called microsoft and they couldn't do anything with it either.