Backup superblock offset
Posted: 17 Jun 2020, 21:19
First of all, many thanks for such amazing tool. I have successfully recovered lost partitons by the testdisk deep scan. But I was unable to do the recovery with quick scan and I noticed following behavior:
I have lost two ext4 partitions on two independent physical discs by wrongly overwriting GPT tables of the disks.
The testdisk quick scan identified the backup superblock of both ext4 partitions, correctly identified the partition label, size and type, but no files could be listed and the filesystem was reported as corrupted.
By doing the deep scan I was able to find primary superblocks and recover the partitions.
In both cases, there was a difference of 2 units (bytes?) between the start of partition as determined by primary and backup superblock.
I suspect there may be some miscalculation of partition start position when backup superblock is used. The version used was Testdisk 7.0 on Ubuntu 18.04.
I have lost two ext4 partitions on two independent physical discs by wrongly overwriting GPT tables of the disks.
The testdisk quick scan identified the backup superblock of both ext4 partitions, correctly identified the partition label, size and type, but no files could be listed and the filesystem was reported as corrupted.
By doing the deep scan I was able to find primary superblocks and recover the partitions.
In both cases, there was a difference of 2 units (bytes?) between the start of partition as determined by primary and backup superblock.
I suspect there may be some miscalculation of partition start position when backup superblock is used. The version used was Testdisk 7.0 on Ubuntu 18.04.