bad super block - PM2009 screwed it up - help

Further to that below from earlier:linux command line fsck reckons it is now an EXT2 file system and other disk handlers think it is EXT4 which it should be. Partion Manager definitely screwed up the super block as you cannot convert, I understand from linux blogs, EXT4 to EXT2.
Also my file backup using PM to my DVD is unreadable so my data is stuck on this disk that I cannot access.
root@patd-laptop:~# sudo fdisk -l /dev/sda

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3c5765e6

Device Boot Start End Blocks Id System
/dev/sda1 * 1 3824 30716248+ 83 Linux
/dev/sda2 3825 30401 213479752+ 5 Extended
/dev/sda5 3825 27962 193888453+ 83 Linux
/dev/sda6 29117 30401 10321731 82 Linux swap / Solaris
root@patd-laptop:~#


________________________________________________________________________________________
OK - Partition Manager 2009. My disk has 3 linux partitions. System, home and swap. They are ext4fs.

I resized the system partition OK. I then resized the home in a separate operation. It is now inaccessible with a bad superblock. Tried deleting and undeleting but PM thinks it is an ext2fs.

My linux disk utlilitities all see it OK and report space used etc but it will not mount. Gparted reports:
GParted 0.5.0

Libparted 1.8.8.git-dirty
Grow /dev/sda5 from 184.91 GiB to 193.75 GiB 00:00:00 ( ERROR )

calibrate /dev/sda5 00:00:00 ( SUCCESS )

path: /dev/sda5
start: 61432623
end: 449209529
size: 387776907 (184.91 GiB)
check file system on /dev/sda5 for errors and (if possible) fix them 00:00:00 ( ERROR )

e2fsck -f -y -v /dev/sda5

e2fsck: Group descriptors look bad... trying backup blocks...
e2fsck: going back to original superblock
Filesystem mounted or opened exclusively by another program?
e2fsck 1.41.9 (22-Aug-2009)
e2fsck: The ext2 superblock is corrupt when using the backup blocks
e2fsck: Device or resource busy while trying to open /dev/sda5

========================================

 

Paragon undelete won't be able to recognize a Ext4 partition. Try a program like findandmount.com to see if it works.


Good luck.