e2fsck: Bad magic number in super-block while trying to open /dev/vda2

Units = sectors of 1 * 512 = 512 bytes 
Sector size (logical/physical): 512 bytes / 512 bytes 
I/O size (minimum/optimal): 512 bytes / 512 bytes 
Disk identifier: 0x0005ddb2 
Device Boot Start End Blocks Id System 
/dev/vda1 * 2048 473958399 236978176 83 Linux 
/dev/vda2 473960446 490731519 8385537 5 Extended 
/dev/vda5 473960448 490731519 8385536 82 Linux swap / Solaris 
rescue:~# fdisk /dev/vda 
Command (m for help): u 
Changing display/entry units to cylinders (DEPRECATED!) 
Command (m for help): c 
DOS Compatibility flag is set (DEPRECATED!) 
Command (m for help): d 
Partition number (1-5): 2 
Command (m for help): n 
Partition type: 
p primary (1 primary, 0 extended, 3 free) 
e extended 
Select (default p): p 
Partition number (1-4, default 2): 2 
First cylinder (29503-63741, default 29503): 
Using default value 29503 
Last cylinder, +cylinders or +size{K,M,G} (29503-63741, default 63741): 
Using default value 63741 
Command (m for help): w 
The partition table has been altered! 
Calling ioctl() to re-read partition table. 
Syncing disks. 
rescue:~# fsck -C0 -y -f /dev/vda2 
fsck from util-linux 2.20.1 
e2fsck 1.42.5 (29-Jul-2012) 
ext2fs_open2: Bad magic number in super-block 
fsck.ext2: Superblock invalid, trying backup blocks... 
fsck.ext2: Bad magic number in super-block while trying to open /dev/vda2 
The superblock could not be read or does not describe a correct ext2 
filesystem. If the device is valid and it really contains an ext2 
filesystem (and not swap or ufs or something else), then the superblock 
is corrupt, and you might try running e2fsck with an alternate superblock: 
e2fsck -b 8193 <device>