← Back to team overview

touch-packages team mailing list archive

[Bug 58430] Re: Command-line recovery required when fsck reports an unexpectedy inconsistency

 

This is not a bug: it is working as intended since the repair may cause
data loss, it really does need manual user intervention, likely with a
backup being made first.


** Changed in: util-linux (Ubuntu)
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/58430

Title:
  Command-line recovery required when fsck reports an unexpectedy
  inconsistency

Status in util-linux package in Ubuntu:
  Invalid
Status in Fedora:
  Won't Fix

Bug description:
  When there is an ext3 filesystem error and fsck fails to correct it,
  the system becomes unusable.  It asks the user to perform fsck
  manually in a very cryptic way.  The average user can in no way
  understand what has happened to their system.  In most cases a simple
  fsck /dev/hdaX (whatever partition required the check) will end up
  solving the problem.  This should be done automatically.

  Here is the output of what happened to a friend of mine who rebooted
  and had to use windows because they couldn't start ubuntu:

  ----------------------------------------------------------------------------
  The following appears when i try to boot ubuntu:

  dev/hda2 contains a file system with errors-check forced

  unexpected inconsistency RUN fsck manually without -a or -p options

  an automatic file system check of the root file system failed

  a manual fsck must be performed then system rebooted
  -----------------------------------------------------------------------------

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/58430/+subscriptions