corrupt ext3 partition

whysyn · 10-24-2005, 09:16 AM

I resized my ext3 partition using Partition Commander, rebooted into Linux (FC4) and everything seemed fine... booted up right away, straight into my Desktop with no complaints.

I then resized my Windows partition, rebooted into Windows, and everything was fine.

I booted into Linux again and got the "Enter root password or press Ctrl-D" prompt, and saw errors on screen about inconsistency in my file system.

I gave it root, and ran fsck... here's what I got:

Code:

Group XX inode table at XX conflicts with some other fs block.
Relocate? yes

hundreds (thousands?) of times, then

Code:

Root inode is not a directory.  Clear? yes

Error allocating 1022 contiguous block(s) in block group 1 for inode table: Could not allocate block in ext2 filesystem
Error allocating 1022 contiguous block(s) in block group 25 for inode table: Could not allocate block in ext2 filesystem
Error allocating 1022 contiguous block(s) in block group 49 for inode table: Could not allocate block in ext2 filesystem
Restarting e2fsck from the beginning...
/ contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes

and the whole process repeats itself. I even tried running it with the -b option and feeding it a backup supernode with no success.

This is a brand-new system that I just migrated to, and do not have a backup (I know, I've become everything I hate). It is critical for me to recover my home directory. Does anybody have any suggestions.

When I initially had the problem, it at least started booting, after a failed repair attempt, it will not even load the grub config.

whysyn · 10-25-2005, 01:53 PM

For what it´s worth, I gave up trying to fix this partition.

I mounted the hard drive in a working Windows system, and grabbed this utility:
http://www.data-recovery-software.ne...Recovery.shtml

The R-Linux utility was able to recover about 90% of what I wanted. I would highly recomend this to anybody, and best of all, it´s free!

takin · 10-26-2005, 11:12 PM

I have the same problem right now, but I can access all my data by booting up with Knoppix. I'm still working on how to restore the partition without losing all the configuration changes I've made. If I succeed, I'll let you know.

gfdecaires · 11-21-2005, 04:27 AM

I tried booting from Knoppix but once I get there it sees both my WinBlows (got me into this in the first place) and my Ubunut Linux drives though it does not see the partition that actually contains the data that I am trying to recover.
HELP!!!!!

takin · 11-21-2005, 05:30 AM

I forgot to post that I'd resolved my problem. Probably the excitement. I'd misread a friend's advice and ran
tune2fs -s 0 /dev/hda3
when it was meant to be a backup option. As soon as I reverted:
tune2fs -s 1 /dev/hda3
the e2fsck command ran without problems.

gfdecaires, can you mount the drive manually? Do you know the device name (ie, which partitiion) your data was on before you ran into trouble?

gfdecaires · 11-21-2005, 05:47 AM

When I boot into a Knoppix Live CD I have to partitions on the drive hdb1 & hdb5 that are mounted but they do not have on the data, they just seem to have the Grub files on them. Runnind fdisk -l /dev/hdb shows me that there is a third partition hdb2 but I cannot mount it. When I try the mount command it says something like (are your sure you don't mean to mount an extended partition?). I don't know where to go from here.

mariapeter12 · 07-01-2010, 11:30 PM

Quote:

Originally Posted by whysyn

I resized my ext3 partition using Partition Commander, rebooted into Linux (FC4) and everything seemed fine... booted up right away, straight into my Desktop with no complaints.

I then resized my Windows partition, rebooted into Windows, and everything was fine.

I booted into Linux again and got the "Enter root password or press Ctrl-D" prompt, and saw errors on screen about inconsistency in my file system.

I gave it root, and ran fsck... here's what I got:

Code:

Group XX inode table at XX conflicts with some other fs block.
Relocate? yes

hundreds (thousands?) of times, then

Code:

Root inode is not a directory.  Clear? yes

Error allocating 1022 contiguous block(s) in block group 1 for inode table: Could not allocate block in ext2 filesystem
Error allocating 1022 contiguous block(s) in block group 25 for inode table: Could not allocate block in ext2 filesystem
Error allocating 1022 contiguous block(s) in block group 49 for inode table: Could not allocate block in ext2 filesystem
Restarting e2fsck from the beginning...
/ contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes

and the whole process repeats itself. I even tried running it with the -b option and feeding it a backup supernode with no success.

This is a brand-new system that I just migrated to, and do not have a backup (I know, I've become everything I hate). It is critical for me to recover my home directory. Does anybody have any suggestions.

When I initially had the problem, it at least started booting, after a failed repair attempt, it will not even load the grub config.

Loosing data from ext3 system is a serious issue i thought journaling will help it out

onebuck · 07-02-2010, 08:23 AM

Hi,

Why resurrect a 5 year old thread? Nothing to contribute?

pixellany · 07-02-2010, 08:30 AM

mariapeter12;

In addition to digging up a thread that is almost 5 years old, your comment does not seem relevant to solving the problem.

If you have a question, please start a new thread.