Seagate 7200.10 ST3250410AS stays BSY

[RescueDRL@gmail.com]

Hi, I have read in the prior posts about similar problem and it was suggested
to write the app code to ram and start the drive in Safe mode then clone it
in DE.
Here's what Terminal shows me:

Reset
8192k x 16 DRAM
NIGHTHAWKPLUS - 1_Disk S-1A 04-06-07_14:29
HM SFI
!
SFI
AMR
SFI
AMR
ERR A2: Boot Adapts

F>

If the problem can be fixed as I descibed above, or any other way, would you please
give me ALOT of detail as to the steps in PC3KU. (Sometimes the answers are so short
as to be of no help.)

Thanks a million, in advance!

Chris Lees
London, UK
==========================================================================

[ACE_Admin]

Hello

This output says, this drive cannot detect its servolabels or data markers.

SFI
AMR
SFI

Boot adaptives are not reachable. Hard drive will not start without them.

ERR A2: Boot Adapts

F>

This drive has hardware problems. The usual procedure with that cases is next:
You need to get a donor drive with same model and capacity, then swap the logic board and see if this drive displays
different output messages. If this situation didn't chagne try swapping the heads stack. Head stack donor drive must be with the same model and capacity. Same site code should be printed on donor drive's top sticker.

[RescueDRL@gmail.com]

Okay, I did the swap with a good donor (but had to transplant ROM chip)
Donor works with Patient card, but Patient exhibits same errors (BSY).

Tried head swap, Patient exhibits new errors:

Reset
8192k x 16 DRAM
NIGHTHAWKPLUS - 1_Disk S-1A 04-06-07_14:29
HM SFI
!

--and nothing else comes up in Terminal, and drive stays BSY only
(but spinning)

For completeness, the Donor (now with original Patient's heads) works fine:

Reset
8192k x 16 DRAM
NIGHTHAWKPLUS - 1_Disk S-1G 09-24-07 15:15

Buzz HM SFI
!
(P)SATA Reset
$SFI
AMR
$SFI
AMR
$SFI
AMR
$SFI
AMR
$SFI
AMR
$$SFI
AMR
$SFI
AMR
$$SFI
AMR
$SFI
AMR
$SFI
AMR
$SFI
AMR
$SFI
AMR
$SFI
AMR

Okay so now we know 100% the problem is Firmware related. I am hoping that there are
some F> commands to use while in Terminal that can lead to fixing this problem.

(When I enter Ctrl+Z in Terminal, I get the F> prompt. But it is T> prompt for the Donor.)

Thanks in advance for any help the Board members can supply.

Chris Lees,
London
===============================================================================
to correct this problem

[RescueDRL@gmail.com]

Wow, I just everyone is stumped with this one...

-Chris

[AJ2008]

Can you switch to Safe mode and read any resources like app code?

did you try load LDR to your drive while in safe mode?