Red Hat Bugzilla – Bug 132346
rc.sysinit drops to shell even if fsck succeeds reparing file system
Last modified: 2014-03-16 22:48:06 EDT
Description of problem:
in /etc/rc.d/rc.sysinit (line 320 in v7.66), the return code of fsck
is checked; if > 1, the system drops the machine to an interactive
shell for manual fsck on a partition.
this is incorrect and should only happen if fsck _fails_ to repair the
problem; if fsck succeeds, the return code is 3 (1+2) and the system
should reboot automatically since no manual fsck (code 4) is needed.
Version-Release number of selected component (if applicable): all
(have tested up to 7.77)
How reproducible: every time
i've used the patch to be attached for > 1 year now and it works.
(patch will be attached on the next page)
this behavior is very annoying for clusters where the machines are
usually not connected to displays; if fsck succeeds in repairing the
file system, we really should just reboot automatically?
from /etc/rc.d/rc.sysinit around line 320
# A return of 2 or higher means there were serious problems.
if [ $rc -gt 1 ]; then
if [ -x /usr/bin/rhgb-client ] && /usr/bin/rhgb-client
--ping ; then
# SHa, Aug 2004 (for seLinux; initscript 7.66)
# drop to interactive shell only if
# fsck errors were not fixed ($rc > 3)
if [ $rc -lt 4 ]; then
echo "(Info) root file system fixed -- rebooting"
# --- SHa: end of changes ---
[keep everything below here; the sleeps are technically not
needed above, but i like to see it on the console]
*** This bug has been marked as a duplicate of 117641 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.