Check Disk shuffled the files on the entire disk.

[mys]

After the power cut while the computer was running, I restarted the computer and while it was still on the boot screen, a partiton of the HDD disk, which was previously partitioned, gave the following errors by sudden Check Disk application.

How can I repair them back? Thanks in advance.

Notes:
* Almost all the files in the corrupted partition were moved to the Found folders and mixed together, including the content. The second and third Check Disk attempts gave less errors.
* Previously, Windows 10 was installed on this partition.
* Found folders moved twice.
* Previously, this partition switched to Linux-Swap type by Linux firmware installed on other HDD partition accidentally, then switched back to NTFS with TestDisk software.
* The remaining files were processed because this situation did not improve for a long time.

 

[Corday]

If you have your files backed up (hopefully twice), delete them from disc(s) you don't want them and reinstall properly.

 

[mys]

There are important files that I need to recover from the Found folders, except the Windows OS parts. It will take "long time" to fix them by human hand. Also, it was one of its backup partition.

If you have your files backed up (hopefully twice), delete them from disc(s) you don't want them and reinstall properly.

I moved them, because presumably the Linux firmware damaged this partition, so it was repartitioned for avoid further damage.

 

[Corday]

Since they were in the root directory of the corrupted drive, I suppose you searched for hidden folders and unless someone else knows what to do with supposedly corrupted files/folders, you're stuck with an arduous and time consuming task.

 

[xrobwx71]

You could try a file recovery app like this one you can recover 2GB for free.

 

[mys]

Since they were in the root directory of the corrupted drive, I suppose you searched for hidden folders and unless someone else knows what to do with supposedly corrupted files/folders, you're stuck with an arduous and time consuming task.

Yes, I've searched System Volume Information/Chkdsk directory after the corruption happened and two-three Check Disk Attempts. This is how I found log files. At least somehow I want to leave it to Windows OS' task.

 

[Corday]

Any chance you made a System Image? If so you could just put it on a HD or SSD and nothing will have been lost.

 

[mys]

Any chance you made a System Image? If so you could just put it on a HD or SSD and nothing will have been lost.

If you're mentioning about ~8 gigabytes file named as hexadecimal codes ("System Volume Information/3{3808876b-c176-4e48-b7ae-04046e6cc752}"), yes, but also I tried for likely two days to extract the file but it didn't come out. However it was deleted after repartitioning.

 

[Corday]

So you didn't make it to an external drive????

 

[Tekno Venus]

Unfortunately you've come across the one big downside of chkdsk - it's actually a pretty dangerous tool when used on a badly damaged drive.

Chkdsk, when run with the /f flag, has one job - detect file system errors and attempt to fix them. Chkdsk is not an incredibly smart tool - all it will do is try to fix the errors it finds. This is often at the expense of having to either move data around, or in some cases remove data entirely to achieve its goal. It can occasionally recover corrupt data, but even then it often is only able to perform partial recovery.

Performing chkdsk on a failing drive can also put a lot of extra stress on the drive - it's not particularly uncommon for a drive to be dying and a chkdsk run pushing it over the edge and killing it.

I know it's little use now, but chkdsk in repair mode should never be run on a disk without performing a full backup first for the exact reason you've seen - sometimes the fixes performed can cause harm in other ways.

Tools such as VoidTools' Everything (voidtools) can search the entire drive to help you find files that may have moved and Recuva (Download Recuva | Recover deleted files, free!) might be able to restore some lost data, but I'll warn you the chances are slim.

Sorry to say there's very little you can do here if you don't have any backups of your data before chkdsk ran. If the data is absolutely essential, stop using the drive immediately and discuss your situation with a data recovery company.