[ext3] Input/Output error

mystia · 09-03-2003, 10:12 AM

Hello everybody !

I'm a french newbie and I need your help to recover datas.
I replaced a Mandrake 9.1 by a Debian but I saved my home directory in a hard disk partition.
At first, I made this partition with ext2 filesystem but I converted it in ext3.

I mounted the partition in the home directory of the Debian and I realized that ext3 filesystem wasn't supported.
So I installed Knoppix 3.2 which supports ext3. But all the directories aren't considered like that and I lost access on all data contained in these directories.
When I try to remove a supposed directory, I get this error :
rm : cannot lstat 'Mail' : Input/Output error

and when I try to check the filesystem :

The filesystem size (according to the superblock) is 2002092 blocks
The physical size of the device is 263056 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? no
/dev/hda7 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Error reading block 294916 (Invalid argument) while doing inode scan. Ignore error<y>? no
Error while scanning inodes (145440): Can't read next inode
e2fsck: aborted
/dev/hda7: 5830/1001920 files (0.0% non-contiguous), 194412/2002092 blocks

Is there someone who can help me ?

Thank you

quatsch · 09-04-2003, 10:30 PM

from man e2fsck:

Quote:

-b superblock
Instead of using the normal superblock, use an alternative superblock specified by superblock. This option is normally used when the primary superblock has been corrupted. The location of the backup superblock is dependent on the filesystem's blocksize. For filesystems with 1k blocksizes, a backup superblock can be found at block 8193; for filesystems with 2k blocksizes, at block 16384; and for 4k blocksizes, at block 32768.
Additional backup superblocks can be determined by using the mke2fs program using the -n option to print out where the superblocks were created. The -b option to mke2fs, which specifies blocksize of the filesystem must be specified in order for the superblock locations that are printed out to be accurate.
If an alternative superblock is specified and the filesystem is not opened read-only, e2fsck will make sure that the primary superblock is updated appropriately upon completion of the filesystem check.

so you might try with this option. Sorry, I don't know much about this fschecking stuff.

mystia · 09-05-2003, 02:27 AM

Thank you for your answer but when I do that, here is the result :

$ e2fsck -b 8193 /mnt/hda7
e2fsck 1.34-WIP (21-May-2003)
e2fsck: Is a directory while trying to open /mnt/hda7

The superblock 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 superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

Is there a command like this for ext3 filesystem ?

mystia · 09-05-2003, 02:47 AM

I found the command for ext3 filesystem

$ fsck -t ext3 <device>

but I get the same error message ...

quatsch · 09-05-2003, 08:52 AM

not /mnt/hda7. This is the mount point which is a directory.
try with
/dev/hda7
instead.