The most effective solution to the "An error occurred during the file system check" error after Linux hard disk mounting is restarted

Since I have recently studied the application and development of QT, the first step is to build a development environment. However, it is found that the hard disk space allocated to the virtual machine is obviously insufficient, resulting in the installation of qt_sdk failure.

As a result, I searched the internet for methods to expand the hard disk space, and browsed countless websites. However, there were two basic ideas:

1. The hard disk space is extended on the basis of the original hard disk, but the steps are too troublesome, and accidental damage to the original content of the hard disk may occur, so this method is not considered for the moment.

2. Create a new hard disk on the VM, open enough space, and then mount it to Linux.

The second method I selected. For more information, see the previous article.Article.

However, an error occurred during the file system check prompt is displayed in reboot after all steps are completed. In addition, the system is notified that you can either enter the root password to fix the problem or press Ctrl + D to skip it. Obviously, you cannot jump to the desktop. You can only enter a password to fix the problem. But where is the problem? Which step is incorrect?

In the first place, I realized that the last operation was to use the VI/etc/fstab command to add new mount content. So the problem must have occurred, I just need to delete the previously added mounting statement. Isn't the problem solved? Yes, it is. But the problem comes again. fstab is in read-only status and the content cannot be updated at all. What do you do: WQ! It is also futile. But I had to go to Google to find a solution.

Most of the information on the Internet is that fsck [-aanprrstv] [-T <file system type>] [file system...] the command method can solve the problem, but I tried it several times without any effect.

Some comrades also hold another point of view and use livecd for rescue mode to solve the problem. Frankly speaking, I don't know the livecd or rescue mode. So we will continue to explore another solution.

If you are interested, you will not be able to afford it. The ancients summed up the results. Finally, we found an effective solution:

Use "Mount-n-o remount, RW/" to re-mount the root directory. Then modify the error. Note that fstab can be read and written at this time. All problems can be solved.

You only need to delete the mounting statement, and then save and exit WQ. Then, reboot is reloaded to the system again. Is that correct?

Be patient and look for more information. There is always a solution. Never give up halfway.