https://qa.mandrakesoft.com/show_bug.cgi?id=2058
------- Additional Comments From [EMAIL PROTECTED] 2003-02-24 09:50 ------- does it print "LINUX MUST REBOOT" or something like that ? since e2fsck directly scan and fix the ext2 fs (thus bypassing the vfs, ext2fs and block layers of the linux kernel), the in-kernel cached data may not be synced with the hard disk contents. in that case, e2fsck print a message requesting you to reboot and returning a return value such that initscripts failled ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: Either rc.sysinit or fsck is causing this, but it started after I updated recently and got the new e2fsprogs. Once fsck runs successfully, rc.sysinit sees this as a failure and drops you to a shell. Is it possible that the return codes from fsck have changed and rc.sysinit needs to be updated so it knows a real failure from a success?
