Seagate Preamp Pulled From ROM (Requests)

Don't Lose Your Data Forever!

DIY data recovery has risks. You could lose your data forever! Don't want to risk it? Talk to a professional now.

Dejiko

New member
Thanks, Michael! Now that I know what to look for, I can see those values at 0x18E7C in the respective files. I'd been worried because the terminal was reporting 57 61 for the preamp of "EKLC" (see below) but I wasn't finding those values in the ROM anywhere.

In other news, the "8YVQ" drive was making a faint whining noise starting July 04, and by the morning of July 05 it was a loud grinding. When I power-cycled it, it is now giving its own "11 clicks of death" with intermittent grinding and can't be seen by the system. So now that drive is dead as well. That's okay, I'd copied its data elsewhere.

On July 07, I was able to get my terminal adapter working to talk to these drives. Well, the one working drive, anyway:

[pre]F3 T>
Hepburn VTPI/RAP16,128K dfcts,9K srvo,Yeti3,5900rpm DT
Product FamilyId: 40, MemberId: 01
HDA SN: 5XW1EKLC, RPM: 5893, Wedges: 160, Heads: 8, Lbas: E8FE5790, [highlight=yellow]PreampType: 57 61[/highlight]
PCBA SN: 0000E107DLKQ, Controller: YETIST_3_0(649B)(3-12-3-3), Channel: AGERE_COPPERHEAD_LITE, PowerAsic: MCKINLEY DESKTOP LITE Rev 13, BufferBytes: 2000000
Package Version: HE1DDB.CCD3.DK0H2H.CC34 , Package P/N: 100615302, Package Builder ID: AT,
Package Build Date: 02/12/2010, Package Build Time: 17:10:46, Package CFW Version: HE1D.CCD3.00237547.AT00,
Package SFW1 Version: BD6C, Package SFW2 Version: ----, Package SFW3 Version: ----, Package SFW4 Version: ----
Controller FW Rev: 02121710, CustomerRel: CC34, Changelist: 00237547, ProdType: HE1D.CCD3, Date: 02/12/2010, Time: 171046, UserId: 00236537
Servo FW Rev: BD6C
RAP FW Implementation Key: 10, Format Rev: 0001, Contents Rev: A2 06 03 03
Features:
- Quadradic Equation AFH enabled
- VBAR with adjustable zone boundaries enabled
- Volume Based Sparing enabled
- IOEDC enabled
- IOECC enabled
- DERP Read Retries enabled
- LTTC-UDR2 compiled off[/pre]

But the two drives giving "11 clicks of death" are not responding to the terminal at all.

Currently my list of things to try includes
-Running Seagate's diagnostics (probably won't detect the drive)
-Running MHDD (probably won't detect the drive)
-Try swapping the "EKLC" PCB to my failed drive (probably will still give 11 clicks of death)
-Copy the BIOS from failed drive to the "EKLC" PCB, try with that (probably will still give 11 clicks of death)

After that the next step will be to build a DIY laminar-flow hood to minimize dust contamination, and then practice removing and re-installing the head assembly on the "8YVQ" drive now that it's completely failed. I also have some other old drives I can practice working on, although they won't be the same design; they're mostly 160GB and smaller.

At that point, if I'm feeling confident enough, I can try to swap the "EKLC" heads into my failed drive, and hope that it is revived long enough to transfer my files off of it.
 

Jared

Administrator
Staff member
Dejiko":1zznjp58 said:
[post]16358[/post] -Running Seagate's diagnostics (probably won't detect the drive)
-Running MHDD (probably won't detect the drive)
-Try swapping the "EKLC" PCB to my failed drive (probably will still give 11 clicks of death)

I wouldn't attempt any of this. The only thing this will possibly do is make the situation worse.

Dejiko":1zznjp58 said:
[post]16358[/post] -Copy the BIOS from failed drive to the "EKLC" PCB, try with that (probably will still give 11 clicks of death)
It's not a BIOS, it's technically an EEPROM chip which is commonly just called the ROM chip in this field. You can certainly try moving the ROM or it's code to another board, but I can almost promise you the board is not the problem here. Beyond checking the contacts for obvious corrosion, I never even bother trying a replacement PCB on these before replacing heads. It's not worth the risk of additional power-ups of the drive with potentially damaged read/write heads.

Dejiko":1zznjp58 said:
[post]16358[/post] At that point, if I'm feeling confident enough, I can try to swap the "EKLC" heads into my failed drive,
Before you do that. Practice taking the heads out of the donor and re-installing them into the donor and see if it still works. Only after you've mastered your technique should you try this on a drive that has actual data needing recovery.
 

scottz

New member
I'm interested in making sure the preamps match in these attached patient/donor firmwares. Also after if the head mappings are the same.

Thanks.
 

Attachments

  • Patient-Donor-ST3000DM001.zip
    1.1 MB · Views: 62

otako

New member
scottz":16ohnw7u said:
I'm interested in making sure the preamps match in these attached patient/donor firmwares. Also after if the head mappings are the same.

Thanks.
Both ROM have B7 04 and same head map.
 

Jared

Administrator
Staff member
In case you didn't notice. PC-3000 has now automated this when you press this button:
01.png

And you can see your preamp here:
02.png

That's not your ROM, just an example from some random Grenada. Just reverse the two pairs, so you know this one is a CC 06 preamp.
 
Hello,

Any chance you could take a quick look in this ROM. The "82 02" and "C2 02" donor I have used cannot write to the SA suggesting a mismatch.

From:
Model : ST1000LM035-1RK172
Serial : WL15364S
Firmware : ACM2

Best regards,
John
 

Attachments

  • ROM_WL15364S_ED58D7F9.bin
    1 MB · Views: 7

Jared

Administrator
Staff member
I don't have a sure way to read preamp from Rosewood ROMs directly. Most often, the issue of being able to read but not write SA is resolved by getting a donor with a closer manufacture date.
 
Top