HDDs Corrupt?

[Xplorer4x4]

Alright so I think using write support in Win 8 using Ext2FSD for my EXT partitions has come back to bite me..I have 2 separate issues here with 2 separate HDDs.

HDD 1. One HDD is reporting 0 space left in dolphin. However, I know I did not use up all the space, and KDE Partition Manager and Gparted show some free space as well.

HDD 2. The other HDD refuses to mount in Kubuntu. It gives this error message when I try:

An error occurred while accessing 'Desktop', the system responded: The kernel driver for this filesystem type is not available.: Error mounting: mount: wrong fs type, bad option, bad superblock on /dev/sdd1,  missing codepage or helper program, or other error. In some cases useful info is found in syslog - try dmesg | tail  or so

dmesg | tail output is:

xplorer4x4@xplorer4x4-MS-7673:~$ dmesg | tail
[ 20.069634] usb 2-1.5: Manufacturer: La-VIEW Technology
[ 20.071514] input: La-VIEW Technology Naos 5000 Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input13
[ 20.071770] hid-generic 0003:04B4:1224.0003: input,hiddev0,hidraw2: USB HID v1.00 Keyboard [La-VIEW Technology Naos 5000 Mouse] on usb-0000:00:1d.0-1.5/input0
[ 37.277290] EXT4-fs (sdd1): ext4_check_descriptors: Checksum for group 3201 failed (45969!=38902)
[ 37.277293] EXT4-fs (sdd1): group descriptors corrupted!
[ 306.412413] EXT4-fs (sdc1): error count: 3
[ 306.412418] EXT4-fs (sdc1): initial error at 1358560365: ext4_journal_start_sb:371
[ 306.412421] EXT4-fs (sdc1): last error at 1358587789: ext4_put_super:887
[ 891.420973] EXT4-fs (sdd1): ext4_check_descriptors: Checksum for group 3201 failed (45969!=38902)
[ 891.420975] EXT4-fs (sdd1): group descriptors corrupted!

sdd1 is the partition that wont mount.
sdc1 is the partition that mounts but reports incorrect data usage.

I ran "sudo fsck.ext4 -v /dev/sd##" on both drives.

HDD 1.It quickly claimed to have fixed sdc1 but after a reboot, the problem is still there.

HDD 2. It ran an operation, sorry I do not have th exact out put, forgot to copy and paste before a reboot, but I ran it from about 7PM last night, to 4PM today, and it was still not done, so I rebooted. Problem still exists.

Am I screwed in terms of data recovery?

[Xplorer4x4]

Small update:

xplorer4x4@xplorer4x4-MS-7673:~$ sudo fsck.ext4 -cDftty -C 0 /dev/sdb1
[sudo] password for xplorer4x4: 
e2fsck 1.42.5 (29-Jul-2012)
Checking for bad blocks (read-only test): done                                                 rors)
WD3: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
                                                                               
Running additional passes to resolve blocks claimed by more than one inode...
Pass 1B: Rescanning for multiply-claimed blocks
Multiply-claimed block(s) in inode 73772: 400048627 400048628
Pass 1b: Memory used: 1564k/20016k (1374k/191k), time:  4.65/ 4.61/ 0.03
Pass 1b: I/O read: 163MB, write: 0MB, rate: 35.04MB/s
Pass 1C: Scanning directories for inodes with multiply-claimed blocks
Pass 1c: Memory used: 1564k/20016k (1374k/191k), time:  9.00/ 0.06/ 0.15
Pass 1c: I/O read: 133MB, write: 0MB, rate: 14.78MB/s
Pass 1D: Reconciling multiply-claimed blocks
(There are 1 inodes containing multiply-claimed blocks.)

File /UFC.on.FX.7.720p.HDTV.x264-KYR/ufc.on.fx.7.720p.hdtv.x264-kyr.r06 (inode #73772, mod time Sun Jan 20 10:21:02 2013) 
  has 2 multiply-claimed block(s), shared with 1 file(s):
        <The bad blocks inode> (inode #1, mod time Wed Jan 23 22:25:29 2013)
Clone multiply-claimed blocks? yes

Error reading block 400048627 (Attempt to read block from filesystem resulted in short read).  Ignore error? yes

Force rewrite? yes

Error reading block 400048628 (Attempt to read block from filesystem resulted in short read).  Ignore error? yes

Force rewrite? yes

Pass 1d: Memory used: 1564k/20016k (1377k/188k), time: 39.08/17.99/ 0.03
Pass 1d: I/O read: 1MB, write: 0MB, rate: 0.03MB/s
Pass 1: Memory used: 1564k/20016k (1330k/235k), time: 126.06/49.57/ 0.51
Pass 1: I/O read: 459MB, write: 1MB, rate: 3.64MB/s
Pass 2: Checking directory structure
Pass 2: Memory used: 2416k/36196k (1260k/1157k), time:  0.91/ 0.27/ 0.03                                                                                                                   
Pass 2: I/O read: 215MB, write: 1MB, rate: 237.20MB/s                                                                                                                                      
Pass 3: Checking directory connectivity                                                                                                                                                    
Peak memory: Memory used: 2416k/36196k (1260k/1157k), time: 19692.12/55.94/ 0.72                                                                                                           
Pass 3A: Optimizing directories                                                                                                                                                            
Pass 3A: Memory used: 3668k/36196k (1402k/2267k), time: 46.86/46.45/ 0.27                                                                                                                  
Pass 3A: I/O read: 145MB, write: 145MB, rate: 6.17MB/s                                                                                                                                     
Pass 3: Memory used: 3668k/35816k (1272k/2397k), time: 46.86/46.45/ 0.27                                                                                                                   
Pass 3: I/O read: 145MB, write: 145MB, rate: 6.17MB/s                                                                                                                                      
Pass 4: Checking reference counts                                                                                                                                                          
Pass 4: Memory used: 3668k/432k (923k/2746k), time:  5.60/ 5.55/ 0.04                                                                                                                      
Pass 4: I/O read: 0MB, write: 0MB, rate: 0.00MB/s                                                                                                                                          
Pass 5: Checking group summary information                                                                                                                                                 
Free blocks count wrong for group #10979 (435, counted=433).                                                                                                                               
Fix? yes                                                                                                                                                                                   
                                                                                                                                                                                           
Free blocks count wrong for group #12208 (65534, counted=0).                                                                                                                               
Fix? yes

Pass 5: Memory used: 3668k/432k (507k/3162k), time:  8.62/ 8.58/ 0.02          
Pass 5: I/O read: 0MB, write: 0MB, rate: 0.00MB/s

WD3: ***** FILE SYSTEM WAS MODIFIED *****
WD3: 380711/111616000 files (1.9% non-contiguous), 430786244/446432285 blocks
Memory used: 3668k/432k (507k/3162k), time: 19773.82/117.50/ 1.10
I/O read: 878MB, write: 197MB, rate: 0.05MB/s

Did not fix the 0 space left error. As for the other drive, I ran sudo fsck.ext4 -cDftty -C 0 /dev/sdb1 on it as well and it seems hung up on the same file for a few hours now and it is just a small mp3.