-
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
Eternal loop reconstructing MFT #6
Comments
Please, before line
Add the following lines:
With the same indentation. This will stop the program just after the scan, printing useful debug information. |
This is the output with those lines: recuperabit.txt |
From the output you posted, it seems you have various traces of files which get divided into over 127000 (127 thousand!) partitions. This can result from an extremely fragmented MFT (that maybe has sustained defragmentation many times in the past). See this file where they are ordered by Long story short, the program is not looping, it's just running. 😅 You might want to put a limit to ignore partitions with few files. For instance, you can ignore those with less than 5001 files. Start with a fresh, unmodified copy of RecuperaBit and add this before line
This way you will only analyze about 50 partitions. I am going to close this issue, however you might consider suggesting one or both of these:
These could be nice enhancements in the future. |
Great! Thanks for the suggestion. I'll try what you suggested. |
I was running RecuperaBit on a 466GB image for a little longer than 100h. I looked at the output and it was repeating the same positions set number.
For example, if you look at the output file, look at the first three positions: 38190544, 37475152, 38357392. The last three positions on the end are the same: 38190544, 37475152, 38357392.
I was able to grab only this part of the output, but when I checked there was more repetition (around 10 or 15 positions). I realized it was repeating the same sequence over and over.
The drive I'm running at is a very damaged one. I'm not sure if it's the image issue (unrecoverable) and I should let it go.
(some more info: running on Mac OS 10.12.1, was using a whole lot of memory, around 12GB~14GB)
The text was updated successfully, but these errors were encountered: