PCB 0J35276 BA5145B for WD80EZZX-11CSGA0

[fzabkar]

I wonder if the WWN of the My Book device shows up in USBDeview?

[michael chiklis]

I wonder if the WWN of the My Book device shows up in USBDeview?

[michael chiklis]

Later i will modify s/n and capacity on module 02 of my WD 500GB test drive and see what happens on controller rom.

[fzabkar]

Later i will modify s/n and capacity on module 02 of my WD 500GB test drive and see what happens on controller rom.

I think your test drive is one that is affected by WD's "IntelliPower" nonsense, so I suspect it will report an RPM of 0.

[michael chiklis]

I did those changes on mod 02 of my 500 GB test drive, but somehow the modification of the capacity (LBA) is not saved properly.
The 8 TB drive has 15628053168 LBAs, once i insert this value on edit ID in MRT, when i repower the drive and go again inside utility it shows me 2743151280 LBA.
Why this number?

I did it with MRT but it's now a bug of the tool, i get the same number also when i do the same changes with WD Marvel.

[fzabkar]

Your 500GB test drive ignores LBA bits 32 - 47.

Code:

  15628053168 = 0x3A3812AB0
   2743151280 = 0x A3812AB0

[michael chiklis]

Frank,
i've found another WD drive for testing, this is a 3 TB drive (Dragon family), model WD30EZRX-00MMMB0.
I edited mod 02, this drive writes properly those LBA bits relative to the capacity changing.

After i've changed capacity, s/n and fw version id of this 3 TB drive, i attached it to the 8 TB MyBook controller, then i unplugged, and finally i've attached the 8 TB drive to the controller.
Unfortunately i still can't access to user data, but it gets loaded into disk management (partition still not).

I also dumped again the controller rom, i compared 1st and 2nd parts.

Here you can download the rom code:

MyBook controller eprom after i attached to hdd WD30EZRX-00MMMB0.rar

(35.08 KiB) Downloaded 895 times

This is what i see in R-studio:

R-Studio shows all E5 pattern, from first to last lba.

This is what Victoria shows

and USBdeview

Last edited by michael chiklis on June 9th, 2019, 19:54, edited 1 time in total.

[fzabkar]

Your 3TB drive is one that is affected by WD's "IntelliPower" BS. Therefore it reports an RPM of 0. You need a drive that reports 5400 RPM. That's the only other thing I can think of.

[michael chiklis]

ok, i will search for 5400 RPM drive, or i will just buy a similar controller on ebay.
Thank you.

[fzabkar]

One other difference is that you have right justified the serial number (and padded it with leading spaces). Instead you should have left justified it and padded it with trailing spaces.

Your S/N changes:

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

0000F080              20 20 20 20 20 20 20 20 20 20 20 20                 
0000F090  56 4B 4A 34 44 4D 33 58                          VKJ4DM3X

Original Identify Device serial number (byte reversed):

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

0001F010              4B 56 34 4A 4D 44 58 33 20 20 20 20      KV4JMDX3   
0001F020  20 20 20 20 20 20 20 20                                 

[fzabkar]

ok, i will search for 5400 RPM drive, or i will just buy a similar controller on ebay.

I don't think another controller will help you other than to show us what a functional EEPROM looks like.

AISI, we need to rebuild one small data section, but we can't do it by hand because we don't know how to calculate the checksum(s). Instead we need to "impersonate" the original drive and trick the bridge into rebuilding the data block for us.

Maybe someone could work out the checksum algorithm?

[fzabkar]

I have another idea.

What if we take a Seagate PCB and modify the "dummy" Identify Device data that are reported by the ROM when the HDA is inaccessible?

