External hard drive mistakenly formatted while creating a bootable key

[vince99]

"Hello,

I created a bootable key to install the latest Linux Mint, and by mistake (in haste), I created the "bootable key" on the 1.5TB HD where I kept my backups. As a result, I lost all my data.

I ran TestDisk, but it couldn't find any partitions initially. Then, while trying to go back (pressing 'q'), it started a 'cylinder analysis'.

The result of this analysis is as follows:

TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER grenier@cgsecurity.org
https://www.cgsecurity.org

Disk /dev/sda - 1500 GB / 1397 GiB - CHS 182397 255 63

The harddisk (1500 GB / 1397 GiB) seems too small! (< 3000 GB / 2794 GiB)
Check the harddisk size: HD jumper settings, BIOS detection...

The following partition can't be recovered:
Partition Start End Size in sectors

It's better to see it in an image:

testdisk

Capture d’écran du 2023-07-26 18-08-41 cadre.png (52.61 KiB) Viewed 1536 times

Does anyone have an idea of what this means?

Could creating a 'bootable key' on my HD interfere with TestDisk's analysis of the disk?

Would it be better for me to remove the Linux installation files from the disk to have a greater chance of data recovery?

Or any other suggestions, of course.

Thank you for your responses.

[recuperation]

Please upload your picture on this website using the attachments tab to the left on the bottom of this page.

[vince99]

I tried a new search by selecting 'EF GPT' and I got the following message:

Capture d’écran du 2023-07-29 13-12-59.png (35.99 KiB) Viewed 1425 times

Should I try selecting other options?

Does anyone have any other ideas?

Thank you.

[recuperation]

"Hello,

I created a bootable key to install the latest Linux Mint, and by mistake (in haste), I created the "bootable key" on the 1.5TB HD where I kept my backups. As a result, I lost all my data.

I ran TestDisk, but it couldn't find any partitions initially. Then, while trying to go back (pressing 'q'), it started a 'cylinder analysis'.

The result of this analysis is as follows:

TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER grenier@cgsecurity.org
https://www.cgsecurity.org

Disk /dev/sda - 1500 GB / 1397 GiB - CHS 182397 255 63

The harddisk (1500 GB / 1397 GiB) seems too small! (< 3000 GB / 2794 GiB)
Check the harddisk size: HD jumper settings, BIOS detection...

The following partition can't be recovered:
Partition Start End Size in sectors

It's better to see it in an image:

Capture d’écran du 2023-07-26 18-08-41 cadre.png
Does anyone have an idea of what this means?

There is a small partition at the end of the disk.

Could creating a 'bootable key' on my HD interfere with TestDisk's analysis of the disk?

You should not create another one before having finished all your recovery efforts.

Would it be better for me to remove the Linux installation files from the disk to have a greater chance of data recovery?

Do not alter the crime scene unless being in certain corner cases where Testdisk is awakening the death.

[vince99]

Thank you recuperation.

Could creating a 'bootable key' on my HD interfere with TestDisk's analysis of the disk?

You should not create another one before having finished all your recovery efforts.

"Oh no, I don't want to create anything more , I just wanted to know if creating the bootable key beforehand could hinder TestDisk's analysis when it is searching for partition table.
I must have made a poor translation.

While searching on this forum, I found Jamsah's case and I was wondering if I could try this solution?

Screenshot 2023-07-29 at 21-00-22 the following partition can't be recovered_ filesystem damaged - cgsecurity.org.png (114.48 KiB) Viewed 1385 times

Is it dangerous for the data? Should I create an image of the disk first?"

Thank you.