1Tb HDD not accessible anymore =( Unreadable file sectors

[jasjeet]

So the PC froze up on me today, was getting very random CPU spikes. So i rebooted it, upon reboot i saw as the Bios loaded up:

"SMART command failed" on one of my Hard drives. It was my WD 1Tb (not a boot drive, just data).

When i finally got to windows, i couldnt access the drive, it told me to format.
So i rebooted once more, CHKDSK ran on the HDD. It found 4 unreadable file sectors. Still cant access the drive.
Then i boot into my OSX installation (dual boot), and i can access the drive perfectly fine, all files in tact.

So now im running CHKDSK e:/r and its taking a long while. Is there anything else i should do apart from backup?

How can i get it to just delete the 4 bad sectors and mark them as bad sectors?

 

[ignatzatsonic]

How can i get it to just delete the 4 bad sectors and mark them as bad sectors?

Checkdisk should find the bad sectors and isolate them, making them unusable.

I'd also download the hard drive manufacturer's drive utility and run it. If it fails, you may have a warranty claim.

 

[jasjeet]

I tried WD's data life guard, but it doesnt seem to pick up any of my 3 Western Digital Drives as Physical drives, just logical partitions which i cant run diagnostics on.
I used HDTunePro to check the SMART data just before i ran the manual CHKDSK and didnt see anything out of the ordinary.

Windows is a bit unstable while this drive is plugged in, programs keep hanging so trying to get HDTunePro to run once more.

 

[jasjeet]

Ok after a lot of tries, i got it to appear in the list:

Here is Quick Scan result

Smart scan:

Extended scan is running says its going to take 3hours, ill post back with results.

CHKDSK /r just made the system hang after a while and i had to reboot. HDD LED on my case was lit solid and CHKDSK did not print anything after Checking Index Files.

CHKDSK ran on reboot once more as well.

How can i get it to run the CHKDSK /r on this drive at startup? Any point? What's the difference between this and the one running at startup currently?