[mdlug] e2fsck - What to do?
Stan Green
Stan at mcomputersolutions.com
Sun Aug 3 22:07:28 EDT 2008
First a little background:
I was copying data over NFS when the target computer locked up. I had to
hard-boot it to get it back. When it came back up, the drive I was copying to
was not mounted. (Normally it is.) The log showed:
EXT2-fs error (device hdg1): ext2_check_descriptors: Block bitmap for group
1280 not in group (block 65545)!
EXT2-fs: group descriptors corrupted!
So I ran mke2fs -n /dev/hdg1 to which gave me a superblock, 98304 that I could
use. I than ran: e2fsck -b 98304 /dev/hdg1
This started producing a large number (I canceled once and it showed 511
errors) of error all in the pattern:
Block bitmap for group 0 is not in group. (block 1493433566)
Relocate<y>? yes
Inode bitmap for group 0 is not in group. (block 772925346)
Relocate<y>? yes
Inode table for group 0 is not in group. (block 1931314432)
WARNING: SEVERE DATA LOSS POSSIBLE.
Relocate<y>?
The question is am I on the right track to recover this drive and if so what
should I answer to the last question. (I don't want SEVERE DATA LOSS!) I was
answering No, but quit after about 40 sets of messages. Lastly, is there any
way to automate this so I don't have to sit an hit Y 1500 times?
Thanks,
Stan Green
More information about the mdlug
mailing list