Seagate Preamp Pulled From ROM (Requests)
- Thread starter Jared
- Start date
drmoast":2evdhoko said:
That looks like it's a Rosewood ROM and we don't have a method to read out the preamp on those ROMs yet. Not a reliable one anyway. Besides, the preamp rarely matters wth those. It's more important that you're in the correct family (e.g _A5 _8C _AF) and have correct head map than anything else.
sheepwildman
New member
Is it possible to get the preamp version without the rom?
Only have this:
SN: W2F0KK2Z
ST2000DM001
PN: 9YN164-500
FW: CC4B
DATE: 13133
Only have this:
SN: W2F0KK2Z
ST2000DM001
PN: 9YN164-500
FW: CC4B
DATE: 13133
TLDR: Please ID the preamps in these three ROMs. Thank you!
Long version:
I want to recover the data from the disk with serial ending in "CPC2", date code 11093, board revision "A". The drive was working perfectly fine until one day when it was supposed to spin up from standby it started giving "11 clicks of death" and can no longer be detected. I've tried swapping in another PCB and it does the same thing. I'm working to build a serial cable to see what the diagnostics interface will tell me.
The drive with serial ending is "EKLC", date code 11103, board revision "A" is a drive which I picked up second-hand as a source for parts (PCB, heads, etc.). It appears to be working 100% correctly and has no data on it.
The drive with serial ending in "8YVQ", date code 11242, board revision "B" is a pull from a Fantom-brand external drive, and it is detected as a Fantom-brand drive even when plugged into an internal SATA port. This drive is operating, but S.M.A.R.T. is predicting imminent failure (5 Reallocated sectors, 3993 bad sectors, 1 weak sector). I've copied the data from this drive, so I can use it for parts.
All three drives are Seagate ST32000542AS Barracuda LP 2TB with firmware CC34, site code WU.
I'm hoping to find a fix without having to open the drive, but from what I've been reading, a head swap is likely to be required, as the drive is spinning up and down correctly. I've never done that before, so I'd likely try removing and reinstalling the heads on the "8YVQ" drive a few times for practice, making sure that it functions acceptably when I put it back together. If that works well, I can try moving the good heads from the "EKLC" drive to the "CPC2" drive I want to fix. Hopefully with the similar date codes, both "EKLC" and "CPC2" will have matching preamps.
If you have any suggestions, please let me know. Thank you! I am enjoying reading the discussions on this forum.
Long version:
I want to recover the data from the disk with serial ending in "CPC2", date code 11093, board revision "A". The drive was working perfectly fine until one day when it was supposed to spin up from standby it started giving "11 clicks of death" and can no longer be detected. I've tried swapping in another PCB and it does the same thing. I'm working to build a serial cable to see what the diagnostics interface will tell me.
The drive with serial ending is "EKLC", date code 11103, board revision "A" is a drive which I picked up second-hand as a source for parts (PCB, heads, etc.). It appears to be working 100% correctly and has no data on it.
The drive with serial ending in "8YVQ", date code 11242, board revision "B" is a pull from a Fantom-brand external drive, and it is detected as a Fantom-brand drive even when plugged into an internal SATA port. This drive is operating, but S.M.A.R.T. is predicting imminent failure (5 Reallocated sectors, 3993 bad sectors, 1 weak sector). I've copied the data from this drive, so I can use it for parts.
All three drives are Seagate ST32000542AS Barracuda LP 2TB with firmware CC34, site code WU.
I'm hoping to find a fix without having to open the drive, but from what I've been reading, a head swap is likely to be required, as the drive is spinning up and down correctly. I've never done that before, so I'd likely try removing and reinstalling the heads on the "8YVQ" drive a few times for practice, making sure that it functions acceptably when I put it back together. If that works well, I can try moving the good heads from the "EKLC" drive to the "CPC2" drive I want to fix. Hopefully with the similar date codes, both "EKLC" and "CPC2" will have matching preamps.
If you have any suggestions, please let me know. Thank you! I am enjoying reading the discussions on this forum.
michael chiklis
Member
5XW28YVQ: 72 03
5XW1EKLC: 57 01
5XW1CPC2: 57 01
5XW1EKLC: 57 01
5XW1CPC2: 57 01
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.
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.
Dejiko":1zznjp58 said:
I wouldn't attempt any of this. The only thing this will possibly do is make the situation worse.
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:
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.Dejiko":1zznjp58 said: