themaddoctor/linux-mybook-tools

WD Mybook Essential 3TB with USB 3.0 won't mount at last stage...

Opened this issue · 3 comments

Hi Thomas. I have a WD Mybook Essential 3TB with USB 3.0. Inspecting the board shows that it has the JMicron JMS538S chip. I used to use it in Windows and it contains MY ENTIRE LIFE. Unfortunately it started to act strangely. It hid the videos folder from me and then within 24 hrs was returning an error in Windows telling me the drive needed to be formatted to use it. Don't worry! I'm not that stupid! I have NOT formatted it.

I have installed Ubuntu, downloaded your tools and followed your tutorial and although I initially had a few hiccoughs with following the procedure, I believe every step has gone successfully (your tests all passed) until the very last command for mounting the disk, whereupon I get the error message, 'mount: /mnt/wd: wrong fs type, bad option, bad superblock on /dev/mapper/wd1, missing codepage or helper program, or other error.'

I have tried several times to no avail. I ran your test for a corrupted MBR and found the results were NOT as expected. I got the word data returned for lines 1 & 2 but not 3 & 4. You didn't say what THAT meant. I don't know whether that means my MBR is corrupted or not although I HAVE had the drive on a regular SATA bridge in Windows before I knew that was a useless endeavor.

Thinking this might be the issue, I tried doing the loop mount method and this failed too. Any help would be greatly appreciate. I went to a data recovery 'expert' once before over a different drive and I believe them to be mainly overpriced fraudsters from experience so, I don't want to have to do that if I can avoid it.

Send a hexdump of the keyblock, sector 0, and sector 2048, and I will look at it when I have the time.
sudo dd if=/dev/whatever count=1 | hexdump -C
sudo dd if=/dev/whatever count=1 skip=2048 | hexdump -C
hexdump -C whateveryounamedthekeyblock

Thank you so much. :-)

Here are the hex dumps you have requested. :-)

Napier's Hex Dumps.tar.gz

They decrypted fine for me. Sector 0 decrypted to an MBR with this partition table:

Disk Napier-3TB-JMS538S-sector0-decrypted.bin: 512 B, 512 bytes, 1 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000246c6

Device Boot Start End Blocks Id System
Napier-3TB-JMS538S-sector0-decrypted.bin1 256 732558335 366279040 7 HPFS/NTFS/exFAT

Sector 2048 decrypted to what looks like NTFS headers.