ST2000LM007 – BSY after head swap, Janus vs CheopsLite

[Josh256]

Hi everyone,

I have a Seagate ST2000LM007 that stays BSY and cannot be identified.
I attempted a head swap with a donor ST2000LM007, but the drive still does not come ready. In MRT terminal I get repeated servo recovery / FAIL Servo Op errors during startup.
To rule out damaged heads, I moved the donor heads back from the patient into the donor, and the donor works normally and identifies correctly., so the heads appear to be OK. I also checked under the microscope, and the head pattern looks identical/similar between the two drives.
In MRT I also noticed that the firmware family is different between the two drives:

Patient shows AF – Janus
Donor shows A5 – CheopsLite

Does this behaviour point to a head compatibility / family mismatch issue, or could it still be surface / SA damage, or something else?

Patient:
Model: ST2000LM007
SN: WDZLCL7D
PN: 1R874-570
FW: EB01
Site: WU
Date: 05 MAY 2019

Donor:
Model: ST2000LM007
SN: WDZ83GPD
PN: 1R8174-568
FW: SBK2
Site: WU
Date: 15 AUG 2017

Any opinions are appreciated.

Attachments

[skinbob]

If the donor head still work in the donor its more than likely they are not a match.

Looking on DonorDrives reveals a close match.....

HDD with Serial Number: WDZMCSJ4
Model: ST2000LM007
Part Number: 1R8174-189
Date Code: 29 JUL 2019 -
Site Code: WU

Heads map: 00 01 02 03
PreampType: 82

Does your donor drive have the same preamp as above?

[Josh256]

If the donor head still work in the donor its more than likely they are not a match.

Looking on DonorDrives reveals a close match.....

HDD with Serial Number: WDZMCSJ4
Model: ST2000LM007
Part Number: 1R8174-189
Date Code: 29 JUL 2019 -
Site Code: WU

Heads map: 00 01 02 03
PreampType: 82

Does your donor drive have the same preamp as above?

Thanks for the info. I checked the donor in MRT terminal.
The donor I tried is Family A5 (CheopsLiteM) with PreampType C2 12, so clearly not a match?
I have another donor which is Family 8C (CheopsAM) with PreampType 82 12,

Second Donor:
Model: ST2000LM007
SN: WCC1NTL5
Part Number: 1R8174-568
FW:SBK2
Site Code: WU
Date Code: 16 JUL 2016 -
Heads map: 00 01 02 03
PreampType: 82

but the family still differs from the patient (AF – Janus). Do you think it would be compatible? or is a strict (AF–Janus) family match required?
If a strict family match is required, how do you recommend finding a compatible donor based only on label information?
Most online guidance suggests matching the model number and the first three characters of the serial number, but in this case that approach clearly does not work.

[michael chiklis]

If the donor head still work in the donor its more than likely they are not a match.

Looking on DonorDrives reveals a close match.....

HDD with Serial Number: WDZMCSJ4
Model: ST2000LM007
Part Number: 1R8174-189
Date Code: 29 JUL 2019 -
Site Code: WU

Heads map: 00 01 02 03
PreampType: 82

Does your donor drive have the same preamp as above?

Thanks for the info. I checked the donor in MRT terminal.
The donor I tried is Family A5 (CheopsLiteM) with PreampType C2 12, so clearly not a match?
I have another donor which is Family 8C (CheopsAM) with PreampType 82 12,

Second Donor:
Model: ST2000LM007
SN: WCC1NTL5
Part Number: 1R8174-568
FW:SBK2
Site Code: WU
Date Code: 16 JUL 2016 -
Heads map: 00 01 02 03
PreampType: 82

but the family still differs from the patient (AF – Janus). Do you think it would be compatible? or is a strict (AF–Janus) family match required?
If a strict family match is required, how do you recommend finding a compatible donor based only on label information?
Most online guidance suggests matching the model number and the first three characters of the serial number, but in this case that approach clearly does not work.

I found this info from Jared's forum
https://www.data-medics.com/forum/threa ... post-15713

"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."

[skinbob]

I find the family does not need to match, just the preamp. However the last post you quoted is right, there is no way to read the preamp from ROM on rosewood drives.

I usually just look up the closest and then match the preamps best I can.

This might help too.....

https://www.recoveryforce.com/forums/vi ... .php?t=537

[laptokowiec]

I hate these drives.

[pepe]

a full log would be helpful instead of that screenshot.
If the drive loads DiscFw on its own, i guess SA is corrupted severely due to write problems.
Other cause may be non-native pcb but we need to see full log to determine that. Especially if that log was taken using virtual start.
pepe

[Josh256]

a full log would be helpful instead of that screenshot.
If the drive loads DiscFw on its own, i guess SA is corrupted severely due to write problems.
Other cause may be non-native pcb but we need to see full log to determine that. Especially if that log was taken using virtual start.
pepe

Thanks everyone for your replies. I bought a third donor and just swapped heads.

Donor details:

Model: ST2000LM007
SN: WDZNKPAK
PN: 1R874-570
FW: EB01
Site: WU
Date: 05 NOV 2019

The patient drive can now identify, and in DE I can see all client data and files.

