All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 17 posts ] 
Author Message
 Post subject: Preamp Vendor & Preamp Revision
PostPosted: November 19th, 2017, 0:29 
Offline

Joined: November 18th, 2017, 2:50
Posts: 8
Location: Los Angeles
Can anyone tell me the easiest way to get Preamp Vendor and Preamp Revision information from a WD hard drive w/ MRTLAB? I have been searching online and come up with absolutely nothing. I'm trying to list this info with donor drives, but finding it difficult.

Thanks in advance


Top
 Profile  
 
 Post subject: Re: Preamp Vendor & Preamp Revision
PostPosted: November 19th, 2017, 12:40 
Offline
User avatar

Joined: April 3rd, 2011, 0:19
Posts: 2003
Location: Providence, RI
It's two clicks with PC-3000 (if the drive is able to ID), but I have no idea if you can check it in MRT easily.

_________________
Data Medics - Hard Drive, SSD, and RAID Data Recovery Service Company


Top
 Profile  
 
 Post subject: Re: Preamp Vendor & Preamp Revision
PostPosted: November 19th, 2017, 13:42 
Offline

Joined: November 18th, 2017, 2:50
Posts: 8
Location: Los Angeles
Yeah, it's sad times over here. I imagine it's just part of a module, right? But which one?


Top
 Profile  
 
 Post subject: Re: Preamp Vendor & Preamp Revision
PostPosted: November 19th, 2017, 14:55 
Offline
User avatar

Joined: April 3rd, 2011, 0:19
Posts: 2003
Location: Providence, RI
Yeah, that I don't know. I've often wished that Ace would go public with where PC3K is pulling the info from, since the utility can only read it if the drive actually IDs. Would be really nice to know how to extract this from the SA.

_________________
Data Medics - Hard Drive, SSD, and RAID Data Recovery Service Company


Top
 Profile  
 
 Post subject: Re: Preamp Vendor & Preamp Revision
PostPosted: November 21st, 2017, 16:40 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15440
Location: Australia
data-medics wrote:
Yeah, that I don't know. I've often wished that Ace would go public with where PC3K is pulling the info from, since the utility can only read it if the drive actually IDs. Would be really nice to know how to extract this from the SA.

You can get the same info with an MHDD script:

Code:
; Reads Drive Physical Parameters for WD Marvell
;
reset
waitnbsy
regs = $45 $0b $00 $44 $57 $a0 $80
waitnbsy

regs = $d6 $01 $be $4f $c2 $a0 $b0
waitnbsy
checkdrq
sectorsfrom = DrvTbl.bin

regs = $d5 $01 $bf $4f $c2 $a0 $b0
waitnbsy
checkdrq
sectorsto = DrvTbl01.bin

; end

;DrvTbl.bin -- 0D 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00

Code:
Offset(d) 00   02   04   06   08   10   12   14

00000000  0200 3230 2E41 304D 0000 3030 2E39 3200  ..20.A0M..00.92.
00000016  0000 3230 2E41 304D 0000 7612 0306 063F  ..20.A0M..v....?
00000032  0015 B400 4000 2F1C E047 0100 1432 4405  ..´.@./.àG...2D.
00000048  0001 0000 017D 0000 017D 0600 2000 0100  .....}...}.. ...
                              preamp vendor  ^^^^

00000064  0400 0000 0000 0116 2B00 320A 0001 4432  ........+.2...D2
          ^^^^ preamp version

