Commentaires sur : fsck failure drops me into a shell

Par : Rob J. Caskey

Rob J. Caskey — Sat, 20 Sep 2008 15:21:27 +0000

Perhaps one of two messages:

Smart Error:

Your boot drive reports that it is suffering a hardware failure. This hardware cannot be repaired and must be replaced.

Or No Smart Error / No SMART:

Your boot drive contains errors, but no hardware errors have been detected in your hard drive. This is most commonly caused by a bad hard drive, but can also be caused by a bad cable, motherboard, or RAID card. In rare cases this can be caused by problems with your computer’s system software.

Followed By:

Some or all of your data my be recoverable.

Professional data recovery service offer the best results, but these services usually extremely expensive. If you wish to use a professional data recovery service power off your computer immediately and do not turn it on again until the drive has been replaced.

If you hear strange noises coming from the drive, you should NOT turn the power off, as it is likely the drive will no longer boot and self-data recovery will become impossible. You should select the Ignore and Attempt to Boot option, and back up your data as quickly as possible.

Self-recovery is frequently successful in temporarily restoring your drive into a working state. Backup your data immediately and replace the drive, as more severe problems are likely.

Par : Paul Collins

Paul Collins — Sat, 20 Sep 2008 12:29:59 +0000

I’ve been inspired to finally go around and set FSCKFIX=yes on all of my systems.

Par : Tester

Tester — Fri, 19 Sep 2008 22:07:22 +0000

@matthew: Yes, there is a trade-off… But sadly, the trade-off is between getting a filesystem expert (not your random sysadmin) and risking data loss.

Par : Matthew W. S. Bell

Matthew W. S. Bell — Fri, 19 Sep 2008 11:43:11 +0000

@Tester: So what you are saying is that there is that a seriously important trade-off that needs to be evaluated before any further action is taken?

Par : http://www.alexander.bostrom.net/

http://www.alexander.bostrom.net/ — Fri, 19 Sep 2008 08:01:54 +0000

I haven’t seen that prompt in _years_. It just never seem to happen with ext3. Did he somehow install it with ext2 instead?

Par : Tester

Tester — Fri, 19 Sep 2008 00:57:02 +0000

I’ve filed a bug with Fedora too.. https://bugzilla.redhat.com/show_bug.cgi?id=462804 .. lets see if they can fix their stuff

Par : Tester

Tester — Fri, 19 Sep 2008 00:45:24 +0000

@matthew: It can be handled, its just that there is a risk of further corruption (comparing to fixing it by hand with debugfs and other such expert tools..)

Par : Matthew W. S. Bell

Matthew W. S. Bell — Thu, 18 Sep 2008 23:53:05 +0000

« A serious error that cannot be handled has occured; do you want it to be handled? » Errr, wait, hang on…

Par : Craig

Craig — Thu, 18 Sep 2008 22:38:13 +0000

There is a bug in the Launchpad about this issue: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/58430

That may be the best place to have this conversation.

I completely agree that this is a serious issue that should be address. If I wasn’t quite experienced (unfortunately) with fsck et al, I’d be completely lost just as your friend was.

Par : oliver

oliver — Thu, 18 Sep 2008 22:27:02 +0000

Hongli Lai: AFAIK Windows Scandisk will only ask if it actually found a problem and wants to repair it. Usually there is nothing wrong with the filesystem after a hard shutdown, but sometimes Scandisk finds corrupted parts, and asks then.