I've got a Maxtor 7Y250M0 here that was IDing as Maxtor CALYPSO. Found the appropriate loader & modules etc and got to where I can look at the SA and even see the broken module but I am unable to write back to it. I've worked on a bunch of Maxtors with this type of problem but haven't ever had the SA be unwritable... Is there something I'm missing?

This is a SATA drive, and I run into this problem whether I am using a SATA or PATA PCB.

_________________
You don't have to backup all of your files, just the ones you want to keep.

You mean when writing you get an error ? It's probably caused by different adaptives. To be sure, you have to use loader and a suitable RAM. Then check if you can have offset = 0. If the drive is still recognised as CALYPSO after loader, then you can't write anything to SA. The drive MUST calibrate.
Or you have serious problems in the SA itself. Can you start from SA-C ?

Are you using hddrepair, or more better tool?

In repair, i have seen this issue too....

Janos

I'm using the salvation hd doctor. When I attempt to upload the module or even just hex edit it directly it claims to be successful but then if I reload the module nothing has actually changed. The software does have an SA read/write test that tells me the SA is in read only mode.

When I load the loader/modules and reset the drive, the firmware does change from the factory code ending in Z to the correct firmware YAR51HW0, but still shows CALYPSO instead of switching to 7Y250M0.

The SA should be in fine shape. I purposely corrupted some of the modules on a working drive for demonstration/testing purposes. I've had no problem recovering from the same thing on some other drive models.

_________________
You don't have to backup all of your files, just the ones you want to keep.

I bet you have problems in ULIST or P- / G- LIST (trash).

The drive was working fine before I wrote a bunch of junk over the beginning of the 1F module. I was expecting to be able to just write the correct module back, however.

_________________
You don't have to backup all of your files, just the ones you want to keep.

If the 2nd copy of DATA group is OK you can try using the 2nd copy to extract what you need, or find an exact FW backup and write everything except adaptives and critical modules.

Anyway, you can break the Readonly state by hotswap.
But take care for adaptives, and assembly matching!

You can easily ruin your drive!

PS: try to replace the PCB.
I am interested.

Janos

I saved a copy of everything before I started... the problem is that I am unable to write anything to the SA to fix the module that I broke.

_________________
You don't have to backup all of your files, just the ones you want to keep.

Hotswap did work, once I was able to find a matching drive. I think that maybe I was not able to put the SATA board into safe mode appropriately. It has the same jumper pins as the PATA board but does not respond to the same jumper settings. I was able to find one setting that made the drive not spin up but then it never dropped busy. Ultimately I was able to get the board to detect as a model ending in Z by just removing it from the HDA entirely but then it did not seem to load rom/modules properly.

Anyone know the safe mode jumper setting for this model? It is a maxline plus 2.

[ o o o o ][:':::][ ____| |________ ] is the layout of the connectors.

_________________
You don't have to backup all of your files, just the ones you want to keep.

Get a PATA board from any DM9 model and switch a ROM. You can use it as PATA drive.

_________________
www.datarecoveryne.com

That is what I was doing earlier that got me to the point of being able to see all of the SA but not write to it.

_________________
You don't have to backup all of your files, just the ones you want to keep.

If you had PC3000, I could have suggested loading overlay's with original board, but I am not familiar with SD and how to do it.

_________________
www.datarecoveryne.com