root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

SUMMARY

Boot failure stating: root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

ISSUE

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.

An example file system error is displayed, below:

Checking filesystems
root contains a file system with errors, check forced.
root:
Inodes that were part of a corrupted orphan linked list found.

root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
 

RESOLUTION

To run a file system check to repair filesystem errors

 
  1. When a file system error is encountered, first restart the appliance manually (from the hypervisor client, select the virtual machine and click restart).
  2. When the appliance restarts, the following message is displayed:
    root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
  3. At this point,  A root prompt is displayed requesting the root OS password (default is unitrends1 or the password set for ssh access)
  4. Next, type fsck followed by Enter.
  5. At each prompt thereafter, type to continue the process.
  6. When complete, restart the appliance again.

CAUSE

This issue can result from improper shutdowns of the appliance for hard resets, power failures, hard disk errors etc...

Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section