00000080  2E30 3044 0000 3030 2E32 3141 2020 0000  .00D..00.21A  ..
00000096  0000 0000 0000 0000 0000 0000 0000 0000  ................
00000112  0000 0000 0000 0400 0000 0000 0000 FC02  ..............ü.
00000128  0000 0000 1334 4B1D 5500 4603 0000 E903  .....4K.U.F...é.
00000144  0200 0000 0000 0000 0000 0000 1100 2200  ..............".
00000160  0400 0000 0801 1000 0000 C409 F401 0000  ..........Ä.ô...
00000176  0000 0000 0000 0000 0000 0000 0000 0000  ................
00000192  0000 0000 0000 0000 0000 0000 0000 0000  ................
00000208  0000 0000 0000 0000 0000 0000 0000 0000  ................
00000224  0000 0000 0000 0000 0000 0000 0000 0000  ................
00000240  0000 0000 0000 0000 0000 0000 0000 0000  ................
00000256  5347 4241 4C4D 5044 4D38 4855 4357 5254  SGBALMPDM8HUCWRT
00000272  5644 4B4B 5546 0020 2020 2020 2020 2020  VDKKUF.         
00000288  2020 2020 3035 2D32 392D 3230 3036 0000      05-29-2006..
00000304  0000 0000 0000 0000 0000 0000 0000 0000  ................
........
00000496  0000 0000 0000 0000 0000 0000 0000 0000  ................

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: Preamp Vendor & Preamp Revision
PostPosted: November 21st, 2017, 18:03 
Offline
User avatar

Joined: April 3rd, 2011, 0:19
Posts: 2003
Location: Providence, RI
Any idea which module that's in? I've never played with MHDD that much using custom scripts, but I assume that usually requires a semi-functional drive to pull the info.

Looks like module 02, but hoping to be sure...

I'd love to build a quick python script to pull it from a module backed up by PC3K.

_________________
Data Medics - Hard Drive, SSD, and RAID Data Recovery Service Company


Top
 Profile  
 
 Post subject: Re: Preamp Vendor & Preamp Revision
PostPosted: November 21st, 2017, 18:34 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15440
Location: Australia
I couldn't find any "2006" string in my SA dump, except for module 02.

I suspect that the "drive table" is assembled on-the-fly, much like the Identify Device data block. Many (all?) of the code modules in the ROM appear to be compressed, so perhaps that's where the version numbers come from. I suspect that the MCU/Channel/Preamp/Power Controller IDs are obtained by reading the peripheral registers.

You might like to scan your drive's manufacturing logs.

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: Preamp Vendor & Preamp Revision
PostPosted: November 21st, 2017, 18:45 
Offline
User avatar

Joined: April 3rd, 2011, 0:19
Posts: 2003
Location: Providence, RI
Yeah, that makes sense. I know in the past I've tried searching through various modules (including 02 where it'd make sense to be) hoping to find the preamp vendor/rev in hex, but I've never been able to find it in any consistent location in any module.

Compression would explain why it sometimes seems like I can find a preamp version in there (by comparing what PC-3000 actually reads from working drive) but sometimes it's not there at all.

_________________
Data Medics - Hard Drive, SSD, and RAID Data Recovery Service Company


Top
 Profile  
 
 Post subject: Re: Preamp Vendor & Preamp Revision
PostPosted: November 21st, 2017, 19:04 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15440
Location: Australia
You could edit specific text strings in module 02 (eg DCM, DOM) and then see whether these changes appear in the drive table.

Another test might be to see whether the drive table reflects the donor's preamp ID or the patient's, if you are ever successful with a dissimilar headswap.

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: Preamp Vendor & Preamp Revision
PostPosted: November 21st, 2017, 20:21 
Offline
User avatar

Joined: April 3rd, 2011, 0:19
Posts: 2003
Location: Providence, RI
Actually, I was thinking more along the lines of writing module 02 from a different preamp drive to a working drive and see how it reads out then. That'd at least confirm if the value is, in fact, being read from that module.

If that works, then it means you could at least transfer the module to a working same model/family drive and check it before doing a head swap.

_________________
Data Medics - Hard Drive, SSD, and RAID Data Recovery Service Company


Top
 Profile  
 
 Post subject: Re: Preamp Vendor & Preamp Revision
PostPosted: November 21st, 2017, 21:22 
Offline

Joined: September 29th, 2005, 4:10
Posts: 402
Location: Moscow
No Preamp Vendor & Preamp Revision in the modules.
Only in RAM
Get chips poll.

