Deleting orphan file record segment and I lost all my data?

[Minhworldclass]

My rigs:
Intel core i7 2600 non K
GIGABYTE™ GA PH67-UD3-B3
Asus GTX 560 Ti CU II TOP
Gskill DDR3 4gb 1333mhz
Seagate 500GB/ 7200Rpm/ Cache 16MB/ SATA 2GB/s
FSP Epsilon 600W

After installing the game Operation Flashpoint Redriver, I restart my PC. The Chkdsk show me that the D drive needs to be checked. But instead of running 3 steps as usual, it display "Deleting orphan file record segment...."

It runs about 10 minutes and boots in Win 7 normally. But some game shortcuts which is installed on D Driver shows that their root folder is not available:

I checked the D drive free space and realized It had deleted my 80 GB

Can anyone tell me What just happened? And What can I do to restore my data . Is my HDD going to break?

 

[Nothinman]

There was a problem with the filesystem and chkdsk did all it could to get the filesystem back into a consistent state, in this case deleted file records that it didn't know where they belong.

How the filesystem got into that state could be any number of things from an unstable overclock to a bad cable.

 

[razel]

In addition to what Nothinman mentioned, I'd re-run chkdsk until it reports no problems. To be on the safe side, I then would run Seagate's Seatools and do a quick SMART check.

 

[Nothinman]

In addition to what Nothinman mentioned, I'd re-run chkdsk until it reports no problems. To be on the safe side, I then would run Seagate's Seatools and do a quick SMART check.

That's the last thing you want to do. If it's a hardware problem then chkdsk may continue to find problems that aren't really there because the cable is corrupting data in transit or memory errors are causing the data to not look right.

 

[razel]

OK, Got anything contributory and productive for the OP?

That's the last thing you want to do. If it's a hardware problem then chkdsk may continue to find problems that aren't really there because the cable is corrupting data in transit or memory errors are causing the data to not look right.

 

[Cerb]

Back up any really important data NOW, get Seatools, and test your HDD. You want to verify that the problem is a software one. If the drive has issues, back up the rest of you can, and RMA it.

 

[Voo]

OK, Got anything contributory and productive for the OP?

Well if you read what he said, the first thing one should do is to replace the SATA cable, get rid of every OC if existing and run memchk.

If the problem is one of the above running chkdsk again or backing up data is waste of time at best (your corrupted backup won't do much good) or harmful at worst (deleting more perfectly fine data)

 

[Spikesoldier]

1. back up data
2. run the LONG hard drive test.

 

[tctu]

Sometimes My PC check disk on startup.



Just before reboot, i still use the files as well. After a reboot, my pc check disk, then they delete them. I think "Deleting index entry" only delete index , not data. is It true?

How can i recover theme?



That mentioned on the log: PL0EF5~1, full.mp4.... I searched the solution, then find folder "found.00X" But i can't find the lost files.
Any idea to help me recover these files would be appreciated. I also need to help to prevent "Deleting index entry" loss my files.




Here is the log

Checking file system on D: The type of the file system is NTFS.   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.                          Deleting orphan file record segment 29143. Deleting orphan file record segment 29148. Deleting orphan file record segment 29152. Deleting orphan file record segment 29155. ............ Deleting orphan file record segment 29179. Index entry PL0EF5~1 of index $I30 in file 0x99 points to unused file 0x702a. Deleting index entry PL0EF5~1 in index $I30 of file 153. Index entry PL2BA0~1of index $I30 in file 0x99 points to unused file 0x702d. Deleting index entry PL2BA0~1 in index $I30 of file 153. ............. Index entry full.mp4 of index $I30 in file 0x3ac5c points to unused file 0x7016. Deleting index entry full.mp4 in index $I30 of file 240732. ..................  293603908 KB total disk space.  109135160 KB in 659568 files.     299360 KB in 107552 indexes.          0 KB in bad sectors.     905852 KB in use by the system.      65536 KB occupied by the log file.  183263536 KB available on disk.        4096 bytes in each allocation unit.   73400977 total allocation units on disk.   45815884 allocation units available on disk.

many thanks

 

[Cerb]

Those found fragments are part of the lost files. Chances are, you won't recover files of any considerable size, only single-fragment files, if you can figure them out.

If this happens often, you have a major problem of some kind, and need to deal with it, be it unstable power, a bad HDD, bad PSU, bad cable, early 6-series south bridge, or whatever else.