-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge functionality gives errors on restore and seems to recover unrelated files #20
Comments
Did you run
|
Never mind. I found an issue with the I am going to check if there is a good way to fix this. |
Please try this one. There could still be issues if you run I suggest you run |
Thank you. |
Woops! 😅 OK done, thanks. |
I tried it again, and sadly it gives me a similar result. But I'm getting a few unrelated random files again, and nothing from my old partition. Despite 312 being listed as having lots of files:
I didn't do any operations except merge with 312 on any other partitions. |
BTW why are you merging everything into |
I tried that and it seems to be working. |
Ok, I merged them in order by partition #, starting from 248, 283, 312, 451, 1007. Then I restored all files by restoring 248. At first it seemed like it was restoring them exactly like it did when I restored the 5 partitions individually. The same folders were in the Root folder, the majority of files were in the LostFiles folders, and everything seemed similar. As if I had restored the 5 partitions one by one and just merged the output folders together. Unfortunately by this I also mean that I found no corrupted files that got "repaired". Most files were corrupted. Then I noticed something very odd. The size of the output folder was 1/3 the size of the output folder of the 5 partitions I restored individually. I thought that maybe I forgot to include 451 Also when I list recoverable, partition 248 has less files than the sum of the other partitions'
This is different from when I merged starting from 312, where you could see there were 500k+ files. |
Well, this is not really something we can do much about. If the files were partially overwritten those parts cannot be recovered. I did not notice that the partitions were "out of order". Try merging them in the MFT order, they should be like this if I am correct:
This ordering thingie might be automated if we see that it works but I would like to try a bit before pushing other modifications. Also, could you please share privately with me all those CSV files (merged and not merged)? Thanks. |
Hi, sorry for the late response. |
I tried using the new merge functionality on the 5 partitions I referenced in issue #18 , however the recovery wasn't successful.
Here is the output:
https://pastebin.com/sns4t84A
Notice first how the root doesn't contain any files. In the individual partitions I had recovered before, some of them had files in the root directory, therefore I would assume that at least those files would end up in the root once I merged these partitions.
As for the LostFiles, it has very few files and none of them were part of the original partition.
In fact from the bodyfile, I noticed that their timestamps were from before the original partition was even created.
Here are the exact commands I executed:
Then I tried to restore partition
#312
.After the merge, it was listed like this when issuing the
recoverable
command:Partition #312 -> Partition (NTFS, ??? b, 576538 files, Recoverable, Offset: 264192, Offset (b): 135266304, Sec/Clus: 8, MFT offset: 4287141256, MFT mirror offset: None)
The text was updated successfully, but these errors were encountered: