Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi all, I'm using FC4 at a friend's house; he had a system crash some days ago, so I decided to run 'shutdown -Fr now' to force fsck upon next boot. The problem is I got this error when booting:
***An error has ocurred during filesystem verification
***You will be returned to a shell; the system will reboot when you exit the shell
***Warning -- SELinux is active
***Disabling security enforcement for system recovery
***Run 'setenforce 1' to reenable
Give root password for maintenance
(or type Control-D to continue):
When I press ctrl-d the system reboots and forces fsck upon boot. I tried with 'init 0' 'init 6' 'shutdown -fr now' and the system restarts with the same error. My question is, how do I toggle off the fsck forcing upon boot?? Thanks in advance.
The system startup script that controls rebooting, e.g. /etc/rc.d/rc.sysinit, will include the logic to test to see if you want to do an fsck on reboot. It probably checks for the existence of a sentinel file in the root directory: distributions vary on this. Removing the file should eliminate the check.
On my system, man shutdown says this:
Quote:
The -F flag means ‘force fsck’. This only creates an advisory file /forcefsck which can be tested by the system when it comes up again.
The boot rc file can test if this file is present, and decide to run
fsck(1) with a special ‘force’ flag so that even properly unmounted
filesystems get checked. After that, the boot process should remove /forcefsck.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.