This bug was fixed in the package sysvinit - 2.86.ds1-14.1ubuntu45
---------------
sysvinit (2.86.ds1-14.1ubuntu45) hardy; urgency=low
* Fix handling of fatal fsck errors in the usplash integration. (LP: #209416)
- usplash-fsck-functions.sh: When fsck exits with an error > 1, this
signals a non-correctable failure, which will trigger sulogin. Quit
usplash in this case and restore stdin/out/err, so that the following
sulogin is actually usable.
- check{root,fs}.sh: Redirect fsck's stdout/err to /dev/console in usplash
mode, so that the user will see the "RUN fsck MANUALLY" warning.
-- Martin Pitt <[EMAIL PROTECTED]> Wed, 16 Apr 2008 17:34:20
+0200
** Changed in: sysvinit (Ubuntu)
Status: Fix Committed => Fix Released
--
fsck not repairing corruption on boot
https://bugs.launchpad.net/bugs/209416
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
