Page 1 of 1

Seagate Sentosa Family Terminal Issues

Posted: Wed Nov 08, 2017 7:14 pm
by adrianf25
Hello,

Has anyone else ever had a real hard time getting terminal access on a Sentosa family Seagate FreePlay drive?

I've got this one I'm working on. Model ST1500LM003. Donor ID'ed and had terminal access without issue.

But it doesn't seem there's any way to get terminal access unless the drive is fully initialized. This patient I'm working on, I've replaced PCB with ROM transfer using boot ROM code. I've even tried replacing the heads, but the drive just spins up, sounds like a pretty normal startup with no clicking etc. But only ID's as:

Model : ST_M13FQBL
Serial : QNR_BFW
Firmware : 04191200
Capacity : 3.86 GB (8 089 950)

Which I know is normal for just having the PCB attached without HDA. I've tried all the usual tricks of shorting the read channel at different times, isolating the motor, isolating the preamp, etc. But nothing seems to get me any terminal access.

And yes I have tested my terminal adapter on other known good drives to be sure it's still working.

Any ideas on this?

Adrian
http://datarecoveryhdd.com/

Seagate Sentosa Family Terminal Issues

Posted: Wed Nov 08, 2017 7:28 pm
by Jared
Why are you quoting my own words (which I posted two years ago on HDD guru) back to me?

Seagate Sentosa Family Terminal Issues

Posted: Wed Nov 08, 2017 8:01 pm
by adrianf25
Because the same thing happens to me and this is a very good forum.

Maybe here I find help.

There are very wise people (like you) for this forum.

Seagate Sentosa Family Terminal Issues

Posted: Thu Nov 09, 2017 3:32 am
by pclab
But the original topic is yours or not?
Do you have exactly the same problem???
What tools do you have?

Seagate Sentosa Family Terminal Issues

Posted: Thu Nov 09, 2017 11:06 am
by Amarbir[CDR-Labs]
Hi Jared ,
This Happens When Heads Are Bad in This Series And Platter Firmware Has Not Initialised

Seagate Sentosa Family Terminal Issues

Posted: Thu Nov 09, 2017 11:12 am
by Jared
Yeah, I think on the case I had I finally gave up and determined that it was just badly damaged SA (which you can't even try to fix up) since I couldn't get terminal access even after perfectly matched heads were installed.

But, it was two years ago, so I'm not 100% sure I remember it.

Seagate Sentosa Family Terminal Issues

Posted: Thu Nov 09, 2017 11:53 am
by adrianf25
I just finished with the case (with the help of PC-3000 support) with the following conclusion:

If the head (or plates) are damaged in this Family it does not show the typical message of:

FAIL Servo Op = 0100 Resp = ....


But it simply does not show anything in the terminal.

You can try it yourself if you have a disk of this model with problems in the heads (which clicks, click,) you will see that it shows nothing through the terminal.

That was my conclusion.

Seagate Sentosa Family Terminal Issues

Posted: Thu Nov 09, 2017 2:14 pm
by Amarbir[CDR-Labs]
adrianf25 wrote:I just finished with the case (with the help of PC-3000 support) with the following conclusion:

If the head (or plates) are damaged in this Family it does not show the typical message of:

FAIL Servo Op = 0100 Resp = ....


But it simply does not show anything in the terminal.

You can try it yourself if you have a disk of this model with problems in the heads (which clicks, click,) you will see that it shows nothing through the terminal.

That was my conclusion.


Well,
This i already told you solved a case yesterday

Seagate Sentosa Family Terminal Issues

Posted: Thu Nov 09, 2017 4:14 pm
by adrianf25
Amarbir[CDR-Labs] wrote:
adrianf25 wrote:I just finished with the case (with the help of PC-3000 support) with the following conclusion:

If the head (or plates) are damaged in this Family it does not show the typical message of:

FAIL Servo Op = 0100 Resp = ....


But it simply does not show anything in the terminal.

You can try it yourself if you have a disk of this model with problems in the heads (which clicks, click,) you will see that it shows nothing through the terminal.

That was my conclusion.


Well,
This i already told you solved a case yesterday


Hello Amarbir, Yes Thank you for your cooperation :-)