Bug 127347 - fsck on root fs exiting with 2 breaks system startup
fsck on root fs exiting with 2 breaks system startup
Status: CLOSED DUPLICATE of bug 117641
Product: Fedora
Classification: Fedora
Component: initscripts (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2004-07-06 17:18 EDT by Krzysztof Halasa
Modified: 2014-03-16 22:46 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:04:20 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Krzysztof Halasa 2004-07-06 17:18:44 EDT
Description of problem:
/etc/rc.d/rc.sysinit treats fsck on root filesystem exiting with
code 2 as error and stops automatic system startup with sulogin.

Version-Release number of selected component (if applicable):
7.53-1 and probably earlier versions

How reproducible:
While system is booting when root filesystem needs fsck and then
reboot is required for the kernel to update in-memory filesystem

Steps to Reproduce:
1. Not trivial: umount /
2. Damage root fs data in a way which will cause fsck to return code 2
3. reboot system
Actual results:
/etc/rc.d/rc.sysinit prints:
   *** An error occurred during the file system check.
   *** Dropping you to a shell; the system will reboot
   *** when you leave the shell.
and runs sulogin.

Expected results:
System is rebooted automatically, probably after a short pause
allowing watching admin to react somehow. After reboot root
filesystem would be clean and fsck would not be run on it.
Comment 1 Bill Nottingham 2004-07-06 17:32:28 EDT

*** This bug has been marked as a duplicate of 117641 ***
Comment 2 Red Hat Bugzilla 2006-02-21 14:04:20 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.