priv.edb problem

[cypherman]

I have an exchange 5.5 server that has experienced information store corruption. This is not the first time this has happened. I have always been able to use the eseutil /p /ispriv to resolve the issue in the past.
the repair of the edb files has never taken more than an hour to fix in the past.

Today I am running the same processes as I have done in the past, and the repair is still sitting and running after several hours (approx 6) the verbose shows it is rebuilding data on the table. Task manager shows the process is running but I am at a loss as to why it is taking forever and cannot determine if it is truly doing anything for certain. Ideas?????

the priv.edb file is only 397mb in size so it should not take very long at all.
Please help,
Thanks in advance,
cypherman.

 

[Zelandakh]

I'd recommend that you leave it. That is a fairly robust app so it PROBABLY hasn't crashed. 12 hours total running should be good.

 

[DestinysDream]

Do you run through the other eseutil options before using that one? Because sometimes the /r will resolve issues and is not as damaging.

If anyone calls and says "I know a little something about computers" just tell them to reformat it.

 

[cypherman]

Well, here is the scoop. Thanks for the advice. Yes, I did run the /mh and the /r options prior to running the /p option for eseutil. That is why I ran the /p. After waiting for 14 hours the 'rebuilding data' was still running with no progress on the status bar. I went around to all of my users workstations to confirm they had created .pst files of their mailboxes and folders ( I make them do this daily), deleted the edb and log files and restarted the services with no problems. Then I restored the .pst files and no one skipped a beat
Thanks again.

 

[DestinysDream]

You braver then me.

If anyone calls and says "I know a little something about computers" just tell them to reformat it.

 

[SimonDavis]

Wow.

"What's a .pst file? Oh. What's a hard disk? really?"

"You want me to what?"

"God these computer people want us to do their . . . "