leni1 wrote: 26 Jun 2024, 23:26
As opposed to your initial postings I had to read the last one three times.
Could you specify exactly what you mean by "this behaviour"?
What was strange: The image of my data is on a 5TB drive
The size of your disk where you stored the image of your data does not matter as long as there had been enough space to save the image.
and in the PhotoRec options, I chose to search the whole partition.
This is not a good case description. Where?! On that 5TB disk? You have to pass over the the clone file to PhotoRec or mount that file as a disk.
The search ends at ~1 hour or so mark, alerting me that I do not have enough space on the destination.
Bad description. Which (new) destination?
By ends, I mean the search pauses, asks me to confirm that the destination directory is correct
If you confirmed a file location on a full disk there is nothing to cure this "behaviour".
and then returns me to the screen showing how many passes it has made, with estimated time having tripled from ~11hrs to ~120hrs.
The above is the behaviour I meant.
The image is of a failing HDD that was NTFS partitioned and of size 250GB (the data itself is ~230GB in size). The destination is a folder on a 1TB drive which should have enough space.
"Should" is subjunctive. And "enough space" is not a quantitative term.
with this line describing the environment in which I am doing the data recovery. I trust that makes it clear.
Given my questions, nothing is clear.