PLX OXUF943SE keyblock
Closed this issue · 7 comments
Hi, I've recently come across this tool and tried to follow the instructions. However, I got stuck at trying to obtain the keyblock (as shown in the screenshot. I have a 2TB My Book with PLX OXUF943SE - the device is assigned sde.
Would be really grateful if anyone could help me with this issue, Thanks! Do let me know if there's any other info I could provide that would help.
That error indicates that /dev/sde does not contain enough blocks to skip that far. Maybe you are mistaken about which drive is the WD drive, or you didn't take it out of the enclosure and use a generic enclosure, or we are wrong about the keyblock location. Try doing lsblk to see what drives you have and their sizes.
Here's a screenshot with lsblk. Some more details on my setup: sda is my internal drive, sdd is my bootable ubuntu drive, sde is the drive in questions with a generic enclosure.
Not sure why I have 3 partitions, but this drive was previously formatted in HFS+. I've tried the keyblock locations for the other chipsets as well, all the others returned something along the lines of 00000000000 (I assume because nothing was located there - I can take a screenshot if needed).
It might not be encrypted. Have you tried opening it with a Mac?
Under OSX:
- With Generic Enclosure: Disk is not readable
- With the original enclosure's chipset with PLX OXUF943SE: Drive mounts, but is extremely slow in accessing data - I'm unable to retrieve my data (this led me to believe the controller has problems and how I ended up searching for the program you made)
Given the details above, I can't access my files with a generic enclosure or with the original enclosure. This hard drive still has some data (which I can see but cant extract with the original enclosure in OSX), so I was wondering if there's anything else that we can try.
Is there a possibility that the keyblock location could be somewhere else? As I noted from the pdf that the keyblock location for this combination of drive size and chip was uncertain.
If you can see the data in OSX (i.e. see the filenames) but not copy the files, then try using sudo in the Terminal App. The sudo
command works the same on OSX as in linux.
With the PLX chip, people have had almost no luck finding the key elsewhere. You could try dumping the service-area modules with HDDSuperTool (google knows where to find it). Or it could be stored in a memory chip on one of the boards. I'm sorry there isn't an easy answer.
Thanks for advice, I'll see if HDDSuperTool can help with dumping the modules.