checkroot think that "* Filesystem couldn't be fixed :(" just beacause fsck doesn't return a value of 0 or 1. Instead with the return value of "3" (as said in "man fsck") fsck is just saying that the errors has been corrected and the system should be rebooted (the output of fsck in fact says "***** REBOOT LINUX *****") Reproducible: Always Steps to Reproduce: 1. Have a problem on root partition 2. Reboot 3. Actual Results: /etc/init.d/checkroot claims that the filesystem could not be repaired while it's not the truth. Expected Results: /etc/init.d/checkroot should have told to the user that his system just need a reboot and that the filesystem instead has been fixed. Maybe it should perform an automatic reboot. fsck 1.33 (21-Apr-2003) e2fsck 1.33 (21-Apr-2003)
Its beed fixed in July already: -- elif [ "${retval}" -eq 2 -o "${retval}" -eq 3 ] then ewend 1 "Filesystem repaired, but reboot needed!" echo -ne "\a"; sleep 1; echo -ne "\a"; sleep 1 echo -ne "\a"; sleep 1; echo -ne "\a"; sleep 1 ewarn "Rebooting in 10 seconds ..." sleep 10 einfo "Rebooting" /sbin/reboot -f
