Identifying LUKS partition

How to use TestDisk to recover lost partition
Forum rules
When asking for technical support:
- Search for posts on the same topic before posting a new question.
- Give clear, specific information in the title of your post.
- Include as many details as you can, MOST POSTS WILL GET ONLY ONE OR TWO ANSWERS.
- Post a follow up with a "Thank you" or "This worked!"
- When you learn something, use that knowledge to HELP ANOTHER USER LATER.
Before posting, please read https://www.cgsecurity.org/testdisk.pdf
Locked
Message
Author
ert8y734
Posts: 2
Joined: 15 Nov 2020, 23:47

Identifying LUKS partition

#1 Post by ert8y734 »

I used testdisk 7.2 to recover partitions on a GPT disk and it did not correctly identify the end of a LUKS partition, only the start, and instead it at 4096 sectors. I had a previous fdisk -l printout and could correct the size and recover the data which was great!

My question is if anything can be done to identify the size of LUKS partitions better?

Second, when I created a new partition of the right size it looks like the program does not identify it as LUKS at the bottom of the screen as it does with other partition types. Perhaps a bug?
recuperation
Posts: 3036
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: Identifying LUKS partition

#2 Post by recuperation »

ert8y734 wrote: 15 Nov 2020, 23:54 I used testdisk 7.2 to recover partitions on a GPT disk and it did not correctly identify the end of a LUKS partition, only the start, and instead it at 4096 sectors.
Please write in understandable english using verbs. I have no clue what "and instead it at 4096 sectors." should mean.
I had a previous fdisk -l printout and could correct the size and recover the data which was great!

My question is if anything can be done to identify the size of LUKS partitions better?
No.

As the content of a LUKS partition is encrypted, Testdisk cannot look inside. There are a few pieces of information at the beginning of a LUKS partition that suggest that it's the beginning of a LUKS partition. This information available is not refering to the length of the LUKS partition.
ert8y734
Posts: 2
Joined: 15 Nov 2020, 23:47

Re: Identifying LUKS partition

#3 Post by ert8y734 »

Sorry, it should have been that testdisk estimated it a 4096 sectors. So, there is nothing that can be done to better estimate the size of a LUKS partition?
recuperation
Posts: 3036
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: Identifying LUKS partition

#4 Post by recuperation »

ert8y734 wrote: 16 Nov 2020, 20:36 Sorry, it should have been that testdisk estimated it a 4096 sectors. So, there is nothing that can be done to better estimate the size of a LUKS partition?
Did you understand me? I already wrote:
recuperation wrote: 16 Nov 2020, 11:12 As the content of a LUKS partition is encrypted, Testdisk cannot look inside. There are a few pieces of information at the beginning of a LUKS partition that suggest that it's the beginning of a LUKS partition. This information available is not refering to the length of the LUKS partition.
Locked