Recovered orphaned file directories/location

[PotatChip]

I've searched far and wide for the answer.
Google seems to be convinced I need to know what an "orphaned file" is as opposed to answering my question.

Long story short;
Cloned a HDD into a new HDD.
Performed chkdsk 2 weeks ago
currently "recovering orphaned files"
files now are currently "corrupt" or so i think.

For example, a picture is shown to be "corrupted" in the windows explorer.
chkdsk reports;
Recovering orphaned file example.jpg into directory file (321674)

I check on that exact file to find nothing has changed.

My question is: is the file recovered in some sort of virtual memory directory?
where is the recovered file? is that file going to be recovered? if so, when is it going to get that recovery?

sorry for crap english, can provide further information if needed.

 

[iko22]

Some times you have to run CHKDSK three times to get the full recovery of the File System.

Which CHKDSK are you using? CHKDSK C: /f or CHKDSK C: /r. You should run CHKDSK C: /f first, then followed by CHKDSK C: /r. Or run CHKDSK C: /f /r in one go (might take longer).

 

[PotatChip]

Am currently running CHKDSK Z: /f /r in one go, and its been two weeks, and its been on recovering orphaned files for about 1 week 3 days ish at 42819 of 713943 of unindexed files scanned

also, I found what you said quite intriguing;

Some times you have to run CHKDSK three times to get the full recovery of the File System.

Is there a reason for this? how does it work?
I would have thought computers and the like either fix it the first try, or if it doesnt, repeating the process does is useless.

Have i been performing chkdsk wrong all my life?

 

[iko22]

Gosh that is a long time by any standards!

Could mean that the HDD has gone bad. Always a good idea to use the Manufacturer's diagnostic Software for testing Hard drives, when you next get the chance.

CHKDSK uses error detecting and correcting codes to check and repair sectors on a hard disk. It is my understanding, that if there are too many sectors to correct, then it just gives up trying to correct all of them in one go. Then it is worth running the program up to three times to get it to complete all stages.

However, if the HDD is defective, then you could be wasting your time, as CHKDSK can never actually repair a HDD, only the integrity of the data on a healthy or near-healthy drive.

 

[Snick]

An Orphaned file in Windows is a file that has lost the parent child association. On a computer's hard drive, an orphan file is a support file (such as a DLL file) that no longer serves a purpose because the "parent" application it is associated with has been moved or uninstalled. This will appear in the CBS.log. Search for "Error " without quotes & yes space is used to parse results from "error".

I don't see a need to run chkdsk more than once in almost every situation, gleaned from Niemiro, Windpws Update Training Academy.

chkdsk /r implies /f i.e. you don't need the /f switch.

You might want to run SFCFix.exe (by niemiro) from your desktop it does a little more in the way of repairing files, associations, etc.

Please post log it generates on your desktop and CBS log which is located at C:\Windows\Logs

 

[PotatChip]

However, if the HDD is defective, then you could be wasting your time, as CHKDSK can never actually repair a HDD, only the integrity of the data on a healthy or near-healthy drive.

The thing is, i migrated the files from a HDD marked as caution by crystaldiskinfo to a new hard drive.
The files before migrating was mostly fine, but me being the big goof i am didnt check if there files migrated OK and decided to go right ahead to perform a chkdsk on the new drive

and now files i previously recognised to be fine are now apparently "orphaned"...

An Orphaned file in Windows is a file that has lost the parent child association. On a computer's hard drive, an orphan file is a support file (such as a DLL file) that no longer serves a purpose because the "parent" application it is associated with has been moved or uninstalled.

Then how come files such as jpgs, pngs, mp3s and such are now "orphaned"?
will try to run SFCFix.exe tomorrow after I get home

 

[Snick]

The thing is, i migrated the files from a HDD marked as caution by crystaldiskinfo to a new hard drive.
The files before migrating was mostly fine, but me being the big goof i am didn't check if there files migrated OK and decided to go right ahead to perform a chkdsk on the new drive

How do you know the files before migrating were mostly fine?
Should have run chkdsk /r before you migrated.

 

[PotatChip]

How do you know the files before migrating were mostly fine?
Should have run chkdsk /r before you migrated.

I knew the files were mostly fine because I had copied some of the files by hand onto a memory stick and they were all fine, and also, I have a good few songs on that drive that were working fine up to the day I migrated.

I also did run chkdsk before I migrated, but felt the needed to do it again after migration




(recovering orphaned files process now at 44034 of 713943)

 

[Snick]

I also did run chkdsk before I migrated, but felt the needed to do it again after migration
(recovering orphaned files process now at 44034 of 713943)

Excellent!

Here's an article from TechWalla for your perusal.
What Does Recovering Orphaned File Mean? | Techwalla.com