For example, here are the ID data in a CC45 ST2000DL003 ROM:

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00019DF0  37 C8 10 00 00 00 00 00 3F 00 00 00 00 00 00 00  7È......?.......
00019E00  20 20 20 20 20 20 20 20 20 20 20 20 4E 51 5F 52              NQ_R
00019E10  46 42 20 57 00 00 00 10 04 00 2E 2E 31 30 20 20  FB W........10 
00019E20  20 20 54 53 4D 5F 33 31 51 46 4C 42 20 20 20 20    TSM_31QFLB   
00019E30  20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20                 
00019E40  20 20 20 20 20 20 20 20 20 20 10 80 00 00 00 2F            .€.../
00019E50  00 40 00 02 00 02 07 00 FF 3F 10 00 3F 00 10 FC  .@......ÿ?..?..ü
00019E60  FB 00 10 01 5E 71 7B 00 00 00 07 00 03 00 78 00  û...^q{.......x.
00019E70  78 00 F0 00 78 00 00 00 00 00 00 00 00 00 00 00  x.ð.x...........
00019E80  00 00 1F 00 02 01 00 00 00 00 00 00 7E 00 1B 00  ............~...
00019E90  6B 34 01 7D 03 40 69 34 01 3C 03 40 7F 40 00 00  k4.}.@i4.<.@.@..
00019EA0  00 00 FE FE FE FF 00 00 00 FE 00 00 00 00 00 00  ..þþþÿ...þ......
00019EB0  00 00 00 00 5E 71 7B 00 00 00 00 00 00 00 00 00  ....^q{.........
00019EC0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00019ED0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00019EE0  00 00 00 00 00 00 00 00 00 00 00 00 01 00 5E 71  ..............^q
00019EF0  7B 00 5E 71 7B 00 20 20 02 00 B6 42 00 01 8A 00  {.^q{.  ..¶B..Š.
00019F00  06 3C 0A 3C 00 00 C6 07 00 01 00 08 78 0F 00 05  .<.<..Æ.....x...
00019F10  02 00 80 02 00 00 00 00 08 00 02 00 00 00 03 FE  ..€............þ
00019F20  50 00 00 00 00 00 00 00 A9 00 0B 00 00 00 00 00  P.......©.......
00019F30  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00019F40  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00019F50  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00019F60  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00019F70  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00019F80  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00019F90  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00019FA0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00019FB0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00019FC0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00019FD0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00019FE0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

We could replace these data with your HGST Identify Device data block, recompute Seagate's CRC16, and rewrite the ROM on your Seagate PCB. If we then use the Seagate PCB on its own, or on a drive where the HDA has been isolated, then perhaps the bridge will rebuild the damaged data area in the EEPROM using the "dummy" ID.

[fzabkar]

What if we take a Seagate PCB and modify the "dummy" Identify Device data that are reported by the ROM when the HDA is inaccessible?

It won't work. The firmware version is changed by the drive. :-(

[NicDaniel]

Hi. i have a silimar problem as topic starter.
connected HGST HUH728080ALE604 with wrong PSU extension cable (+5v and GND was swapped). Now it is completely silent, but no visible damage on the PCB (if i swap PCB from same working drive - it starts spinning). Can you guide me what can i check on the PCB ?

BTW i ordred this PCB from the same Ebay seller as TS. he did not sent me my order and cancelled it after 3 weeks or so.

[fzabkar]

Check the 5V TVS diode, Schottky rectifier (marking "74") and fuse.

https://forum.hddguru.com/viewtopic.php?f=1&t=38523

[NicDaniel]

Check the 5V TVS diode, Schottky rectifier (marking "74") and fuse.

https://forum.hddguru.com/viewtopic.php?f=1&t=38523

Thanks. 5v fuse, 5v TVS diode and "74" Schottky were fried

[NicDaniel]

Does anybody know parameters of fuse, 5v TVS and "74" Schottky ? i can't find donor PCB

[fzabkar]

The TVS diode and Schottky rectifier don't need to be replaced -- just remove them. You may only need to remove the TVS diode for the short to go away. As for the fuse, a 2A smt fuse should be OK.

[shubhsinghal]

Hello Everyone,

I have received one similar case few days back and trying to find a solution for it.

Model: WD80EFZX-68VW8N0
P/N: 2W10102
PCB: 006-0A90439

Drive spinning good and gets ready in a while, but when i try to access the sectors it goes to busy state.


Not able to detect the family.

Any Suggestions?

Thank you

[fzabkar]

Not able to detect the family.

This is a new HGST firmware architecture. It has not yet been reverse engineered, AFAIK.