Page 1 of 1

Photorec stops at sector, application does not respond

Posted: 27 Nov 2014, 09:23
by svshane
Hi,

I'm using Photorec 7-WIP to recover JPGs form a NAS drive which has been formated before.

I'm using default settings but filtering only for JPGs.

It is running fine and already recovered 3500 JPGs until it suddenly stops at a sector and does not respond any more. At next start recovery can be selected, but again after a few seconds it stops.

Please see attached screenshot.
Photorec console
Photorec console
photorec.jpg (58.44 KiB) Viewed 3409 times
I searched the forum and discovered a post that it is possible to edit the ses file and insert another sector but PR starts at the same old sector even if I change it. Maybe I'm doing sth. wrong.

How should I choose the sector to continue?

What is the list below the second line in the ses file?

2120628-2395251
2405620-2406131
2419444-2420083
2436852-2437683
2451188-2451827
.
.
.

Anyway, thanks so far for your work Christophe.

UPDATE: I recognised that version 7 is still beta hence I tried version 6.14, it is working fine now. Post can be closed or deleted.

Regards
Stefan

Re: Photorec stops at sector, application does not respond

Posted: 27 Nov 2014, 21:13
by sockface
Thanks for posting this! I've also found the same problem with 7.0 not realising it's a beta. It seemed to be working wonders until it would hang just like yours did, im now running 6.14 but it'll take a while to reach where it fairly consistently stalling in 7.0.

I didn't take any screen grabs, but i have noted that 7.0 would stall between sectors 92,614,002 and 92,682,320 out of a total 976,773,168 sectors. This was over 4 attempts using default options and only recovering .jpg file types.

testdisk-7.0-WIP on Windows 7 64bit

Re: Photorec stops at sector, application does not respond

Posted: 28 Nov 2014, 09:04
by cgrenier
Do you know the type of the last file recovered using PhotoRec 7.0-WIP ?

Re: Photorec stops at sector, application does not respond

Posted: 09 Dec 2014, 10:30
by svshane
It was a JPG, cause I set the filter to only apply to JPGs.