- Feb 28, 2016
- 2
- 0
- 1,510
So everything has been fine until today when data seem to disapear while I was playing borderlands, I had problems loading into an area and validated my files and sure enough files were missing... 1.2 GB worth. So it went on it's merry way installing the lost files untill I noticed strange clicking sounds while the HD was under load (and not the clicking sound of death mind you, the are small very fast paced clicks not the slow repetitive loud clicks of the click of death) and then steam started getting writing errors when trying to allocate files. My computer is a laptop so this could be a factor though I treat my laptop very well and am unaware of any trauma being sustained to it. The drive in question is my D: drive (my C: drive is an ssd), and the model in question is a HGST HTS721010A9E630 and the system event log for the scan is as follows (I am not fluent in the Chkdsk log which is why I am asking for help):
Chkdsk was executed in scan mode on a volume snapshot.
Checking file system on D:
Volume label is DATA.
Stage 1: Examining basic file system structure ...
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x4.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x4.
394240 file records processed. File verification completed.
2357 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x4.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x4.
504238 index entries processed. Index verification completed.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
54999 data files processed. Read failure with status 0xc0000010 at offset 0xb62e2000 for 0x10000 bytes.
A disk read error occurredc0000010
----------------------------------------------------------------------
Stage 1: Examining basic file system structure ...
Stage 2: Examining file name linkage ...
Stage 3: Examining security descriptors ...
An unspecified error occurred (6c6f6766696c652e 29c).
Thank you for your time.
Chkdsk was executed in scan mode on a volume snapshot.
Checking file system on D:
Volume label is DATA.
Stage 1: Examining basic file system structure ...
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x4.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x4.
394240 file records processed. File verification completed.
2357 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x4.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x4.
504238 index entries processed. Index verification completed.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
54999 data files processed. Read failure with status 0xc0000010 at offset 0xb62e2000 for 0x10000 bytes.
A disk read error occurredc0000010
----------------------------------------------------------------------
Stage 1: Examining basic file system structure ...
Stage 2: Examining file name linkage ...
Stage 3: Examining security descriptors ...
An unspecified error occurred (6c6f6766696c652e 29c).
Thank you for your time.
I'd strongly recommend you to backup your data from the HDD somewhere else ASAP and then proceed with the troubleshooting. Chkdsk might not be a good idea when dealing with physical damage. I'd advise you to use the HDD manufacturer's brand-specific diagnostic tool to check up on the health and SMART status of the drive. 
Facebook
Twitter
Instagram