This is going to come across as a very strange question, but what happens if I use the cfdisk on the slackware dvd to rewrite the partition table precisely as I did before?
|
This looks like a valid bootrecord. Have you tried just mounting your partitions? What is the output of
Code:
fdisk -l |
Quote:
Code:
fdisk -l Code:
Disk /dev/sda: 500.1 GB, 500107862016 bytes |
Do a
Code:
dd if=/dev/sda | hexdump -C | grep 'LUKS' If you don't see a line starting with the characters "LUKS" then your luks header is gone and whatever else has happened to the drive really doesn't matter. |
Quote:
Code:
testdisk /debug /log /dev/sda |
unSpawn, Does testdisk detect luks headers? I didn't see any mention of it on its website?
|
AFAIK no. The only reason why I would want the PT restored is to have a boundary for running 'isLuks'. One could look for
Code:
#define LUKS_MAGIC {'L','U','K','S', 0xba, 0xbe}; |
Quote:
Code:
dd if=/dev/sda | hexdump -C | grep 'LUKS' Code:
1de41bb20 b7 01 4c 55 4b 53 af 44 31 72 fa 19 f6 54 d4 6b |..LUKS.D1r...T.k| |
You have obviously not re-zeroed the MBR since you still show data beginning at address 0. Easiest thing to do is just skip over the first megabyte and see how much of the rest of the drive got zeroed:
Code:
dd if=/dev/sda bs=1M skip=1 | hexdump | head |
[QUOTE=kristizz;4870578]
Code:
dd if=/dev/sda | hexdump -C | grep 'LUKS' Code:
1de41bb20 b7 01 4c 55 4b 53 af 44 31 72 fa 19 f6 54 d4 6b |..LUKS.D1r...T.k| |
Quote:
|
Quote:
Code:
dd if=/dev/sda bs=1M skip=1 | hexdump | head Code:
0000000 0000 0000 0000 0000 0000 0000 0000 0000 |
I just wanted to say a big thank you to those of you who helped out on this. I wasn't able to locate the partition in the end and ran out of time due to the arrival of my baby daughter. Fortunately I was able to use testdisk to recover the files from my wife's external hard drive; she had forgotten that they had been backed up on there a while ago and then deleted, but it looks like they were never overwritten.
|
All times are GMT -5. The time now is 12:10 AM. |