1) Create a situation where on boot a fsck of / succeeds in restoring
the filesystem, but changes it enough to issue the "Reboot LINUX"
message. (You might need to use ext2 for / in order for this to happen).
rc.sysinit reboots the machine.
rc.sysinit goes to "An error occurred during the file system check.
Dropping you to a shell; ..." routine.
This is especially unpleasant if the reboot is unattended.
I am seeing this with initscripts-7.46-1.1 and e2fsprogs-1.35-6.1 on
an AMD Opteron.
What's the return code of e2fsck in this case?
Here is what the man page says:
The exit code returned by e2fsck is the sum of the
0 - No errors
1 - File system errors corrected
2 - File system errors corrected, system should
4 - File system errors left uncorrected
8 - Operational error
16 - Usage or syntax error
32 - E2fsck canceled by user request
128 - Shared library error
*** Bug 127347 has been marked as a duplicate of this bug. ***
*** Bug 128117 has been marked as a duplicate of this bug. ***
At line 297 of rc.sysinit from initscripts-7.55
elif [ "$rc" = "1" ]; then
elif [ "$rc" = "2" -o "$rc" = "3" ]; then
echo $"Unmounting file systems"
mount -n -o remount,ro /
echo $"Automatic reboot in
elif [ $rc -gt 3 ]; then
if [ -x /usr/bin/rhgb-client ] &&
/usr/bin/rhgb-client --ping ; then
Also add the above at line 577 of the modified file.
This reboots in the appropriate cases.
*** Bug 132346 has been marked as a duplicate of this bug. ***
Fixed in 7.91-1.