Fixing an Ext3 FS

[Amichai Rotman]

Hi Guys and Gals,

I have two HDs: 1 for / and /home and another for my data collection
(music, funnies, pix etc.).

I did somethig stupid and hang my machine - so I had to ¨turn it off
uncleanly¨...

When I try to run fsck.ext3 on it I get this:

<-- snip -->
i_file_acl for inode 16416 (...) is 465902557, should be zero.
Clear<y>? yes

Inode 16416 (...) has a bad mode (0163644).
Clear<y>? yes

i_file_acl for inode 16417 (...) is 3952012214, should be zero.
Clear<y>? yes

i_faddr for inode 16417 (...) is 3931302522, should be zero.
Clear<y>? yes

i_frag for inode 16417 (...) is 213, should be zero.
Clear<y>? yes

i_fsize for inode 16417 (...) is 233, should be zero.
Clear<y>? yes

Segmentation fault

<-- end -->

I had to answer yes to each question because it claimes I cannot run
it with -a or -p options.

I know some of the data is fixed - but I cannot mount it.

Here is the mke2fs output for this device:

[root at pinguino ~]# mke2fs -n /dev/hdd
mke2fs 1.36 (05-Feb-2005)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
3670016 inodes, 7329168 blocks
366458 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=8388608
224 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
      32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
      4096000

Anything I can do? Please Help!!!

All my stuff is on that device...

Thanks


-- 
:====================================================:.

Amichai Rotman

UIN#: 6401746
Registered Linux User#: 201192

-----------------------------------------------------------------------------------

PLEASE READ: http://www.fsf.org/philosophy/no-word-attachments.html

-----------------------------------------------------------------------------------------------------------