<div>
1] Do you have sufficient memory &amp;&nbsp;hard drive space left.<br />
2] What is the error given on hard repair<br />
3] What does the event log show you in regards to this issue.<br />
4] Have you tried using the Exchange CMDlet shell to run <i>Get-EventLogLevel</i> and review the event log levels for the Exchange stores. This might hold additional clues.
</div>


<div>
I managed to run eseutil /P and it finish repairing but still cant mount the DB
</div>


<div>
error attached<br />
<a href="https://filedb.experts-exchange.com/incoming/2016/02_w06/1079324/a.png" target="_blank" class="file-inline" title="error (751 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>a.png</a>
</div>


a.png

<div>
Ok. When the eseutil /P finalized, did it give you the status &quot;<b>Clean Shutdown</b>&quot;?<br />
Without this status you will be unlikely able to mount it.<br />
<br />
If still &quot;<b>Dirty Clean</b>&quot; it could be that there is a problem with the DataBase logs.<br />
<br />
You could use the <i>eseutil /m1</i> parameter pointed to the logs to try and repair the logs.<br />
Still make sure that there is sufficient space left on the database &amp;&nbsp;the log drives for Exchange to be able to work.<br />
<br />
Example command:<br />
<br />
&quot;<b>eseutil /ml &quot;C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox<wbr /> Database\E00</b>&quot;<br />
<br />
Don't forget to specify E00 btw, which is the start equence of the logs
</div>


<div>
hi, I don't have e00 its start from e01, however its refuse to mount ....
</div>


<div>
Looks like some of the logs got deleted potentially.<br />
When refusing to mount the problem is either with the database, or the database log files.<br />
Often what happens is that an engineer might be wanting to clear space, and incidentally removes log files for Exchange.<br />
<br />
This can cause the DB not to mount post a backup or reboot.<br />
I'm not certain what would happen if the e00 folder is missing, but try the command starting with e00 regardless. If that fails run the command with e01 instead and post back results please.<br />
<br />
Alternatively check a recent backup of the server from the day where it last worked, and see if restoring the e00 folder, then running the command helps in resolving the problem.
</div>


<div>
ok I resolve this by moving the logs to a different folder...
</div>


<div>
<div class="content wysiwyg-content">
hello all,<br />
<br />
we have exchange 2013 running on 2012, the server crash (blue screen) but we able to start it.<br />
the exchange is not working and (dismount) we tried to check db integrity and the result was &quot;dirty clean&quot;<br />
we tried /p hard repair but it comes out with error.
</div>
</div>


hello all,

we have exchange 2013 running on 2012, the server crash (blue screen) but we able to start it.
the exchange is not working and (dismount) we tried to check db integrity and the result was "dirty clean"
we tried /p hard repair but it comes out with error.

cant mount exchange 2013

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.