Find the answer to your Linux question:
Results 1 to 9 of 9
Hello I can't boot my system (Debian Sarge) because of a file system corruption. It says, that I have to do it manually. I launched the mepis live CD, and ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Dec 2005
    Posts
    25

    Emergency - file system corrupt -solved


    Hello
    I can't boot my system (Debian Sarge) because of a file system corruption. It says, that I have to do it manually. I launched the mepis live CD, and this is what a utility for checking hard drives said:



    Code:
    Checking/repairing filesystem (e2fsck) on /dev/sda1.
    /sbin/e2fsck
    : 
    Bad magic number in super-block
     
    while trying to open /dev/sda1
     
    
    /dev/sda1: 
    
    The 
    super
    block
     could not be read or does not describe a correct ext2
    
    filesystem
    .  If the 
    device
     is valid and it really contains an ext2
    
    filesystem
     (and not swap or ufs or something else), then the 
    super
    block
    
    is corrupt, and you might try running e2fsck with an alternate 
    super
    block
    :
        e2fsck -b 
    8193
     <
    device
    >
    
    
    Check completed.
    Checking/repairing filesystem (e2fsck) on /dev/sda1.
    e2fsck 1.37 (21-Mar-2005)
    
    Couldn't find ext2 superblock, trying backup blocks...
    
    /sbin/e2fsck
    : 
    Bad magic number in super-block
     
    while trying to open /dev/sda1
     
    
    
    The 
    super
    block
     could not be read or does not describe a correct ext2
    
    filesystem
    .  If the 
    device
     is valid and it really contains an ext2
    
    filesystem
     (and not swap or ufs or something else), then the 
    super
    block
    
    is corrupt, and you might try running e2fsck with an alternate 
    super
    block
    :
        e2fsck -b 
    8193
     <
    device
    >
    
    
    Check completed.
    Please help, I've got some extremely important stuff there I don't know what to do

    Thanks in advance for any help

    I have a SATA drive
    sda1 is my root partition
    My entire drive has reiserFS.

  2. #2
    Linux Engineer rcgreen's Avatar
    Join Date
    May 2006
    Location
    the hills
    Posts
    1,134

  3. #3
    Just Joined!
    Join Date
    Dec 2005
    Posts
    25
    Thanks, problem sovled
    hardware is to blame - bad RAM. A friend of mine suggested testing this and it turned out that I have bad memory. Debian still seems to be indestructible
    Thx

  4. #4
    Just Joined!
    Join Date
    Jun 2006
    Posts
    4
    I have the same problem.
    It says:
    fsck failed. Please repair manually and reboot. Please note that the root file system is currently mounted read-only. To remount it read-write:

    # mount -n -o remount,rw /
    I typed that and then I've runed reiserfsck and then it says that the partition permissions are set to read-only.

    How to change my partition permissions to read-write???

    I have reiserfs file system. It's on /dev/hda8

    Help, please!

    P.S. Sorry for my bad English.

  5. #5
    Linux User
    Join Date
    Feb 2006
    Posts
    484
    post the output of the following command

    ls -l /dev/hda8

  6. #6
    Just Joined!
    Join Date
    Jun 2006
    Posts
    4
    Quote Originally Posted by iwanabeguru
    post the output of the following command

    ls -l /dev/hda8
    Here's the output:

    brw-rw---- 1 root disk 3, 8 Feb 26 2005 /dev/hda8

  7. #7
    Just Joined!
    Join Date
    Sep 2006
    Posts
    21

    Myro try this:

    1. Boot to single user mode (maintenance mode) and give root pasword.
    2. Manually run fsck -y.
    3. Remount the file system as read/write (mount -n -o remount,rw /).
    4. Reboot the system to run level 2.

    It may want to do an automatic fsck on reboot. That's fine if it does.

    Hope this helps.

  8. #8
    Just Joined!
    Join Date
    Jun 2006
    Posts
    4
    Quote Originally Posted by MainFrame185
    1. Boot to single user mode (maintenance mode) and give root pasword.
    2. Manually run fsck -y.
    3. Remount the file system as read/write (mount -n -o remount,rw /).
    4. Reboot the system to run level 2.

    It may want to do an automatic fsck on reboot. That's fine if it does.

    Hope this helps.

    Thanks for help! I tryed this and fixed filesystem, but now I have another problem.

    It says:
    chroot: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
    Kernel panic: Attempted to kill init!
    Does anybody know how to fix this? Could I boot Knoppix and manually copy this library on the linux partition on my hard disk?

  9. #9
    Just Joined!
    Join Date
    Jun 2006
    Posts
    4
    I tried to copy libc.so.6 manually with Knoppix, but without success.
    Now I've installed Ubuntu. Hopefully there will be nothing wrong with that distro.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •