EXT3-fs: corrupt root inode after resize
After a partition resize my 500GB USB2 disk refuses to mount, disk was ext3 partition, gparted & qtparted now recognizes it as ext2
Code:
root@ubuntu:/#fsck -y /dev/sda1
giving me a lot of "Group x's inode table at xxxxx conflicts with some other fs block." Relocate<y>? yes"
until " Root inode is not a directory. Clear? yes " Aaaaargh, damn ......
error 8 popped up, but didn't halt process, left it running for 50 hours before quiting it.
it gave me also a couple of following mesages ( I included further a #dumpe2fs -h /dev/sda1 )
"Programming error? block #71663648 claimed for no reason in process_bad_block"
"Programming error? block #78676000 claimed for no reason in process_bad_block."
"Programming error? block #102400032 claimed for no reason in process_bad_block."
etc...
Code:
root@ubuntu:/# mount /dev/sda1 /media/500gb/
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Code:
root@ubuntu:/# dmesg | tail
[17179650.572000] Bluetooth: L2CAP ver 2.8
[17179650.572000] Bluetooth: L2CAP socket layer initialized
[17179651.772000] Bluetooth: RFCOMM socket layer initialized
[17179651.772000] Bluetooth: RFCOMM TTY layer initialized
[17179651.772000] Bluetooth: RFCOMM ver 1.7
[17181754.432000] EXT2-fs: corrupt root inode, run e2fsck
testdisk reveals EXT2 Large file Sparse superblock, 497 GB / 463 GiB
gparted & qtparted are showing an ext2 partition
Code:
root@ubuntu:/# lde /dev/sda1
User requested autodetect filesystem. Checking device . . .
Found ext2fs on device.
Warning: First block (0) != Normal first block (1)
root inode isn't a directory
Code:
root@ubuntu:/# dumpe2fs -h /dev/sda1
dumpe2fs 1.39 (29-May-2006)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: 0ef5a677-47fb-4bae-aee0-a25bc58bfd4a
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: resize_inode dir_index filetype sparse_super large_file
Default mount options: (none)
Filesystem state: not clean with errors
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 60735488
Block count: 121453400
Reserved block count: 6072670
Free blocks: 10644662
Free inodes: 60563151
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 1024
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16384
Inode blocks per group: 512
Filesystem created: Sat Feb 24 13:51:53 2007
Last mount time: Wed Mar 14 17:16:31 2007
Last write time: Wed Mar 14 17:30:45 2007
Mount count: 1
Maximum mount count: 29
Last checked: Wed Mar 14 16:31:47 2007
Check interval: 15552000 (6 months)
Next check after: Mon Sep 10 17:31:47 2007
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Default directory hash: tea
Directory Hash Seed: 25354299-dd40-40db-928a-47b1cd3bf8b6
Journal backup: inode blocks
Bad blocks: 7962656, 11239456, 20480032, 23887904, 71663648, 78676000, 102400032 ( see first part of message )
For sure there's a filesystem there....
started fsck again
again a lot of "Group x's inode table at xxxxx conflicts with some other fs block." Relocate<y>? yes"
and
"Programming error? block #71663648 claimed for no reason in process_bad_block"
"Programming error? block #78676000 claimed for no reason in process_bad_block."
"Programming error? block #102400032 claimed for no reason in process_bad_block."
currently it's still running ( 64 hours now, is this normal ? )
lde is probably able to correct this, but I thought it would be wise if one of the gurus out there would help me out on this.
Rlinux ( free application on http://www.data-recovery-software.ne...Recovery.shtml is able to recover about 70% of my data.
Nucleus Kernel Linux ( not free, 49$ http://www.nucleustechnologies.com/ ) is able to recover ALL of my data
any help is highly appreciated
Jan
