Her is some suggestions....
to that ...
$ sudo e2fsck -f
/dev/sdb1
e2fsck 1.41.4 (27-Jan-2009)
e2fsck: Attempt to read
block from filesystem resulted in short read while trying to open
/dev/sdb1
Could this be a zero-length partition?
$ sudo
dumpe2fs -f /dev/sdb1 | grep -i superblock
dumpe2fs 1.41.4
(27-Jan-2009)
dumpe2fs: Attempt to read block from filesystem
resulted in short read while trying to open /dev/sdb1
Couldn't
find valid filesystem superblock.
$ sudo mke2fs -n
/dev/sdb1
mke2fs 1.41.4 (27-Jan-2009)
Filesystem label=
OS
type: Linux
Block size=4096 (log=2)
Fragment size=4096
(log=2)
10010624 inodes, 40019915 blocks
2000995 blocks
(5.00%) reserved for the super user
First data block=0
Maximum
filesystem blocks=0
1222 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
________________________________________________________________________________________________
!
remember “-y” so you do not need type yes for every block
recover !
$ sudo e2fsck -f -b 32768
-y /dev/sdb1
e2fsck 1.41.4 (27-Jan-2009)
Superblock has an
invalid journal (inode 8).
Clear? yes
*** ext3
journal has been deleted - filesystem is now ext2 only ***
Pass
1: Checking inodes, blocks, and sizes
Journal inode is not in
use, but contains data. Clear? no
Error reading
block 5668 (Attempt to read block from filesystem resulted in short
read) while reading indirect blocks of inode 8. Ignore error?
yes
Force rewrite? yes
Inode 8, i_blocks is
65616, should be 57424. Fix? yes
Error reading block
1343501 (Attempt to read block from filesystem resulted in short
read) while getting next inode from scan. Ignore error?
yes
Force rewrite? yes
Error reading block
1343502 (Attempt to read block from filesystem resulted in short
read) while getting next inode from scan. Ignore error?
no
Error while scanning inodes (671744): Can't read next
inode
Recreate journal? yes
Creating journal
(32768 blocks): Error : File exists
while trying to create
journal
e2fsck: aborted
TestDisk is powerful free data recovery software! It was primarily designed to help recover lost partitions and/or make non-booting disks bootable again when these symptoms are caused by faulty software, certain types of viruses or human error (such as accidentally deleting a Partition Table). Partition table recovery using TestDisk is really easy.
just run simply in terminal, type
# photorec
and follow instruction in terminal.
the recovery tool will see like screen-shot bellow
PhotoRec in action:
download your copy here
This ‘How to’ is written to show the step by step password recovery of the Cisco Routers
. It is assumed that you have a prior knowledge of what a router is and its basic function. It is also assumed the you are having some experience of configuring the router.
Please do not follow these steps if you are a new to Routers, as this can damage the IOS or any physical interface of the router.
1.Connect a computer to the router’s Console port using the Console cable that came with your router (it is usually flat and light blue).
Use these terminal settings:
* 9600 baud rate
* No parity
* 8 data bits
* 1 stop bit
* No flow control
2.Turn the router off using the power switch and turn it back on.
3.Once text starts popping up on the screen, send the break command CTRL + B or CTRL +BREAK (sometimes it is CTRL +X). This will abort the boot and present you with a rommon 1> prompt
4.From the new prompt you need to change the configuration register using the following command: confreg 0×2142
5.If you are using an older model of router you may need to enter o/r 0×2142
6.Now you need to recycle the router with the reset command.
7.If you used the o/r command then reset the router with the I command
8.Once the router finishes restarting you will find that there are no passwords to deal with, so you can enter enabled mode carte blanche.
9.Once in enabled mode enter this: copy start run. This will copy the startup config to the running config.
10.Now, go into configuration mode with the config t command
11.Once there enter the new password with the enable secret password command (i.e. enable secret admin).
12.Now set the configuration register back to normal with this command: confreg 0×2102
13.Exit config mode and enter the command copy run start to copy the new configuration to ram.
14.Now it is time to reload your router
15.Once the router is back up you need to configure all of your interfaces with the no shutdown command or they will not work.