Closed Aztec03hub closed 12 months ago
Can you please try to replace this block: https://github.com/Lazza/RecuperaBit/blob/728e978e459463e259bacca18d8a13a66241f309/recuperabit/fs/ntfs.py#L291-L294
With this code?
candidates = [
(f['content']['namespace'], f['content']['name'] + ads_suffix)
for f in filtered
]
print(candidates)
name = best_name(candidates)
Then re-run the program. It will give the same error but it should also print some useful information.
Unfortunately, this cannot be reproduced.
Hello, I'm quite interested in how powerful RecuperaBit appears.
I have a 2TB NTFS drive, which was given to me in a failed state (with the complete PC). The drive was originally in a RAID, although I'm uncertain as to which kind.
I was unable to obtain much information pertaining to what was done to the drive before it was fielded to me, other than someone trying to rebuild the RAID the drives were part of.
(On the actual affected machine) I was able to start Ubuntu 22.04 from a Live USB, and used ddrescue to create an image of the failed drive, using:
sudo ddrescue /dev/sdb /media/aztec/iODD/test-recovery/copy.img /media/aztec/iODD/test-recovery/status.log
(The iODD is my external device - with 4TB space - which I used to save the "copy.img" onto.)
Following @Lazza 's instructions here, I was able to get the image to begin scanning by RecuperaBit... However, after quite a bit of time, riiiiight at the end of the scan, it outputs the following:
I am uncertain as to how to handle this, and any help would be greatly appreciated.
If any further info is required, just let me know, and I'll do my best to provide it.