Help! Should I RMA this harddrive ?

[kirby7777]

I have a 2Gb WD RE4 GP WD2002FYPS 01U1B0 for about 3 years or so.

It has C and D partitions. This is like a backup computer so it is seldom use.

Need to press reset button a week ago and during reboot process chkdsk came in. Here is the log file.

************************************************** **************
Checking file system on D:
The type of the file system is NTFS.
Volume label is RE4GP2.

One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
45312 file records processed.

File verification completed.
77 large file records processed.

0 bad file records processed.

0 EA records processed.

0 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
48228 index entries processed.

Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
1 unindexed files scanned.

Recovering orphaned file 8F6262~1 (10180) into directory file 5.
Recovering orphaned file 8f62629b-0714-46d3-b816-31c209e99f1e (10180) into directory file 5.
0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...
45312 file SDs/SIDs processed.

Cleaning up 37 unused index entries from index $SII of file 0x9.
Cleaning up 37 unused index entries from index $SDH of file 0x9.
Cleaning up 37 unused security descriptors.
Security descriptor verification completed.
1459 data files processed.

CHKDSK is verifying Usn Journal...
Read failure with status 0xc000009c at offset 0xdbc1afe000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xdbc1b0c000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd65e000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd66a000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd66b000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd66c000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd66d000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd66d000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd66e000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd66f000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd670000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd670000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd671000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd675000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd676000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd676000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd677000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd678000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd679000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd679000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd69a000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd6a8000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd6a9000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd6b1000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd6c2000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd6ce000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd6ef000 for 0xf000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd6f0000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd6f1000 for 0xd000 bytes.
Read failure with status 0xc000009c at offset 0xdbbd6f2000 for 0x1000 bytes.
The remaining USN block at offset 0x3194000 in file 0x24 is
less than a page.
The remaining of an USN page at offset 0x3194000 in file 0x24
should be filled with zeros.
Repairing Usn Journal file record segment.
35210400 USN bytes processed.

Usn Journal verification completed.
Adding 15 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

1848652799 KB total disk space.
1311799580 KB in 42172 files.
26976 KB in 1460 indexes.
60 KB in bad sectors.
202127 KB in use by the system.
65536 KB occupied by the log file.
536624056 KB available on disk.

4096 bytes in each allocation unit.
462163199 total allocation units on disk.
134156014 allocation units available on disk.

************************************************** *************

After the reboot somehow I lost D partition.

Managed to get the partition back after just scanning the HDD with Acronis Disk Director.

I think I might have lost some files as one of the folders is empty.
Backup the rest of the data. Could not do partition cloning of D partition as Casper 7 failed a few times because of some read error. So has to do copy and paste. C partition could be cloned ok.

Then used GetDataBack but could not find any extra files.

Then run the disk with HDD Regenerator 2011. Found over 300 bad sectors and managed to regenerate all. Run the second time and found about 72 and regenerated all again. Have just completed the third run and found & recovered 25 bad sectors.

It is always about half way through the run where the bad sectors were found. Must be significant corruption around there.

So my questions are:

1) Should I RMA the HDD if I found more bad sectors during the fourth run?
2) Should I RMA the HDD if no bad sectors are found during the fourth and subsequent run?

Thanks.

[D_W_Y]

have you actually had any problem with the drive? have a look here
https://westerndigital.secure.force....yCheck?lang=en

in the ocd nature of ocau, you must be annoyed if its failing any checks. i think wd provides software you can download to check the drive and if that shows issues it can be rma'd. but honestly if nothing bad is happening with it why bother.

[HUMMER]

run the hard drive scanning tools of the manufacturer. go to the website. there should be a link there. scan the drive. if it comes up with an error. then you can RMA the drive then.

[tiro_uspsss]

yes. rma. now.