Open Antx0n opened 1 year ago
Your NTFS filesystem is luckily still at sector 2048, and is encrypted. You will have to use the loopback method at the end of the PDF document.
The error message you report indicates that something doesn't exist. Try using /dev/dm-1 instead of /dev/mapper/wd-layer1, because a few years ago, linux decided to do things differently. Running the command ls -l /dev/mapper/wd-layer1 will tell you if it is a symbolic link and where it points.
Hi, Thank you very much for your answer; I have tried to implement your suggestions, but I still have the same issue.
I get the same error when I try sudo file -s /dev/mapper/wd
or sudo file -s /dev/dm-1
ls -l /dev/mapper/wd-layer1
and echo | sudo cryptsetup -d - -c rev16-ecb \ create wd-layer1 /dev/sda
both return
WARNING: Device /dev/sda already contains a 'gpt' partition signature. device-mapper: reload ioctl on wd-layer1 (253:1) failed: No such file or directory
Finally, the adapted cat dek.hex | xxd -p -r | sudo cryptsetup -d - --hash=plain \ --key-size=256 -c aes-ecb create wd-layer2 /dev/dm-1
returns
Device /dev/dm-1 does not exist or access denied.
I suppose that I am doing something the wrong way or that there has been a second change in the way linux does things? I checked in the dev/mapper folder, and I only have 2 folders: control and cryptswap
I dunno. Start over and make sure you don't make any mistakes.
Hi, First of all, thank you for your work, it is remarkable, not only because of the amount of work but also because it is disinterested. As most people you are trying to help, I am trying to recover the pictures I had on a My Book Essential 3TB that died after an electrical overload. The closest thread/issue that I have found is this one: https://github.com/themaddoctor/linux-mybook-tools/issues/58, in the sens that I screwed up and clicked the initialize button when Windows prompted it (it was an early morning)... The procedure works fine (I get the DEK and activate the new module without issues) until setting up the filter, then I get the following error:
Is there something that I can try? I eventually thought
Key-block: (my drive is from April 2012 according to the label):
Sector 0:
Sector 2048: