Photorec

[conib00]

Hello I am running Photorec against a 4Tb NTFS disk to retrieve JPG and MPG with file option JPG an MPG on Ubuntu 20.04.
At a disk with no problems I just want to retrieve deleted pictures
Now I see on
date 2022-02-18 Pass 1 - Reading sector 444548496/2930272002, 10596 files found. Elapsed time 140h estimated time to completion 787h
date 2022-02-21 Pass 1 - Reading sector 413585288/2930272002, 12038 files found. Elapsed time 212h estimated time to completion 1293h
date 2022-02-23 Pass 1 - Reading sector 476622304/2930272002, 12954 files found. Elapsed time 260h estimated time to completion 1338h
Why is it that the Reading sector goes up and down? and time to completion goes up so much??
And reading sector also strange readings.

Where/when does this end??

Regards Bas.

[recuperation]

Hello I am running Photorec against a 4Tb NTFS disk to retrieve JPG and MPG with file option JPG an MPG on Ubuntu 20.04.

And what is your Photorec version?

At a disk with no problems I just want to retrieve deleted pictures
Now I see on
date 2022-02-18 Pass 1 - Reading sector 444548496/2930272002, 10596 files found. Elapsed time 140h estimated time to completion 787h
date 2022-02-21 Pass 1 - Reading sector 413585288/2930272002, 12038 files found. Elapsed time 212h estimated time to completion 1293h
date 2022-02-23 Pass 1 - Reading sector 476622304/2930272002, 12954 files found. Elapsed time 260h estimated time to completion 1338h
Why is it that the Reading sector goes up and down? and time to completion goes up so much??

Broken sectors will increase recovery time. Testdisk is not supposed to work on such broken drives. Check the health of your drive and depending on the outcome you will be better off duplicating your drive using ddrescue. Are you recovering your stuff on a separate disk?

And reading sector also strange readings.

Where/when does this end??

Please ask a clairvoyant.

[conib00]

And what is your Photorec version?

The version I use = "PhotoRec 7.1, Data Recovery Utility, July 2019.

Yes I am using a separate disk for the "recup_dir.##" files

I am using a 4Tb disk (USB) and had no problems with reading and writing in the past.

[recuperation]

Please try again using the most recent Photorec version "7.2 WIP".

To get a quick overview on possible health issues of your drive post your smartmontools log file:

viewtopic.php?f=5&t=10910

[conib00]

Please try again using the most recent Photorec version "7.2 WIP".

To get a quick overview on possible health issues of your drive post your smartmontools log file:

viewtopic.php?f=5&t=10910

see attachments

[recuperation]

I have never seen such an empty SMART report.
You could try to duplicate the drive using ddrescue. By looking at the ddrescue command prompt style you will quickly see if ddrescue works or if it hangs on certain sectors.

But I guess you will probably need professional assistance.

[conib00]

I have never seen such an empty SMART report.
You could try to duplicate the drive using ddrescue. By looking at the ddrescue command prompt style you will quickly see if ddrescue works or if it hangs on certain sectors.

But I guess you will probably need professional assistance.

I think this report is better