Just reporting a crash during Bruteforce pass (pass 1 recovery went fine). Happened ~17 hours into bruteforce pass.
System: Windows 7 64-bit
photorec_win.exe recent 7.1-WIP: SHA256: F952613403911F11C47D6CF79D1E0B063CA05BB1D2C542443A964FBDEE7C89AA
Side note: I'm still running an early stepping ...
Search found 3 matches
- 03 Dec 2018, 00:18
- Forum: File recovery
- Topic: PhotoRec - Crash during Bruteforce pass
- Replies: 0
- Views: 1725
- 03 Dec 2018, 00:04
- Forum: Partition Recovery
- Topic: No way to specify approx. partition positions for Deep Search?
- Replies: 2
- Views: 2116
Re: No way to specify approx. partition positions for Deep Search?
Thanks, I will keep it in mind for the next time (hopefully not). And it's not in the testdisk.pdf manual. My suggestion would be to have a kind of an "S" key to skip, say 5 GB per single press.
- 28 Nov 2018, 17:33
- Forum: Partition Recovery
- Topic: No way to specify approx. partition positions for Deep Search?
- Replies: 2
- Views: 2116
No way to specify approx. partition positions for Deep Search?
I'm in the process of recovering the partition table after it was completely wiped on the HDD. I was wondering why is there no way to specify approximate positions (start/end) of the partitions to speed up the process of Deeper Search?
I have a 2TB HDD and I know that the first partition was ~1.2 ...
I have a 2TB HDD and I know that the first partition was ~1.2 ...