[Bug 385882] Re: if fsck exits with error code 4 no way for non-experts to recover

[Dmitrijs Ledkovs]

** Changed in: mountall (Ubuntu)
     Assignee: (unassigned) => Dmitrijs Ledkovs (xnox)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/385882

Title:
  if fsck exits with error code 4 no way for non-experts to recover

Status in “mountall” package in Ubuntu:
  New

Bug description:
  Binary package hint: sysvinit

  When mounting the rootfs fails because of fsck exiting with error code
  >= 4 the user sees a message that he/she needs to manually run a file
  system check. It does not tell the user how to do that. A non-expert
  is left in the dark at this point how to restore his system.

  Booting into recovery mode (and use the fsck option there) does not
  work either because the checkroot.sh is still run and drops to a
  shell.

  I would like to improve the error output to contain instructions what the user needs to do, something like:
  --- sysvinit-2.86.ds1/debian/initscripts/etc/init.d/checkroot.sh        2009-06-11 13:14:03.000000000 +0200
  +++ sysvinit-2.86.ds1/debian/initscripts/etc/init.d/checkroot.sh        2009-06-11 13:14:05.000000000 +0200
  @@ -320,9 +320,10 @@
                  # Surprise! Re-directing from a HERE document (as in "cat << EOF")
                  # does not work because the root is currently read-only.
                  log_failure_msg "An automatic file system check (fsck) of the root filesystem failed.
  -A manual fsck must be performed, then the system restarted.
  +A manual fsck  must be performed, then the system restarted.
   The fsck should be performed in maintenance mode with the
   root filesystem mounted in read-only mode."
  +               log_failure_msg "Please run \"fsck $rootdev\" manually to fix the problem."
                  log_warning_msg "The root filesystem is currently mounted in read-only mode.
   A maintenance shell will now be started.
   After performing system maintenance, press CONTROL-D

  In addition we may consider ignoring this failure and continue booting
  in ro-mode when the user selects the recovery option and/or check for
  /usr/share/recovery-mode/recovery-menu and use that in favor of
  sulogin (if available).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/385882/+subscriptions