HELP! Linux 911... (fsck/HDD failure)

From: Joe Cipale (joec_at_aracnet.com)
Date: 02/25/04

  • Next message: Brian Reiahle: "Re: Conspiracy theory: MS leaked the Win2k code *on* *purpose*" 
    Date: Tue, 24 Feb 2004 18:18:19 -0800

    Sandy/Sean/whomever...

    Bad mojo took place today at the home office in Topeka, KS (aka my house).

    I have SuSE 7.2 running. My desktop locked-up. HARD! I mean no mouse, no
    keyboard, unable to toggle desktops from KDE. I did a hard shutdown (power
    cycle).

    While watching the system perform the fsck, I observed the following error
    message:
    /dev/hda3 contains file system with errors, check forced.
    /dev/hda3
    Unattached inode 1212796

    /dev/hda3: UNEXPECTED INCONSISTENCY; Run fsck MANUALLY.
        (i.e., without -a or -p options)
    fsck.ext2 /dev/hda3 failed (status 4)! Run it manually!
    .
    .
    .
    .

    fsck failed. Please repair manually and reboot. The root
    file system is currently mounted read-only. To remount
    it read-write do:
        bash# mount -n -o remount,rw /

    Attention: Only CONTROL-D will reboot the system in this
    maintenenance mode. shutdown or reboot will not work.

    After logging in as root, I am in the (repair filesystem)# mode.

    I have tried the following with no success:
    (e2)fsck /dev/hda3 --> WARNING!!! Running e2fsck on a mounted filesystem may
    cause
                                    SEVERE filesystem damage.

    I can get to my data (read only, obviuosly) and can view it. I can access it
    from this 'file fix' prompt (command-shell). I am just unable to boot the
    filesystem. Can anyone give me some pointers on what to do here?

    Private email is okay.

    Joe Cipale

  • Next message: Brian Reiahle: "Re: Conspiracy theory: MS leaked the Win2k code *on* *purpose*"

    Relevant Pages

    • HELP! Linux 911... (fsck/HDD failure)
      ... My desktop locked-up. ... /dev/hda3 contains file system with errors, ... Please repair manually and reboot. ... I am in the (repair filesystem)# mode. ...
      (alt.os.linux.suse)
    • Re: prevent fs check after being up for a long time
      ... Issue was that i was told that as a particular filesystem has not been ... Another solution when you are going to reboot the system ... remount the file system 'read-only' and do a quicky fsck. ... Even the virtually unsupported RH9 has had two kernel errata ...
      (linux.redhat)
    • Re: Printer not working after a short circuit
      ... > system will reboot when you leave the shell. ... Give root password for maintenance or type Control-D to ... Run fsck manually. ... > entire file system and prompted me as to whether or not to continue. ...
      (microsoft.public.windowsxp.hardware)
    • Re: Set all files on Windows XP to a specified create & access date
      ... >I did belaatedly reboot (why wouldn't the change take hold ... would be some sort of security enhancement. ... note that the name of the registry refers to disabling the Last ... Do you understand that the NTFS file system maintains 3 ...
      (microsoft.public.security)
    • Re: Checking the integrity of the file system
      ... I now check whether my file system is not corrupted? ... I do not see the result of 'shutdown -rF now'... ... Thats a root only command for starters, and it should have made the machine reboot, during which the fsck on the file systems would have been done, however you may have to edit /boot/grub/grub.conf to remove the 'rhgb' from the kernels boot command line before you would see anything because it would otherwise be hid behind a graphic and all you would see is a longer bootup time. ...
      (Fedora)