-
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
Script still fails after attribute list step #79
Comments
Thank you for reporting this issue. OK, this is a bit weird. It seems there is a file record which is not complete (truncated). This should almost never occur (in fact, this is the first time it does). Anyhow I added an extra check. Could you please try with the latest code? Thank you. |
Now it fails with:
|
Could you please try to change this line:
To this one?
Please note that it occurs twice in Thank you. |
Same failure:
|
Can you try like this?
|
Progress! It completed indexing. Running "recoverable" printed almost 3300 entries, but almost all with no size given, and the number of files as 16 or 32 or other low multiples of 8. I don't know whether that's normal. Partition # 23 showed with nearly the full size of the hard drive, and more than 100,000 files. Running "restore 23 5" recovered many files, yay! It worked through the \Users directories. I don't think it restored all the files which were originally on the hard drive. Again, I don't know whether that's normal. (Any tips to possibly recover more files from \Users ?) The script did eventually fail again with:
I don't care about any files other than in \Users, but if you want me to test anything else to debug that crash, or send the list of >100 partitions if that's unusual behavior, I'm happy to do so. (Though I'm doing this recovery for a friend on a large external HD of hers, so will only have the image file to test with for a few more days.) For background info: I used ddrescue to 99.99% image a hard drive which no longer booted or mounted due to read errors in early sectors. I'm running recuperabit on the image. And thank you for such a useful tool, and for your quick responses here! I greatly appreciate it. |
@norristh thank you very much for your feedback, it is very helpful!
This is due to heavy disk fragmentation. The more a drive is used, the more it happens. RecuperaBit does not attempt to blindly merge partitions, thus sometimes many different partitions are detected.
Possibly they could be in the
Ouch. This is left from the migration to Python 3. It seems the smaller sample NTFS on which I tested it did not reach this part of the code. It should be fixed now.
Thank you. It would be great if you could try the latest commit.
Please be aware that if there are compressed files, those will not be recovered. I mean NTFS-compressed files, not archives. RecuperaBit does print a warning in this case though. |
Success all around! The restore completed with all seven partitions I tried, both Root and LostFiles for each. And by restoring from all partitions with more than 20,000 files, between Root and LostFiles I may have restored all the files my friend was worried about. Thank you again for working on and sharing this tool! |
I am glad it worked for you. 😊 Yesterday I had a very bad day and this news is cheering me up a bit. Per the testing you performed, I can now tag a new release on GitHub with all these fixes. Thanks! |
Thanks for fixing #78 !
However, now the script version 1.1.3 fails with:
The text was updated successfully, but these errors were encountered: