/etc/fstab file error, unable to enter Linux system

Problem Description

Review Linux file system management today, mount a new hard disk on a Linux system, then partition, format, step by step, in order to enable the hard disk to boot at system startup Automatically mounted, so it was written to the /etc/fstab file. However, after reboot, the Linux system could not be started normally. The system displayed the same situation as the following figure (because it was eager to handle the fault, so there was no screenshot, then I found a few pictures on the Internet and generally recorded my own processing ideas.
According to the system prompts, it can be seen that the real reason that the system can not be started is that /etc/fstab is wrong, and the system startup report Checking filesystems fails. At this point, according to the system prompt, enter the root password into the repair filesystem mode

repair process
mount -o remount, rw /# re-mount the file system in read/write mode, re-edit /etc/fstab, modify the error As shown in the figure [Note, the latest CentOS version no longer supports writing the volume in this way. For details, please see the location given in this blog below. Address]

Summary
The above problem occurs because the /etc/fstab file is incorrectly configured. When the system is restarted, the volume label (/other) is not recognized, resulting in failure to start properly. If you run the mount -a command after modifying the /etc/fstab file to verify that the configuration is correct, you can avoid such problems. In the process of solving the problem, remount /is a more critical step (mount -o remount, rw /). Without this step, the file system is read-only, causing the configuration file not to be modified and saved.

Related Blogs

http://blog.csdn.net/zjf280441589/article/details/39480907