Corrupted files, drive won't chkdsk

[jhmac777]

In my backup I have this notation:

"11/2/2014 7:22:57 PM - Begin: 3 c- g ================================================
11/2/2014 7:24:47 PM - The file or directory is corrupted and unreadable - g:\Users\JimandKaren\AppData\Local\Microsoft\Windows Live Mail\Storage Folders\Recovered items\08-25-2014 29\Bellsouth ( c13\Inbox\
11/2/2014 7:24:47 PM - End: 3 c- g ... Copied: 0, Errors: 1"

Cannot delete bad folder!
Disk will not completely chkdsk, just partially. HdTune 255 error chk no damages shown. Fairly new Black WD 500 GB drive. 19 error counts listed in HD Sentinel log on Nov 2 for that drive. This drive is one of three drives of desktop, no other corrupted files noted on other drives. What do I do?

 

[ronintexas]

It appears the hard drive may be failing. Can you run WD diagnostics on the drive? http://support.wdc.com/product/download.asp?groupid=613&lang=en

 

[jhmac777]

Any other opinions:
TODAY is Nov 3: 19 error counts listed in HD Sentinel log starting on Nov 2 for that drive., but no errors, all green, in HDTune 2.55 free version(old version??) not the pro version. This is a backup drive only, and has a 5 year warranty expires next year.

I thought about backing up drive and reformatting it. It also has 3 drives D, G, F on it and it would take a long time to backup. I actually have several backup drives with similar material on them. I have not call WD support about this yet.

 

[Hawkeye22]

WD support won't help you until you've checked the drive with their data lifeguard utility which ronintexas has already provided a link to.

 

[jhmac777]

Error count HDSentinel (so far no problems with WD test, Quick and now running Extended test.):

11/3/2014 3:44:11 PM,#199 Ultra ATA CRC Error Count 48613 -> 48873
11/3/2014 3:40:32 PM,#199 Ultra ATA CRC Error Count 48115 ->

48613
11/3/2014 3:34:47 PM,#199 Ultra ATA CRC Error Count 47816 -> 48115
11/3/2014 3:29:44 PM,#199 Ultra ATA CRC Error Count 47609 -> 47816
11/3/2014 3:24:03 PM,#199 Ultra ATA CRC Error Count 47271 -> 47609
11/3/2014 3:18:49 PM,#199 Ultra ATA CRC Error Count 46734 -> 47271
11/3/2014 3:13:11 PM,#199 Ultra ATA CRC Error Count 46463 -> 46734
11/3/2014 3:07:29 PM,#199 Ultra ATA CRC Error Count 46169 -> 46463
11/3/2014 3:01:46 PM,#199 Ultra ATA CRC Error Count 45919 -> 46169
11/3/2014 2:56:43 PM,#199 Ultra ATA CRC Error Count 45564 -> 45919
11/3/2014 2:51:06 PM,#199 Ultra ATA CRC Error Count 45545 -> 45564
11/3/2014 2:50:03 PM,#199 Ultra ATA CRC Error Count 44799 -> 45545
11/2/2014 8:34:59 PM,#199 Ultra ATA CRC Error Count 44634 -> 44799
11/2/2014 8:29:54 PM,#199 Ultra ATA CRC Error Count 44333 -> 44634
11/2/2014 8:24:51 PM,#199 Ultra ATA CRC Error Count 44075 -> 44333
11/2/2014 8:19:20 PM,#199 Ultra ATA CRC Error Count 43933 -> 44075
11/2/2014 7:23:22 PM,#199 Ultra ATA CRC Error Count 43928 -> 43933
11/2/2014 7:13:13 PM,#199 Ultra ATA CRC Error Count 43914 -> 43928
11/2/2014 7:08:09 PM,#199 Ultra ATA CRC Error Count 43732 -> 43914
11/2/2014 7:03:05 PM,#199 Ultra ATA CRC Error Count 43379 -> 43732
11/2/2014 6:58:00 PM,#199 Ultra ATA CRC Error Count 38288 -> 43379
11/2/2014 4:42:29 PM,#199 Ultra ATA CRC Error Count 38043 -> 38288
11/2/2014 4:37:25 PM,#199 Ultra ATA CRC Error Count 37492 -> 38043
11/2/2014 4:31:44 PM,#199 Ultra ATA CRC Error Count 35142 -> 37492
11/2/2014 3:51:55 PM,#199 Ultra ATA CRC Error Count 34821 -> 35142
11/2/2014 3:48:33 PM,#199 Ultra ATA CRC Error Count 34476 -> 34821
11/2/2014 2:31:48 PM,#199 Ultra ATA CRC Error Count 34439 -> 34476
11/2/2014 2:26:44 PM,#199 Ultra ATA CRC Error Count 34437 -> 34439
11/2/2014 2:21:40 PM,#199 Ultra ATA CRC Error Count 34267 -> 34437
11/2/2014 2:11:31 PM,#199 Ultra ATA CRC Error Count 34099 -> 34267
11/2/2014 2:01:23 PM,#199 Ultra ATA CRC Error Count 34098 -> 34099
11/2/2014 1:57:59 PM,#199 Ultra ATA CRC Error Count 33997 -> 34098
11/2/2014 1:55:54 PM,#199 Ultra ATA CRC Error Count 33983 -> 33997
11/2/2014 1:20:24 PM,#199 Ultra ATA CRC Error Count 33979 -> 33983
11/2/2014 1:05:08 PM,#199 Ultra ATA CRC Error Count 0 -> 33979
WD Smart status is pass

 

[Hawkeye22]

If the drive is under warranty, RMA it. WD Black drives have a 5 year warranty.

 

[jhmac777]

I am running extended test and it says it will take over 90 hours= 4+ days to complete. This is ridiculous. My chkdsk stops in progress and will not complete. Have to restart computer to access drive.

 

[ronintexas]

Given you post above with the CRC errors - you drive is dying....no diagnostic tool or software is going to fix it. Contact WD and RMA it....

 

[jhmac777]

??????????? PLEASE COMMENT!!!!!
I believe I FIXED THIS: I put the drive in a USB 3.0 Plugable docking station using a Win 8.1 laptop. Check disked the drive and the drive errors were corrected and now the chkdsk says no errors. I am wondering whether the encloseure used in my old desktop caused all the problems. It is a star tech enclosure. I am backing up onto this disk using a docking station and Windows 8.1 without any error problems.

Before when I had all the problems with corruption I was trying to backup over the network on my desktop(it is several years old).
But my other drives on the desktop using network backed up without problems.

Last chkdsk: Checking file system on H: Stage 1: Examining basic file system structure ... The USA check value, 0xffff, at block 0x1 is incorrect. The expected value is 0x6. The USA check value, 0xffff, at block 0x1 is incorrect. The expected value is 0x4. The USA check value, 0xffff, at block 0x1 is incorrect. The expected value is 0x4. The USA check value, 0xffff, at block 0x1 is incorrect. The expected value is 0x4. 1965568 file records processed. File verification completed. 1579 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... The USA check value, 0xffff, at block 0x1 is incorrect. The expected value is 0x6. The USA check value, 0xffff, at block 0x1 is incorrect. The expected value is 0x4. The USA check value, 0xffff, at block 0x1 is incorrect. The expected value is 0x4. The USA check value, 0xffff, at block 0x1 is incorrect. The expected value is 0x4. 2086468 index entries processed. Index verification completed. Stage 3: Examining security descriptors ... Security descriptor verification completed. 60451 data files processed. CHKDSK is verifying Usn Journal... 1040 USN bytes processed. Usn Journal verification completed. Windows has scanned the file system and found no problems. No further action is required. 321765853 KB total disk space. 302767672 KB in 1152621 files. 621084 KB in 60452 indexes. 2042241 KB in use by the system. 65536 KB occupied by the log file. 16334856 KB available on disk. 4096 bytes in each allocation unit. 80441463 total allocation units on disk. 4083714 allocation units available on disk. ---------------------------------------------------------------------- Stage 1: Examining basic file system structure ... Stage 2: Examining file name linkage ... Stage 3: Examining security descriptors ... Windows has scanned the file system and found no problems. No further action is required.
00FE1D009D821200270D21000000000063220100000000000000000000000000


--------------------------------------------------------------------------------

Binary data:


In Words

0000: 001DFE00 0012829D 00210D27 00000000
0010: 00012263 00000000 00000000 00000000


In Bytes

0000: 00 FE 1D 00 9D 82 12 00 .þ..‚..
0008: 27 0D 21 00 00 00 00 00 '.!.....
0010: 63 22 01 00 00 00 00 00 c"......
0018: 00 00 00 00 00 00 00 00 ........



Can you explain this!!

 

[Hawkeye22]

It's possible the enclosure is bad. What does HD senitnel say now? You may also want to check it with crystal disk info. Also, try WD Lifeguard again.

 

[jhmac777]

HD Sentinal showed only 1 error today. WD Lifeguard extension test is running normal right now yesterday it stopped very prematurely due to bad sectors.

 

[jhmac777]

I found the problem!! It is the star Tech enclosure. I put another drive 320 gb into that enclosure and I see one error in hd sentinal already for that 320 gb drive. I guess it could also be in the wires that connect that enclosure. The other drives both 500gb are connected to another brand of enclosure and to a docking station. One of those drives that was previously corrupted is connected via a usb docking station.

Any comment!