Firmware Reconstruction for Maxtor DiamondMax Plus 9

[Ergos]

Hello everyone,
I am looking for an expert or a specialized lab capable of performing an advanced firmware reconstruction on a legacy Maxtor drive.
Drive Details:
Model: Maxtor DiamondMax Plus 9 120GB ATA/133 (Calypso)
Model Number: 6Y120L0132011
Code: YAR41BW0
S/N: Y3LMZA2E
Mfg. Date: 26 DEC 2003 (Singapore)
The Problem:
The original PCB is missing. The drive was sent to Ontrack (KLDiscovery), but they were unable to recover it. According to their report, they tried several donor PCBs from their stock but failed because they couldn't regenerate the unique adaptive data required to initialize the heads and access the Service Area.
Current Situation:
I have since acquired a perfect donor drive with the exact same Code: YAR41BW0 (Made in Singapore).
The patient drive is physically silent when handled (no rattling or signs of platter scoring).
I understand that for this Calypso family, the adaptives are stored in the MCU and need to be reconstructed.
My Goal:
I am looking for a technician with PC-3000 expertise who can attempt an adaptive regeneration by booting the drive with the donor PCB (hot-swap or loader method) to gain access to the SA and rebuild the unique ROM modules (03, 04, 31, etc.) from the platters.
Is there anyone here (especially in Europe/Italy) who still feels confident in handling these old Maxtor firmware puzzles? Please let me know your thoughts or PM me for further details.
Thank you.

[fzabkar]

Strange.

This vendor doesn't mention adaptives.

https://www.hdd-parts.com/18000020.html

Please match the Model, Code, and Main Controller IC of your hard drive with the information listed above.

Can you show us a photo of your PCB?

[pepe]

i guess it is about 2 separate issues: pcb is lost and SA is damaged/corrupted...

[fzabkar]

The PCB has date codes on the ICs and on the PCB itself. That should help to narrow down a suitable donor.

https://www.hddoracle.com/viewtopic.php?p=135#p135

[Ergos]

Hi fzabkar and pepe,

Thank you for the feedback. As requested, here are photos of both the donor PCB and the PCB currently on the patient drive.
I'm not sure if the patient's PBC is original or not.

fzabkar, looking at the ICs and the PCB date codes, do you see any major mismatch that could explain why the adaptives wouldn't initialize?

Thank you for your invaluable time.

Attachments

[Ergos]

Hi fzabkar, pepe, and everyone,

Thank you for your guidance. I have taken photos of both the donor PCB and the PCB currently attached to the patient drive.
I'm not sure if the PCB on the patient's hdd is the orginal or not.

Technical Details from the Chips:

Donor PCB - Mfg. Date 27 Dec 2003 - Code: YAR41BW0
Main Controller IC:
AGERE
ARDENT C8-C1
040111300
ARDENT-C8C1-840UK
0350T
5787843

Motor Controller:
hynix 346A
HY57V161610DTC-6
KOREA 5W69009IA

Other Chip (don't know name)
SMOOTH
L7250E 1.2
B995P0348
MAL

Patient Drive Info - Mfg. Date 26 Dec 2003 - Code: YAR41BW0

(maybe not the original one)
Main Controller IC:
AGERE
ARDENT C8-C1
040111300
ARDENT-C8C1-840UK
0346S
5718143

Motor Controller:
SAMSUNG 340
K4S161622E
UJH182PCS KOREA

Other Chip (don't know name)
SMOOTH
L7250E 1.2
B991Q0344
MAL

@fzabkar: Based on the date codes and the IC versions shown in the photos, do you believe this specific Calypso revision stores unique adaptive data in the MCU, or could a straight PCB swap (or simple firmware transfer) work if the components match closely enough?

I'm looking forward to your analysis of the board revisions. Thank you!

Attachments

[fzabkar]

Code:

            Donor          "Patient"
            -----------    -----------
Manf date   27 Dec 2003    26 Dec 2003
MCU (YYWW)  0350           0346
SMOOTH      0348           0344
SDRAM        346            340
PCB         ????           4203 (WWYY)

The labels of the two HDDs indicate that they were manufactured one day apart in the same country. The PCBs appear functionally identical, except that several ICs are sourced from different manufacturers. However, the "patient" PCB appears to have been assembled around 4 to 6 weeks before the donor, if you compare the Year/Week date codes on the ICs.

That said, the two MCUs have the same code version, and both contain mask ROMs, ie no flash memory. Furthermore, there are no external flash memories at U401 or U303. This means that any adaptives are located in the "discware" on the platters, not on the PCB.

Since the patient PCB predates the donor PCB by one month, and since the two PCBs are functionally identical, I would expect that your donor PCB is a direct match for the original PCB. No modifications required.

As for the physical aspects of the two drives, the model number code, 6Y120L0132011, indicates that both drives have 3 heads, if I understand correctly. I don't know whether this means that there actually 3 physical heads, or it could be that there are 4 heads, with one being switched off. This might come into play if a head swap is required.

I'm not a data recovery pro, but it seems to me that either your drive has a head fault, or media damage, or firmware damage in the discware (as @pepe has suggested).

[Ergos]

Hi fzabkar,

First of all, thank you very much for your time and for the invaluable information you provided.

I have an update: I tested the patient drive by connecting it directly to the native IDE port using the donor PCB. The drive spins up, but it emits rhythmic clicking sounds (about once per second). After a few sequences of clicks, the motor spins down and stops completely.

I have now reinstalled the donor PCB back into its original drive to keep everything in order. It seems like a mechanical failure or a serious System Area issue. What is your take on this behavior?

Thanks again for your help!

[fzabkar]

Do both PCBs produce the same symptom?

If I understand correctly, in cases of a head transplant, the Code on the label should match. Yours are NMGD and KFCD for patient and donor, respectively. Like I said, I'm not a pro.

https://www.donordrives.com/blog/matching-guide#maxtor

https://hddguru.com/articles/2006.02.17-Changing-headstack-Q-and-A/

I can't understand why two drives manufactured one day apart in the same country/factory should have differing headstack codes. Perhaps my assumption that the same PCB was used for all drives during that one month period is wrong?

[fzabkar]

Some discussion here:

https://forum.hddguru.com/viewtopic.php?p=37324#p37324

[Ergos]

Hi fzabkar,

Thank you for pointing out the difference in the headstack codes (NMGD vs KFCD). That is a very interesting observation.

However, I must share a crucial detail that I had overlooked: there is a strong possibility that the PCB I considered "original" until now was actually a replacement installed back in 2004 during a first, failed attempt to fix the drive. This would explain why Ontrack found it "non-original" and why they couldn't find the unique adaptive data on it.

If my memory serves, the drive might have been "mismatched" for over 20 years. This makes your find about the new donor (Dec 27, 2003) being a "direct match" even more significant—it might actually be closer to the real original than the one I’ve had for years.

Given that the symptom persists with a functionally identical PCB, do you think the next logical step is to assume the "discware" (Service Area) is corrupted, or is that clicking sound more likely a sign that the heads (NMGD) simply cannot calibrate using the donor's MCU parameters?

Thanks again for your incredible insight!

[fzabkar]

If the original symptoms, with the original PCB, match the current symptoms, then it's an internal fault, probably bad head(s).

The OP in that other Maxtor thread is Italian, and is still in business. In fact, we had a chat just a few days ago.

[Ergos]

Thank you very much for the clarification and for the recommendation. I truly appreciate you pointing me toward a trusted professional who is still active in the field.
I’ll be sure to update the thread if we manage to get a successful recovery!