RAM table CP=0D id=01.


Top
 Profile  
 
 Post subject: Re: Preamp Vendor & Preamp Revision
PostPosted: November 23rd, 2017, 4:59 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15440
Location: Australia
It should be possible to write a script to extract the DCM codes and head/media/preamp IDs from modules 02 and C5. I have worked out part of the structure of C5 in the following thread.

Head Stack Replacement: Questions and Answers:
http://www.hddoracle.com/viewtopic.php?f=78&t=198&p=14976

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: Preamp Vendor & Preamp Revision
PostPosted: November 24th, 2017, 2:22 
Offline

Joined: November 18th, 2017, 2:50
Posts: 8
Location: Los Angeles
Wow. Your work on this is really impressive. I'm looking at this from a complete beginner, but I'm trying to figure out how you figured out the groups, bytes, records 'rosetta stone'... nicely done.

For me, I'm just trying to get a hold of hex in general. Aside from editing executables two decades ago to put my own name in games like leisure suit larry and things, I have zero experience. Approaching it from a more useful angle today. It looks quite difficult, but I think once I spend enough time with this I'll get the hang of it. It's intimidating at the moment, though.

Thanks for your answers and the script.


Top
 Profile  
 
 Post subject: Re: Preamp Vendor & Preamp Revision
PostPosted: November 24th, 2017, 4:00 
Offline

Joined: November 18th, 2017, 2:50
Posts: 8
Location: Los Angeles
fzabkar wrote:
It should be possible to write a script to extract the DCM codes and head/media/preamp IDs from modules 02 and C5. I have worked out part of the structure of C5 in the following thread.

Head Stack Replacement: Questions and Answers:
http://www.hddoracle.com/viewtopic.php?f=78&t=198&p=14976


I tried following along to your C5 tutorial with a Pinclite drive (WD2500AAJS-60Z0A0). The Head DCM and Media Codes are very straight forward, as there is nothing to decode. However, I'm unable to locate any of the other record IDs.

Can you tell me if I'm still hex illiterate or is this just a case where C5 doesn't contain these items in that format?

Thanks!


Attachments:
File comment: C5
C5.7z [1.65 KiB]
Downloaded 523 times
Top
 Profile  
 
 Post subject: Re: Preamp Vendor & Preamp Revision
PostPosted: November 24th, 2017, 4:06 
Offline

Joined: November 18th, 2017, 2:50
Posts: 8
Location: Los Angeles
Tomset wrote:
No Preamp Vendor & Preamp Revision in the modules.
Only in RAM
Get chips poll.

RAM table CP=0D id=01.


Can you elaborate? I have no idea what this means.


Top
 Profile  
 
 Post subject: Re: Preamp Vendor & Preamp Revision
PostPosted: November 24th, 2017, 15:07 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15440
Location: Australia
There appear to be several formats for the C5 module. In your example all I could find was ...

Code:
+--- Head DCM Codes -------- Media DCM Codes -----+   
|                       |                         |   
|  WDB:    7            |  SHOWA: F               |   
|  SAE:    D            |  KOMAG: K               |   
|                       |  WDMO_2M2: W            |   
|                       |                         |   
|                       |                         |   
+-------------------------------------------------+   

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: Preamp Vendor & Preamp Revision
PostPosted: November 24th, 2017, 17:13 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15440
Location: Australia
meanaverage wrote:
Tomset wrote:
No Preamp Vendor & Preamp Revision in the modules.
Only in RAM
Get chips poll.

RAM table CP=0D id=01.


Can you elaborate? I have no idea what this means.

AISI, it's doing the same thing as my MHDD script. My script reads SMART log BFh after executing a SMART WRITE LOG BEh command with Action Code 0Dh and Function Code 01h.

http://yura.puslapiai.lt/files/wd/mhdd/index.html

_________________
A backup a day keeps DR away.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 17 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 7 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group