WD My Book essential HDD replacement - wrong size

Toggle sidebar Toggle sidebar
A

assembled

Honorable
Aug 8, 2013
23
0
10,510
Hi,
I have a WD My Book Essential USB 3.0 external drive that originally was 1 or 2TB. Few years ago I replaced the original drive with some older 250GB Maxtor drive and clearly remember that I had to use some software tool to make it work. Now I have a spare 1TB WD Blue that I want to use in this enclosure, but simply connecting it to WD controller shows only those 250GB. I do not remember what exactly I did to make the maxtor work and was unable to google it again as I don't have error codes to start with.

In other words here is what I did:
1. Removed original 1-2TB hdd from WD My Book Essentials
2. inserted Maxtor 250GB
3. did some magic so that My Book controller would recognize and work with Maxtor
4. forgot what exactly I did
5. removed Maxtor
6. inserted WD Blue 1TB and My Book only sees 250GB (roughly)
7. have no idea how to undo magic from No. 3
8. wrote this message.
 
Solution
Boogieman_WD
Wow, that's a whole new level of troubleshooting. Didn't expect you to go that far and understandably it's not something that I'd ever recommend. However I'm pretty impressed with what you've achieved. Just keep a closer eye on the drives you're using with that enclosure from now on. Hopefully it doesn't mess up a partition or file system somehow.
As for the WD software you're talking about, I guess if it's one of the programs which need to recognize a WD drive in order to work, then that ship has probably sailed, unless you connect the WD Blue drive internally so that it's recognized properly. :(

Oh, I almost forgot, nice disclaimer! :)
Sort by date Sort by votes
Boogieman_WD

Boogieman_WD

Judicious
Jul 31, 2014
6,050
2
35,960
Hey there, assembled.

Well, I don't have a lot to offer in this situation, besides trying out a low level format, while the drive is in the external enclosure (but not before you've backed up any important data which you might have on that WD Blue HDD). Hopefully this allows the computer to recognized the full capacity of the drive.
Here's how to do it via DLG (Data Lifeguard): How to low level format or write zeros (full erase) to a WD hard drive or Solid State drive

Anyway, as you probably know, taking a drive out of its original enclosure voids its warranty. It's even miraculous to some extend that you were able to do whatever "magic" you've done to use properly a different drive with that enclosure, so even if you don't succeed this time, you'd still have had your good fortune.

If you happen to remember what you did back then, I'd be really interested to find out what it was.

Hope that helps. Please let me know how it goes.
Boogieman_WD
 
Upvote 0 Downvote
A

assembled

Honorable
Aug 8, 2013
23
0
10,510
Ok, few more hours in to this and now I know that any HDD I plug shows the same 233GB (250 Gb). I managed to find my old downloads with all the WD software of that time (same as today, only older), but there is nothing special about it...
I also tried "forgetting" password hoping that it will cause full controller reset. It didn't. Formatting also does not help as controller says it is a 233GB no matter what.
I'll try to shove something under that to see how it will react while trying to write something outside actual HDD size. Because that was exactly the problem I solved then. Just have to find something sata and under 250 Gb and without anything valuable inside.

I could go full EE and try to find a working dump to shove in to it just to see what happens, but I am still curious what is going on here. Maybe I should compare my dump with that to see what exactly is different besides encryption key.

Onboard controller JMS558S, eeprom Pm25LD020
 
Upvote 0 Downvote
A

assembled

Honorable
Aug 8, 2013
23
0
10,510
I did it. Shorting HOLD# pin (pin 7) of eeprom (U2) to ground while powering up caused controller board to loose any memory of being WD controller. I don't know whether I completely destroyed eeprom or simply the bridge IC decided to ignore what ever is inside after my invasion, but now it is recognized as a USB to ATA/ATAPI Bridge. It also works with any drive I have on my table not discriminating them by manufacturer nor size. AND the best part (at least for me) is that it does not encrypt any more. That's right folks, now if the bridge fails (electronics tend to to that) it will be possible to simply put the HDD internally or replace it into another enclose. Of course WD software now refuses to even talk to this equipment, but I can live with that.

Disclaimer: if someone will follow this, be warned that by doing anything to your equipment you are responsible for the end result. If your attempt to do the same and will destroy your equipment or ruin your data, you are on your own.


Oh, I forgot to mention that now I have no way of knowing what software/firmware changes caused the issue at the first place. Anyway I am pleased to know that WD representatives keep an eye on this forum and react even to topics like this one. Thank you.
 
Upvote 0 Downvote
Boogieman_WD

Boogieman_WD

Judicious
Jul 31, 2014
6,050
2
35,960
Wow, that's a whole new level of troubleshooting. Didn't expect you to go that far and understandably it's not something that I'd ever recommend. However I'm pretty impressed with what you've achieved. Just keep a closer eye on the drives you're using with that enclosure from now on. Hopefully it doesn't mess up a partition or file system somehow.
As for the WD software you're talking about, I guess if it's one of the programs which need to recognize a WD drive in order to work, then that ship has probably sailed, unless you connect the WD Blue drive internally so that it's recognized properly. :(

Oh, I almost forgot, nice disclaimer! :)
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom