cgsecurity.org

Presumable Photorec's recovered file are named using some data integrity algorithm (like checksum). What algorithm exactly? Having this information would help identity duplicates.

In the latter case you would have tried to duplicate the disk using ddrescue as described in the manual and rechecked the SMART parameters after the duplication process. So I did up to checking SMART, below. I'm getting a clicking sound with this backup disk, though.

$ sudo smartctl -a /dev/sdc ...

I was giving earnest feedback as a self declared novice, but I've only succeeded in rubbing you the wrong way. I'm sorry about that. However, I must point tout that:

"I am sorry for that but Testdisk is a professional tool not aiming at computer starters. "

is contradicted by this page that says ...

This is a follow up from this post , after which I launched an analysis in GPT mode (much faster). I selected `P` for `[Vol 1]`, which took me to the screen below. There is an indication at the bottom that says ": to select the current file". If I do that on `.`, it moves the cursor to ...

I'm beginning to understand there are three different words for a given partition type, that is, MBR=Windows=Intel, and one can deduce it is the choice that has been made to run the analysis based on "Your screen is filled with found partitions in CHS (cylinder, head, sector) adresses." This level ...

You started Testdisk in MBR mode.

What makes you say so? The first code snippet shows eleven lines preceded by 'P'. Aren't these 11 partitions? That's not possible under MBR. Besides, there weren't 11 partitions. There were 3 that I created, Vol 1,2 (encrypted),3. I think I chose the default 'no ...

This is a follow up from this post , after which I launched an analysis in GPT mode (much faster). I selected `P` for `[Vol 1]`, which took me to the screen below. There is an indication at the bottom that says ": to select the current file". If I do that on `.`, it moves the cursor to `..`. Bottom ...

My filesystem was corrupted in such a way I could login, but was only able to use the command line. So I installed an upgraded OS (from Linux Mint 19 to 23). To do so I wrote the reboot iso image to an external drive (below, sdc), and launched the reboot from there. The end result is: the old ...