The latest articles on DEV Community by Bharat Bhushan (@bharat_bsingh_6f4fe7fc7). https://dev.to/bharat_bsingh_6f4fe7fc7 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3873990%2F193f4cff-3d0a-49f3-8cef-e6d6bb33be9e.jpg https://dev.to/bharat_bsingh_6f4fe7fc7 en Bharat Bhushan Sat, 11 Apr 2026 19:39:57 +0000 https://dev.to/bharat_bsingh_6f4fe7fc7/exchange-database-wont-mount-after-shutdown-the-complete-diagnostic-flowchart-jet-1018-1022-59bg https://dev.to/bharat_bsingh_6f4fe7fc7/exchange-database-wont-mount-after-shutdown-the-complete-diagnostic-flowchart-jet-1018-1022-59bg <p><em>Last Updated: April 2026</em></p> <h2> Quick Answer </h2> <p>An Exchange database that won't mount after shutdown is almost always in a <strong>dirty shutdown</strong> state, caused by one of four JET (Extensible Storage Engine) errors:</p> <ul> <li> <strong>-1018</strong> → Database corruption (checksum mismatch)</li> <li> <strong>-1022</strong> → Disk I/O failure</li> <li> <strong>528</strong> → Missing transaction logs</li> <li> <strong>548</strong> → Log file mismatch</li> </ul> <blockquote> <p><strong>Golden Rule:</strong> Never run <a href="https://www.stellarinfo.com/article/exchange-database-hard-repair-eseutil-p-commands.php" rel="noopener noreferrer"><code>eseutil /p</code></a> before identifying the exact error. This can permanently delete mailbox data.</p> </blockquote> <h2> Applies To </h2> <ul> <li>Microsoft Exchange Server 2013</li> <li>Microsoft Exchange Server 2016</li> <li>Microsoft Exchange Server 2019</li> </ul> <h2> Why Exchange Databases Fail to Mount </h2> <p>Microsoft Exchange uses the Extensible Storage Engine (ESE) database (<code>.edb</code>) with transaction logs (<code>.log</code>) for crash-safe operations.</p> <p><strong>How it works:</strong></p> <ul> <li>Data is written to logs first</li> <li>Then committed to the database</li> <li>Ensures recovery after failure</li> </ul> <p><strong>What causes failure:</strong></p> <ul> <li>Power outage</li> <li>OS crash</li> <li>Storage disconnection</li> <li>Forced service stop</li> </ul> <p>According to Microsoft: <a href="https://learn.microsoft.com/en-us/exchange/troubleshoot/database/database-corruption-issues" rel="noopener noreferrer">According to Microsoft Exchange documentation on database corruption</a></p> <h2> Step 1: Check Database State </h2> <p>Run <a href="https://www.stellarinfo.com/article/check-exchange-database-state-using-eseutil-mh-command.php" rel="noopener noreferrer"><code>eseutil /mh</code></a> to determine the current database state:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight batchfile"><code><span class="kd">eseutil</span> <span class="na">/mh </span><span class="kd">DBPath</span>.edb </code></pre> </div> <div class="table-wrapper-paragraph"><table> <thead> <tr> <th>State</th> <th>Meaning</th> <th>Action</th> </tr> </thead> <tbody> <tr> <td>Clean Shutdown</td> <td>Safe</td> <td>Mount database</td> </tr> <tr> <td>Dirty Shutdown</td> <td>Inconsistent</td> <td>Continue diagnosis</td> </tr> </tbody> </table></div> <h2> The 4-Layer Failure Model </h2> <p>Every Exchange mount failure belongs to one of four layers:</p> <div class="table-wrapper-paragraph"><table> <thead> <tr> <th>Layer</th> <th>Error</th> <th>Meaning</th> </tr> </thead> <tbody> <tr> <td>Data Layer</td> <td>-1018</td> <td>Database corruption</td> </tr> <tr> <td>Storage Layer</td> <td>-1022</td> <td>Disk failure</td> </tr> <tr> <td>Log Layer</td> <td>528</td> <td>Missing logs</td> </tr> <tr> <td>Consistency Layer</td> <td>548</td> <td>Log mismatch</td> </tr> </tbody> </table></div> <h2> What is Jet Error -1018? </h2> <p>Jet error -1018 is a database corruption error caused by a <strong>checksum mismatch</strong>. It occurs when a database page is partially written, storage returns inconsistent data, or external tools modify the database.</p> <p><strong>Diagnose:</strong><br> </p> <div class="highlight js-code-highlight"> <pre class="highlight batchfile"><code><span class="kd">eseutil</span> <span class="na">/g </span><span class="kd">DBName</span>.edb </code></pre> </div> <p><strong>Recovery:</strong></p> <div class="table-wrapper-paragraph"><table> <thead> <tr> <th>Method</th> <th>Risk</th> <th>When to Use</th> </tr> </thead> <tbody> <tr> <td>Restore backup</td> <td>None</td> <td>Best option</td> </tr> <tr> <td><code>eseutil /p</code></td> <td>High</td> <td>No backup available</td> </tr> <tr> <td><a href="https://www.stellarinfo.com/edb-exchange-server-recovery.htm" rel="noopener noreferrer">Stellar Repair for Exchange</a></td> <td>Low</td> <td>Critical recovery</td> </tr> </tbody> </table></div> <blockquote> <p>⚠️ <code>eseutil /p</code> permanently deletes corrupted pages — use only as a last resort.</p> </blockquote> <h2> What is Jet Error -1022? </h2> <p>Jet error -1022 is a <strong>disk I/O failure</strong> caused by storage issues — not database corruption. Exchange cannot access the disk.</p> <p><strong>Diagnose:</strong> Check Event Viewer (IDs: 7, 11, 51) and run <code>chkdsk /f /r</code></p> <p><strong>Recovery:</strong></p> <ol> <li>Fix the storage problem first</li> <li>Copy database to a healthy disk</li> <li>Run <code>eseutil /mh</code> </li> </ol> <blockquote> <p>⚠️ Never run eseutil on an unstable or failing disk.</p> </blockquote> <h2> JET Error -1018: Checksum Mismatch (Detail) </h2> <p><strong>Diagnose:</strong> <code>eseutil /g DBName.edb</code></p> <p><strong>Recovery:</strong> Restore from backup or use <code>eseutil /p</code> (high risk of data loss)</p> <h2> JET Error -1022: Disk IO Failure (Detail) </h2> <p><strong>Diagnose:</strong> Event Viewer + <code>chkdsk</code></p> <p><strong>Recovery:</strong> Fix disk first, then attempt database repair</p> <h2> Error 528: Missing Transaction Logs </h2> <p><strong>Cause:</strong> Required transaction logs are missing, breaking the recovery chain.</p> <p><strong>Common causes:</strong></p> <ul> <li>Circular logging enabled</li> <li>Manual deletion of log files</li> <li>Antivirus quarantine</li> <li>Failed backup job</li> </ul> <p><strong>Diagnose:</strong><br> </p> <div class="highlight js-code-highlight"> <pre class="highlight batchfile"><code><span class="kd">eseutil</span> <span class="na">/mh </span><span class="kd">DBName</span>.edb </code></pre> </div> <p>Check the <code>Log Required: X-Y</code> range and verify which log files exist.</p> <p><strong>Recovery:</strong></p> <div class="table-wrapper-paragraph"><table> <thead> <tr> <th>Scenario</th> <th>Solution</th> </tr> </thead> <tbody> <tr> <td>Backup exists</td> <td>Restore from backup</td> </tr> <tr> <td>Circular logging ON</td> <td>Hard repair (data loss likely)</td> </tr> <tr> <td>Partial logs missing</td> <td><a href="https://www.stellarinfo.com/edb-exchange-server-recovery.htm" rel="noopener noreferrer">Stellar Repair for Exchange</a></td> </tr> </tbody> </table></div> <blockquote> <p>⚠️ Circular logging + crash = no full recovery possible.</p> </blockquote> <h2> Error 548: Log Signature Mismatch </h2> <p><strong>Cause:</strong> Log files don't match the database signature.</p> <p><strong>Common causes:</strong></p> <ul> <li>Mixed log files from different databases</li> <li>Improper restore operation</li> <li>DAG misconfiguration</li> </ul> <p><strong>Diagnose:</strong><br> </p> <div class="highlight js-code-highlight"> <pre class="highlight batchfile"><code><span class="kd">eseutil</span> <span class="na">/ml </span><span class="kd">logfile</span>.log <span class="kd">eseutil</span> <span class="na">/mh </span><span class="kd">DBName</span>.edb </code></pre> </div> <p><strong>Fix:</strong></p> <ol> <li>Move mismatched logs to a backup folder</li> <li>Run <code>eseutil /p</code> followed by <code>eseutil /d</code> </li> </ol> <h2> Diagnostic Flow </h2> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code>DB won't mount → Run: eseutil /mh → Dirty Shutdown? → Check error code: -1018 → Database repair -1022 → Fix disk first 528 → Restore logs 548 → Remove mismatched logs </code></pre> </div> <h2> When <a href="https://www.stellarinfo.com/blog/how-to-use-eseutil-for-exchange-database-repair/" rel="noopener noreferrer">eseutil</a> Is NOT Enough </h2> <ul> <li>Causes data loss with <code>/p</code> </li> <li>Cannot recover data from dead disks</li> <li>Requires a complete log chain</li> <li>No granular mailbox recovery</li> </ul> <p>Microsoft recommends using verified backups as the primary recovery method. For critical EDB corruption scenarios, <a href="https://www.stellarinfo.com/edb-exchange-server-recovery.htm" rel="noopener noreferrer">Stellar Repair for Exchange</a> provides granular mailbox-level recovery without data loss.</p> <h2> Prevention </h2> <ul> <li>Disable circular logging</li> <li>Use UPS (Uninterruptible Power Supply)</li> <li>Monitor disk health proactively</li> <li>Test backups regularly</li> <li>Separate database and log files onto different volumes</li> <li>Use DAG (Database Availability Group) for high availability</li> </ul> <h2> JET Errors Summary </h2> <div class="table-wrapper-paragraph"><table> <thead> <tr> <th>Error</th> <th>Cause</th> <th>Fix</th> <th>Risk</th> </tr> </thead> <tbody> <tr> <td>-1018</td> <td>Checksum corruption</td> <td>Repair / Restore</td> <td>High</td> </tr> <tr> <td>-1022</td> <td>Disk I/O failure</td> <td>Fix storage</td> <td>High</td> </tr> <tr> <td>528</td> <td>Missing logs</td> <td>Restore logs</td> <td>High</td> </tr> <tr> <td>548</td> <td>Log mismatch</td> <td>Rebuild / Remove logs</td> <td>Medium</td> </tr> </tbody> </table></div> <h2> FAQ </h2> <p><strong>What is dirty shutdown?</strong><br> An inconsistent database state where transactions were not fully written to disk before shutdown.</p> <p><strong>Is eseutil /p safe?</strong><br> No. It removes corrupted data permanently and should only be used as a last resort when no backup is available.</p> <p><strong>Can the Exchange DB be repaired without data loss?</strong><br> Only if a valid backup exists. Native repair tools (<code>eseutil /p</code>) always involve data loss.</p> <p><strong>What causes Jet error -1018?</strong><br> Storage corruption, incomplete page writes, or hardware-level I/O issues.</p> <h2> Final Thought </h2> <p>Exchange failures are predictable — data loss is not. The difference between recovery and disaster is <strong>correct diagnosis</strong>.</p> <p><strong>Diagnose first. Repair second.</strong></p> devops exchange database sysadmin