What a disaster to find that your File Allocation Table is been destroyed.
Well there is a possible light at the end of the tunnel.
Scenario:
Partition to recover: /dev/sdb2
HOW-TO
– Find out where the SuperBlock got backed-up with the command
mke2fs -n
This gives you all the locations where the SuperBlock is back-up
eg.
mke2fs -n /dev/sdb2
.
mke2fs 1.41.3 (12-Oct-2008)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
69648384 inodes, 278563083 blocks
13928154 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
8502 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848
– Now I’ll be using one of the backup locations to fix the filesystem:
fsck.ext3 -b 884736 /dev/sdb2
This will use the back-up block address to try to recover the files.
After answering some repair questions with ‘y’ the program qill quit and you should hav your files back.
If not then the damage has been done deeper and probably all the files were deleted.