Unexpected inconsistency error when Linux starts system

The following error occurred while booting the system.

This means identifying the problem when confirming the file system, and here's how to fix the file system error.

Checking filesystems

/12:unexpected inconsistency; RUN fsck manually.
(i.e., without-a or-p options)

An error occurred during the file system check.
dropping to a shell; The system would reboot
When you leave the shell.
Give root password for maintenance
(or type control-d to continue):

Enter the root password according to the prompts.

Give root password for maintenance
(or type control-d to continue): <-Enter the password of the root user

Initiates the file system repair script and then uses the Mount command to confirm the distinction of the hard drive that needs to be repaired.

(Repair filesystem) 1 # Mount
/dev/hda6 on/type ext3 (rw) <-here/dev/hda6 is a hard drive to repair

Repair using the fsck command, specifying the file system type and version with the-t option.
There will be more than a few confirmation messages, all entered enter (that is, yes).

(Repair filesystem) 2 # fsck-t Ext3/dev/hda6 start Repair
Fsck 1.39 (29-may-2006)
E2fsck 1.39 (29-may-2006)
/12 contains a file system with errors, check forced.
Pass 1:checking inodes, blocks, and sizes
Inode 97349 has a bad extended attribute block 21760.
Clear? <-enter

Inode 97249, I_blocks is 8, should to 0.
Fix it? <-enter
Omitted
Inodes that were part of a corrupted orphan linked list found.
Fix it? <-enter

Inodes 1855559 is part of the orphaned inode list. FIXED.
Omitted
Deleted inode 1856596 has zero dtime.
Fix it? <-enter
Omitted
Extended attribute block 1868847 has reference count 131,
should be 130. 　Fix it? <-enter
Omitted
/12: * * * * FILE SYSTEM was MODIFIED * * * * *
/12: * * * REBOOT LINUX * * * *
/12:107499/2560864 files (1.5% non-contiguous),
936536/2560351 blocks
(Repair filesystem) 3 # Exit <-out of Repair mode

The restoration of the system after the end of the file system repair, in general, will be able to repair the success, in case the repair fails, you need to restore from the system backup.

# reboot