Ask the Community
Groups
root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>Boot failure stating: root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <p>If a Unitrends appliance fails to start and a file system error is displayed in the hypervisor client console (or onscreen for physical appliances), on reboot the appliance will need a manual file system check (fsck) to correct the problem.</p> <p>An example file system error is displayed, below:</p> <blockquote class="blockquote"> <p>Checking filesystems<br>root contains a file system with errors, check forced.<br>root:<br>Inodes that were part of a corrupted orphan linked list found.<br><br>root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.<br><br>*** An error occurred during the file system check.<br>*** Dropping you to a shell; the system will reboot<br>*** when you leave the shell.<br> </p> </blockquote> <h2 data-id="resolution"><strong>RESOLUTION</strong></h2> <p></p> <table><tbody><tr><td colspan="1" rowspan="1"> <table border="0" cellpadding="0" style="border-spacing: 0px;"><tbody><tr><td colspan="1" rowspan="1"> <p>To run a file system check to repair filesystem errors</p> <blockquote class="blockquote"> </blockquote> <ol><li>When a file system error is encountered, first restart the appliance manually (from the hypervisor client, select the virtual machine and click restart).</li> <li>When the appliance restarts, the following message is displayed: <blockquote class="blockquote">root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.</blockquote> </li> <li>At this point, A root prompt is displayed requesting the root OS password (default is unitrends1 or the password set for ssh access)</li> <li>Next, type <strong>fsck </strong>followed by <strong>Enter</strong>.</li> <li>At each prompt thereafter, type <strong>y </strong>to continue the process.</li> <li>When complete, restart the appliance again.</li> </ol></td></tr></tbody></table></td></tr></tbody></table><h2 data-id="cause"><strong>CAUSE</strong></h2> <p>This issue can result from improper shutdowns of the appliance for hard resets, power failures, hard disk errors etc...</p> </article> </main>