Red Hat Bugzilla – Bug 128117
Improperly handles FSCK result
Last modified: 2014-03-16 22:46:47 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4)
Description of problem:
When the initial fsck is run and the result is some minor fixes are
performed, the return code is 2 or 3. In these cases, fsck is
suggesting a reboot of the system.
This should be handled automatically by the script. It should follow
the path to automatically rebooting the system, not hang waiting for
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create a minor file system error (dtime != 0)
3. wait for fsck to finish, it reports:
*** REBOOT LINUX ***
4. System prompts for root password or Ctrl-D to restart.
Actual Results: System waits for user input without completing boot
Remote servers can't be restarted without someone there to monitor
them in case something like this pops up.
Expected Results: System should reboot automatically, as requested by
the fsck return code.
Something like this:
if [ -z "$fastboot" -a "X$ROOTFSTYPE" != "Xnfs" ]; then
STRING=$"Checking root filesystem"
initlog -c "fsck -T -a $fsckoptions /"
if [ "$rc" = "0" ]; then
elif [ "$rc" = "1" ]; then
elif [ "$rc" = "2" -o "$rc" = "3" ]; then
echo $"Unmounting file systems"
mount -n -o remount,ro /
echo $"Automatic reboot in progress."
# A return of 4 or higher means there were serious problems.
if [ $rc -gt 3 ]; then
if [ "$BOOTUP" = "graphical" ]; then
This needs to be implemented in two places in the rc.sysinit script.
*** This bug has been marked as a duplicate of 117641 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.