Apple AT31000528AS FirmAP24

[halfmoon]

Good morning Gentlemen and Ladies,

I have a Apple branded Seagate 1TB ST31000528AS with Firmware AP24 that does not transmit via terminal connection. A comparison to a none branded Seagate 1TB drive to thew Apple branded shows the MCU is different a LSI instead of ST. This 1TB has the Apple cable for temperature monitoring connecting to the terminal output.

Is terminal mode disabled on these drives?

thank you

[drc]

This 1TB has the Apple cable for temperature monitoring connecting to the terminal output.

Can you post a picture of this?

[halfmoon]

DRC,

here are the images of the Apple Seagate 1TB hard disk

cheers

Attachments

[drc]

This in itself shouldn't have any effect on terminal, as it is not using the pins for terminal connection. Having said that, it wouldn't surprise me if the terminal was disabled. Have seen that on some other newer Seagates.

[halfmoon]

thanks for the prompt reply

[fzabkar]

Those two pins are set aside for a jumper that sets the SATA interface speed.

No connection = 3Gbps
Jumpered = 1.5Gbps

See Section 3.2 of the following document.

Barracuda 7200.12 Serial ATA Product Manual, Rev. B:
http://www.seagate.com/staticfiles/supp ... 29369b.pdf

[drc]

Not in this case, obviously

[fzabkar]

Not in this case, obviously

It would seem strange for Seagate to redefine the end pin for some other function. In any case, if the relevant Apple product supports a variety of HDD models from different manufacturers, then it would seem unlikely for Apple to modify each and every model in this way.

Moreover, since the OP referred to these pins as "terminal output", then it may be that s/he is not aware of their original function.

BTW, I have seen temperature sensor PCBs that were attached to the side of a HDD:
http://forums.seagate.com/t5/Barracuda- ... td-p/49204

Having said the above, here is a thread where a Mac user appears to have a WD drive that connects to an external temperature sensor circuit:
http://forums.seagate.com/t5/Barracuda- ... td-p/83380

[pcimage]

Good morning Gentlemen and Ladies,

I have a Apple branded Seagate 1TB ST31000528AS with Firmware AP24 that does not transmit via terminal connection. A comparison to a none branded Seagate 1TB drive to thew Apple branded shows the MCU is different a LSI instead of ST. This 1TB has the Apple cable for temperature monitoring connecting to the terminal output.

Is terminal mode disabled on these drives?

thank you

AP24=HP24

[drc]

Not in this case, obviously

It would seem strange for Seagate to redefine the end pin for some other function. In any case, if the relevant Apple product supports a variety of HDD models from different manufacturers, then it would seem unlikely for Apple to modify each and every model in this way.

Moreover, since the OP referred to these pins as "terminal output", then it may be that s/he is not aware of their original function.

BTW, I have seen temperature sensor PCBs that were attached to the side of a HDD:
http://forums.seagate.com/t5/Barracuda- ... td-p/49204

Having said the above, here is a thread where a Mac user appears to have a WD drive that connects to an external temperature sensor circuit:
http://forums.seagate.com/t5/Barracuda- ... td-p/83380

So you are saying OP is lying, or plugged his plug into the wrong place, or what?

[drc]

http://blog.macsales.com/2751-proprieta ... e-09-imacs
http://www.ifixit.com/Guide/iMac-Intel- ... ent/1766/4
http://www.ifixit.com/Guide/iMac-Intel- ... ent/1634/4

[fzabkar]

So you are saying OP is lying, or plugged his plug into the wrong place, or what?

No, I didn't say that. You really should choose your words better. I said that the setup seemed "strange". I was thinking that it could be some way to remotely control the SATA interface speed, but I couldn't understand the point of doing so. Of course all this was before I saw your links. Now I see the setup as just another way for Apple to gouge its customers.

Moreover, it wasn't clear whether the OP was an end user or a DR pro, and I did provide a link to a Seagate thread that questioned my own interpretation, so I was prepared to be proven wrong.

[dick]

Hi halfmoon, It would be best to describe why it is you want to connect the drive to terminal. What are the symptoms? What can/can not be seen in Mhdd etc, bios, serial number, registers. Spin up down etc.

[BlackST]

Why the need for "terminal connection" in this case - in a nutshell what was the problem, if any ?

[halfmoon]

I received two drives on the same day exhibiting the same problem. Both are Seagate ST31000528AS, both clicking, shutdown, and identified as St_M13FQBL both have the new terminal connector for temperature sensing and both do not detect via terminal cable.
Initially i suspected ROM failure, Pass coded or Encrypted ROM or simply... Apple requested no access via terminal connector. The change to LSI MCU From ST also could have played a role.

Yes, i make my living doing data recovery for twenty years...and was simply asking a question.

thank you for your responses

cheers to all

[hddguy]

Yes, i make my living doing data recovery for twenty years...and was simply asking a question.

identified as St_M13FQBL... Initially i suspected ROM failure, Pass coded or Encrypted ROM

20 years experience but you are not familiar with one of the most common symptoms of one of the the most common failures in recent years?

This is not good....

[BlackST]

I received two drives on the same day exhibiting the same problem. Both are Seagate ST31000528AS, both clicking, shutdown, and identified as St_M13FQBL both have the new terminal connector for temperature sensing and both do not detect via terminal cable.
Initially i suspected ROM failure, Pass coded or Encrypted ROM or simply... Apple requested no access via terminal connector. The change to LSI MCU From ST also could have played a role.

Yes, i make my living doing data recovery for twenty years...and was simply asking a question.

thank you for your responses

cheers to all

Apple can request whatever they want, but if you are really good at it you can do what you want with THE DRIVE (this doesn't mean you get what you need, BUT...) . Well, after 20 years you may have missed something, it's not the end of the world ...

P.S. your question has a value.

[halfmoon]

wow....obviously i asked the wrong question....... sorry for taking your valuable time

I'll get back to recovering data and keeping my questions to myself

thank you for all who answered without a insulting comment

signed

20 year NEWBIE

[BlackST]

"INSULTING" is another thing and there was a GREAT hint between the lines : if you know (and you should) how this stuff works, you can succeed in diagnose / get data if there is no other catastrophical damage even if there is no terminal at all. After so much time spent in DR you should come to the conclusion that sometimes is necessary to circumvent problems instead of facing them. Obviously, if you want to have the tricks and tips explained, this has a value. Nothing more nothing less.

[fzabkar]

I received two drives on the same day exhibiting the same problem. Both are Seagate ST31000528AS, both clicking, shutdown, and identified as St_M13FQBL

According to the following article ...

http://www.salvationdata.com/blog/error ... r-7200-11/

... your drive could have a head problem, firmware problem or bad sector problem. The result is that the drive is unable to read the firmware which is located in the hidden System Area on the platters. It then reverts to identifying itself with a factory alias (ST_M13FQBL) which is stored in the serial flash memory chip on the board.

The Salvation Data article states that it may be possible to "solve it as fix the LBA=0 problem (yes, the LBA=0 problem caused by verify code error)."

Although the article refers to the 7200.11 drives, I have seen statements by data recovery professionals that the 7200.11 LBA=0 fix can also be applied to the 7200.12 models.

Of course you need to be able to communicate with the MCU ...