e2fsck hangs whole O/S

Help
Steph Reed
2008-02-03
2012-11-28
  • Steph Reed

    Steph Reed - 2008-02-03

    Hi

    I have a corrupt filesystem, and have been trying to use e2fsck on it. I downloaded and compiled the latest version (10.40.5). It is the second partition on an IDE drive, and the 1st one seems fine.

    The first time I ran it, it seemed to fix a lot of errors, and then when I came back to my PC it was hanging, so I rebooted into RunLevel 3 (previously had been in normal, as this is not the main O/S drive) and tried again. It seems to go for a bit and then hung the whole system again.

    It does this every time. Here is what I saw in dmesg that prompted me to run it:

    EXT2-fs: corrupt root inode, run e2fsck

    Its a little worrying that it takes down the whole operating system with it (Fedora 7), requiring a hard-reset. Here is the output from e2fsck:

    Videos contains a file system with errors, check forced.
    Pass 1: Checking inodes, blocks, and sizes
    Root inode is not a directory.  Clear? yes

    Pass 2: Checking directory structure
    Missing '..' in directory inode 180225.
    Fix? yes

    Entry '..' in ... (180225) has deleted/unused inode 2.  Clear? yes

    Missing '..' in directory inode 1212417.
    Fix? yes

    Entry '..' in ... (1212417) has deleted/unused inode 2.  Clear? yes

    Missing '..' in directory inode 1245185.
    Fix? yes

    Entry '..' in ... (1245185) has deleted/unused inode 2.  Clear? yes

    Missing '..' in directory inode 2326529.
    Fix? yes

    Entry '..' in ... (2326529) has deleted/unused inode 2.  Clear? yes

    Missing '..' in directory inode 5292033.
    Fix? yes

    Entry '..' in ... (5292033) has deleted/unused inode 2.  Clear? yes

    Missing '..' in directory inode 11960321.
    Fix? yes

    Entry '..' in ... (11960321) has deleted/unused inode 2.  Clear? yes

    Missing '..' in directory inode 11960345.
    Fix? yes

    Entry '..' in ... (11960345) has deleted/unused inode 2.  Clear? yes

    Missing '..' in directory inode 13205505.
    Fix? yes

    Entry '..' in ... (13205505) has deleted/unused inode 2.  Clear? yes

    Missing '..' in directory inode 18055169.
    Fix? yes

    Entry '..' in ... (18055169) has deleted/unused inode 2.  Clear? yes

    Pass 3: Checking directory connectivity
    Root inode not allocated.  Allocate? yes

    If anyone has any ideas where I proceed from here I would be most grateful, it would be a real pain if I can't get the drive to mount again.

     
    • Steph Reed

      Steph Reed - 2008-02-09

      Just an update, when I run it without the -y option I get 1 line further:

      Error reading block 23953409 (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps.  Ignore error<y>?            

      Clicking y always hangs Linux a little after this point. Does anyone have any ideas what I can do?

      Some other forums suggested buying some commercial recovery software for about 80 US$, but since I don't have Windows, I would need to get that too first, which is just defying the whole point of using Linux!

      Help please...

       

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks