Help needed. On the last leg of deleted partition table recovery but too much of a noob to finish.
Posted: 17 Jan 2020, 10:45
TLDR; i have to use the original partitioning tool (minitool) to recreate the lost partitions on the disk to recover but minitool forces you to create a 128MB partition when initializing to GPT. Can i do the same with testdisk instead?
Full version:
1. The GPT disk to recover contained 5 veracrypt encrypted data partitions. the partitions were created with minitool partition wizard and later formatted/encrypted using veracrypt. partitions had the following sizes:
2. clonezilla script (accidentally) tried to restore a different mbr disk's image to the above disk. it errored before any actual data was overwritten but filesystem header and partition table were deleted. Here is a pseudo clonezilla log created after the fact but under similar conditions:
3. the partitions and the encrypted volumes therein were luckily created with poor security practices ie:
4. probably due to (3) there are large portions of hex 00's occupying the free space of the encrypted volumes. by using dmde's hex view i was able to find large swathes of these zeroes followed by data followed by zeroes and so on. the start to end sector ranges of these portions match the disk sizes listed in (1). screenshot of sdd5 for example. probable start sectors of partitions (ie first non 00 hex after lots of 00's):
5. this is where i'm stuck. i see from several sources (example here) that by simply creating the partitions of the same sizes using the same partitioning tool (in my case minitool), i should be able to mount the veracrypt volumes again. BUT:
I'm positive i can do this with testdisk but don't know how. Can someone help me finish? Also note that i'm working on a cloned copy of the disk to recover created with ddrescue/knoppix.
Full version:
1. The GPT disk to recover contained 5 veracrypt encrypted data partitions. the partitions were created with minitool partition wizard and later formatted/encrypted using veracrypt. partitions had the following sizes:
Code: Select all
sdd1: 700GB
sdd2: 700GB
sdd3: 1900GB
sdd4: 350GB
sdd5: 76.02GB
Code: Select all
Clean filesystem header in device /dev/sdd1...
Clean filesystem header in device /dev/sdd2...
Clean filesystem header in device /dev/sdd3...
Clean filesystem header in device /dev/sdd4...
/dev/sdd4: 4 bytes were erased at offset 0x000001c6 (atari): b9 d3 d8 fa
Clean filesystem header in device /dev/sdd5...
Trying to clean the MBR and GPT partition table on the destination disk first: /dev/sdd
Informing the OS of partition table changes... done !
Non-grub bootloader found on /tmp/sdc-rolling-backup-tmp-cnvted/sdd-mbr...
The CHS value of hard drive from EDD will be used for sfdisk.
Sfdisk >= 2.26 does not support C/H/S option. Skip using C/H/S option.
Error: /dev/sdd: unrecognised disk label
**************************
Tue Jan 7 14:36:24 UTC 2020
Writing the partition table...
No partition table exists in target disk /dev/sdd, try to initialize one so that we can get the disk
size by parted... Running: parted -s /dev/sdd mklabel msdos
done !
Warning!! Destination disk (/dev/sdd) size is 4.00TB, which is larger than the MBR partition table
entry maximum 2 TiB (~2.2 TB). You have to use GUID partition table format (GPT).
Press "Enter" to continue......
[Panic rebooted here]
Code: Select all
a. full format brand new disk
b. create 5 partitions with minitool partition wizard (quick formatted if at all)
c. veracrypt volumes created with quick format
d. mount volume and copy data
Code: Select all
sdd1: 4096
sdd2: 1468008448
sdd3: 2936014848
sdd4: 6920603648
sdd5: 7654606848
- the disk is currently in MBR mode. If i try to initialize to GPT, minitool forces me to create a 128MB partition. this partition did not exist on sdd as it was promptly deleted after creation (when originally setting up the partitions on the disk).
- minitool does not allow specifying start and end sectors.
I'm positive i can do this with testdisk but don't know how. Can someone help me finish? Also note that i'm working on a cloned copy of the disk to recover created with ddrescue/knoppix.