Linux does not boot on display an error occurred during the file System__linux

Turn from: http://www.oschina.net/question/17_2280

Linux boot has disk error, disk scan progress complete after the cursor stays in

An error occured during the filesystem check
dropping to a shell; The system would reboot
When you leave the shell.

Give root password for maintainence
(or type controll-d to continue)

Prompt to enter root password

After entering the password, fsck.

Linux command:fsck

function Description: Check the file system and try to fix the error.

syntax:fsck [-aanprrstv][-t < file system type >][file system ...]

Supplemental Note: when the file system has an error Sihua, you can try to fix it with the FSCK directive.

Parameters:  -A automatically fixes the file system without asking for any questions.
-A  Check all file systems listed in the file according to the contents of the/etc/fstab configuration file. -
n  does not execute instructions, listing only the actions that are actually performed.  -P when used with the "-A" parameter, all file systems are checked at the same time. -
R  uses interactive mode to ask questions when performing repairs, allowing users to confirm and decide how to handle them.  -R when used with the "-A" parameter, the file system of the/directory is skipped.  -S performs the check job sequentially, not concurrently.
-t< file System type >  Specifies the type of file system to check.  -T displays header information when executing the FSCK directive.  -V Displays the instruction execution process.

The

Check file system integrity with fsck
File system is complex and therefore prone to errors. You can use the fsck command to check that the file system is correct and valid. It can repair the small errors found by the instructions and will not fix the error report to the user. Fortunately, the file system code is very effective, so there is very little problem at all, and the problem is usually due to power failure, hardware failure, or operation error, such as not shutting down the system properly.


Most systems are set to run fsck automatically at startup, so any errors will be detected (and modified as desired) before the system is used. Using a file system with errors can make the problem worse: if there is a problem with the data structure, using the file system can make it worse, resulting in more data loss. Of course, running fsck on a large file system takes a certain amount of time, and if the system shuts down normally, there are almost never any errors, so there are some ways to do this without checking. If the file/etc/fastboot exists, it is not checked. Also, if the ext2 file system has a specific tag in the super fast that tells the filesystem that there is no normal unmount after the last mount. If the tag indicates that unmount is properly completed (assuming normal unmount indicates that it is OK), E2fsck (fsck's Ext2 File System edition) does not check the system. Whether/etc/fastboot affects the system depends on your startup manuscript, but the ext2 tag works when you use E2fsck-based on a e2fsck option (see E2fsck man page)


Automatic checking only works on file systems that mount automatically at startup. Use fsck to manually check other file systems, such as floppy disks.


If Fsck discovers a problem for repair, you need to drill down to the general workings of the file system and the details of the file system in question, or a good backup. The final approach is easy (albeit lengthy) and can sometimes be arranged by friends, Linux newsgroups, e-mail lists, or other support sources if you don't know for yourself. I would like to tell you more, but I do not have much study and practice of this. The DEBUGFS program for Theodore T ' so should be useful.


Fsck can only run on a file system that is not mount, not for the Mount file system (except for a read-only root file system at startup). This is because it accesses the original disk and modifies the file system without the knowledge of the operating system. There'll be trouble, if the operating system is confused