However, in the MRT terminal, I still get repeated RECOV Servo / EMCDataErr messages during startup. It seems that system files and SA modules cannot be fully loaded, which prevents me from creating a head map.

Should I proceed with imaging, or is there a way to fix this issue?

Terminal:

Starting LBA of RW Request=000B188829 Length=00000414
ProcessRWError -Read- at LBA 000B188829 Sense Code=43160080ProcessRC: 00000001,00000000ReadContinuous: 0B188829,0000015CUnrecovSectorCount:015C,015B,015CNumUDEs: 0000015C,00000000,0000015BPassed: 00000080,00000116,00000139Out:
PrgFSkipLBA: 0B188829,0B188984
Starting LBA of RW Request=000B188829 Length=00000414
ProcessRWError -Read- at LBA 000B188985 Sense Code=43160080ProcessRC: 00000001,00000000ReadContinuous: 0B188985,0000015CUnrecovSectorCount:015C,015B,015CNumUDEs: 0000015C,00000000,0000015BPassed: 00000080,00000116,00000139Out:
PrgFSkipLBA: 0B188985,0B188AE0
RECOV Servo Op=0295 Resp=0005
RECOV Servo Op=0095 Resp=0005
RECOV Servo Op=02A5 Resp=0005
RECOV Servo Op=03A5 Resp=0005
Starting LBA of RW Request=000B1891AD Length=00001DE8
ProcessRWError -Read- at LBA 000B1891AD Sense Code=43160080ProcessRC: 00000001,00000000ReadContinuous: 0B1891AD,0000015CUnrecovSectorCount:015C,015B,015CNumUDEs: 0000015C,00000000,0000015BPassed: 00000080,00000116,00000139Out:
PrgFSkipLBA: 0B1891AD,0B189308
Starting LBA of RW Request=000B1891AD Length=00001DE8
ProcessRWError -Read- at LBA 000B189C8D Sense Code=43110081ProcessRC: 00000001,00000000ReadContinuous: 0B189C8D,0000015CUnrecovSectorCount:015C,015B,015CNumUDEs: 0000015C,00000000,0000015BPassed: 00000080,00000116,00000139Out:
PrgFSkipLBA: 0B189C8D,0B189DE8
Starting LBA of RW Request=000B1891AD Length=00001DE8
ProcessRWError -Read- at LBA 000B189DE9 Sense Code=43160080ProcessRC: 00000001,00000000ReadContinuous: 0B189DE9,0000015CUnrecovSectorCount:015C,015B,015CNumUDEs: 0000015C,00000000,0000015BPassed: 00000080,00000116,00000139Out:
PrgFSkipLBA: 0B189DE9,0B189F44
Starting LBA of RW Request=000B1891AD Length=00001DE8
ProcessRWError -Read- at LBA 000B18A1FD Sense Code=43160080ProcessRC: 00000001,00000000ReadContinuous: 0B18A1FD,0000015CUnrecovSectorCount:015C,015B,015CNumUDEs: 0000015C,00000000,0000015BPassed: 00000080,00000116,00000139Out:
PrgFSkipLBA: 0B18A1FD,0B18A358
Starting LBA of RW Request=000B1891AD Length=00001DE8
ProcessRWError -Read- at LBA 000B18A359 Sense Code=43160080ProcessRC: 00000001,00000000ReadContinuous: 0B18A359,0000015CUnrecovSectorCount:015C,015B,015CNumUDEs: 0000015C,00000000,0000015BPassed: 00000080,00000116,00000139Out:
PrgFSkipLBA: 0B18A359,0B18A4B4
Starting LBA of RW Request=000B1891AD Length=00001DE8
ProcessRWError -Read- at LBA 000B18AE39 Sense Code=43110081ProcessRC: 00000001,00000000ReadContinuous: 0B18AE39,0000015CUnrecovSectorCount:015C,015B,015CNumUDEs: 0000015C,00000000,0000015BPassed: 00000080,00000116,00000139Out:
PrgFSkipLBA: 0B18AE39,0B18AF94
RECOV Servo Op=0095 Resp=0005
RECOV Servo Op=0295 Resp=0005
RECOV Servo Op=03A5 Resp=0005
RECOV Servo Op=00A5 Resp=0005
RECOV Servo Op=01A5 Resp=0005
RECOV Servo Op=03A5 Resp=0005
RECOV Servo Op=00A5 Resp=0005
RECOV Servo Op=01A5 Resp=0005

Attachments

[changkong]

Thank you for sharing

[Omega]

I have done probably a couple hundred of these for recovery and I rarely ever check the preamp. Only thing I check for is if the drive is alt or default for head type. These drives dont care about preamp from my finding.

What they are picky about sometimes is manufacture data. But I have also had drives just straight up not be compatible even though they are exact matches. I would recommend getting another set of heads. Try to get as close to the manufacturing data as you can. This is important to hopefully have heads that can write and fix firmware after the head swap.

The fact the drive is coming ready is good. You are able to get the drive to ID, access the SA etc?

have you checked to see what firmware modules are damaged?

Those sim errors are because system files are not being read.

[pepe]

This is important to hopefully have heads that can write and fix firmware after the head swap.

Heads that "can't write" usually do write albeit at wrong position, effectively overwriting adjacent tracks, corrupting other data. at least without any measures that prevent writing.