Note: if there is several inode or block bitmap blocks
which require relocation, or one part of the inode table
which must be moved, you may wish to try running e2fsck
with the '-b 8193' option first.  The problem may lie only
with the primary block group descriptor, and the backup
block group descriptor may be OK.

Inode table for group 0 is not in group.  (block 40000)
WARNING: SEVERE DATA LOSS POSSIBLE.
Relocate? yes

../e2fsck/e2fsck: A block group is missing an inode table while reading bad blocks inode
This doesn't bode well, but we'll try to go on...
Pass 1: Checking inodes, blocks, and sizes
Relocating group 0's inode table to 5...
Restarting e2fsck from the beginning...
Pass 1: Checking inodes, blocks, and sizes
Root inode is not a directory.  Clear? yes

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Root inode not allocated.  Allocate? yes

Pass 4: Checking reference counts
Pass 5: Checking group summary information
Fix summary information? yes

Block bitmap differences: -10 -11 -12 -13 -14 -15 -16 -17 -18 -19 -20 -21.  FIXED
Free blocks count wrong for group 0 (78, counted=90).  FIXED
Free blocks count wrong (78, counted=90).  FIXED
Inode bitmap differences: -11.  FIXED
Free inodes count wrong for group #0 (21, counted=22).  FIXED
Directories count wrong for group #0 (2, counted=1).  FIXED
Free inodes count wrong (21, counted=22).  FIXED

test_filesys: ***** FILE SYSTEM WAS MODIFIED *****
test_filesys: 10/32 files (0.0% non-contiguous), 10/100 blocks
Exit status is 1