[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: x hung, fsck failed



on Wed, Apr 16, 2003 at 10:21:15PM -0400, Fitz Hugh Ludlow (fhludlow@sbcglobal.net) wrote:
> I finally got the stupid Nvidia Nforce motherboard chipset drivers working
> ("tainted" onboard nic, vid, sound, ide, and usb drivers) and when X started
> for the first time everything hung.  The capslock light on the keyboard
> wouldn't go on, no response to any keystrokes whatsoever, etc.  Had to power
> off.
> 
> Now of course I'm getting "fsck failed.  Please repair manually..."
> 
> What exactly should I do to fix the ext2 file system?  I mean REALLY fix it,
> fix it good, fix it permanently.  This is a clean install of woody, apt-get
> dist-upgrade to testing, and fresh new 2.4.20 kernel.
> 
> EVERY single time I've gotten a linux system off the ground it ends up
> getting destroyed because it is so fragile to power outages or crashes or
> whatever.  

If you've got unreliable power, you need a UPS.  Even journaling
filesystems (ext2, reiserfs, xfs, jfs) can't protect your data from
corruption if, say, your database crashes in the middle of a write
(though a fully ACID database should help here as well).  Nor can this
protect you against hardware damage from power surges, etc.

First point for you is to identify the source of the crashes.  In most
cases they can be traced to bad environment (e.g.:  unstable power), bad
hardware, or bad drivers.  A properly functioning GNU/Linux system does
*not* crash randomly, and band-aiding the problem by trying to
compensate for crashes is the *wrong* solution.

> Someone PLEASE clue me in on how to backup whatever I need to
> backup or do whatever I need to do to prevent these errors when the
> inevitable happens.  

    http://kmself.home.netcom.com/Linux/FAQs/backups.html


> This was my first compiled kernel and I am very frusterated.  I just
> have this sick feeling because anytime I have had a linux machine get
> powered off it was never the same again and became difficult to
> troubleshoot.

You might try running a stock kernel until you have a proper
understaning of your hardware.  Today, in most cases, building your own
kernel is *not* required (though I can't speak to Nvidia requirements).
Closed, proprietary, non-specced hardware should be avoided if at all
possible.

Peace.

-- 
Karsten M. Self <kmself@ix.netcom.com>        http://kmself.home.netcom.com/
 What Part of "Gestalt" don't you understand?
    Scandinavian Designs:  Cool furniture, affordable prices, great service,
    satisfied customer.                  http://www.scandinaviandesigns.com/



Reply to: