Need HELP!! Current Pending Sector!!

Aminados

Member
Sep 24, 2013
30
0
0
30% of the time I start my PC it says "One of your disk needs to be checked for consistency" I did let it finish the first time and no errors wore found. Since then the windows on my problematic HDD (WD Caviar Black 1TB) (2months old) has been screwed. The trouble started when my PC froze and I had to shut it down incorrectly.

CMD "diskdrive get status" and "WD Lifeguard" report all is ok. While "HD Tune Pro" and "CrystalDiskInfo" report Current Pending Sector!!

How to fix?

5247b7ac_HDDWDBLACK.jpeg
 
Last edited:

Bubbaleone

Golden Member
Nov 20, 2011
1,803
4
76
If two out three SMART reports indicate a bad sector you should assume that's the case. To correct the problems you're experiencing with Windows you need to run chkdsk. Open an elevated command prompt and run this command:

chkdsk C: /x /v /r /b

This command will resolve both file system and disk errors. It will take a while to complete so just be patient and don't interrupt the process for any reason. Once it's completed you should backup all your data to a good drive to ensure that (should the WD continue to degrade, which it most likely will) your data is safe.
 

Ketchup

Elite Member
Sep 1, 2002
14,559
248
106
You could wipe the hard drive and see if the errors come back, but they probably will. I would RMA the hard drive while you still can.
 

Ketchup

Elite Member
Sep 1, 2002
14,559
248
106
If two out three SMART reports indicate a bad sector you should assume that's the case. To correct the problems you're experiencing with Windows you need to run chkdsk. Open an elevated command prompt and run this command:

chkdsk C: /x /v /r /b...

You have more patience than I good sir.
 

AnitaPeterson

Diamond Member
Apr 24, 2001
5,992
494
126
If two out three SMART reports indicate a bad sector you should assume that's the case. To correct the problems you're experiencing with Windows you need to run chkdsk. Open an elevated command prompt and run this command:

chkdsk C: /x /v /r /b

This command will resolve both file system and disk errors. It will take a while to complete so just be patient and don't interrupt the process for any reason. Once it's completed you should backup all your data to a good drive to ensure that (should the WD continue to degrade, which it most likely will) your data is safe.

Would you still need to use the same command on a disk that's not the primary (boot) device? Or would chkdsk /f /r [drive-letter-followed-by-:] be enough?
 

Aminados

Member
Sep 24, 2013
30
0
0
So you can't boot from the hdd any more?

I can boot from the HDD but explorer.exe stops working every 3 seconds, maybe there was a windows file on the bad sector.

I just want to be clear, the drive is 2 months old, It was running perfectly fine until my PC froze. The HDD was probably writing something hence the bad sector. (I could hear a looping sound from the HDD after the PC froze)

I'm still using the HDD as storage/installation drive with no problems.
 

Bubbaleone

Golden Member
Nov 20, 2011
1,803
4
76
Would you still need to use the same command on a disk that's not the primary (boot) device? Or would chkdsk /f /r [drive-letter-followed-by-:] be enough?

Yes, however, using the /f switch is redundant as the /r switch implies the functionality of /f. Regardless of the drive (or volume) being primary or storage the command follows this syntax:

chkdsk X: /x /v /r /b (where X: is your actual drive/volume letter)

The /x switch locks the drive for full access by chkdsk, the /v switch gives you verbose output, the /r switch locates bad sectors and recovers readable information, and the /b switch clears the list of bad clusters on the volume and rescans all allocated and free clusters for errors. This chkdsk command is much more intensive and thorough than the standard chkdsk /f command.

.
 
Last edited:

Aminados

Member
Sep 24, 2013
30
0
0
If two out three SMART reports indicate a bad sector you should assume that's the case. To correct the problems you're experiencing with Windows you need to run chkdsk. Open an elevated command prompt and run this command:

chkdsk C: /x /v /r /b

This command will resolve both file system and disk errors. It will take a while to complete so just be patient and don't interrupt the process for any reason. Once it's completed you should backup all your data to a good drive to ensure that (should the WD continue to degrade, which it most likely will) your data is safe.


OK, I'm doing that right now. How long should it take? (1TB)
 

Bubbaleone

Golden Member
Nov 20, 2011
1,803
4
76
It will depend on the both the amount of data contained on the drive and the number of damaged clusters present, but for 1TB you're probably looking at two hours minimum.

.
 

Aminados

Member
Sep 24, 2013
30
0
0
Just finished the chkdsk, and... I still have the pending sector by the look of things.

dd17de9c_pendingsectorr.jpeg
 

Steltek

Diamond Member
Mar 29, 2001
3,310
1,050
136
Sounds like that bad sector is probably in a bad location. Did you run an extended test using the Data Lifeguard software?

Out of curiosity, where did you purchase the drive?
 
Last edited:

Aminados

Member
Sep 24, 2013
30
0
0
Yes, actually I did both quick test and extended test, it failed both even though Lifeguard's S.M.A.R.T is reporting no errors...

Test Option: QUICK TEST
Model Number:
WDC WD1002FAEX-00Z3A0
Unit Serial Number:
WD-WCATRC368621
Firmware Number:
05.01D05
Capacity:
1000.20 GB
SMART Status:
PASS
Test Result:
FAIL
Test Error Code:
06-Quick Test on drive 1 did not complete! Status code = 07 (Failed read test element), Failure Checkpoint = 97 (Unknown Test) SMART self-test did not complete on drive 1! Test Time: 00:27:15, September 25, 2013

I bought the drive brand new on Amazon, had no bad sectors until my PC froze and I had to shut it down the hard way...
 
Last edited:

Bubbaleone

Golden Member
Nov 20, 2011
1,803
4
76
Just finished the chkdsk, and... I still have the pending sector by the look of things.

As already noted by several peers; if RMA is still an option you should do that ASAP (deal directly with WD not Amazon). You may have misunderstood the purpose of running the chkdsk command I posted. It was to correct any file system errors and disk errors (bitmap image and free space reporting errors) that were present as the result of the damaged clusters, thus stabilizing your data so that you can safely transfer it to a good drive. Chkdsk can't correct physical damage to the platter itself, which is what's happened to your WD and will only continue to get worse. At some (unknown) point your data will become unrecoverable if you continue to use that drive.

.
 
Last edited: