Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 



Sign in to follow this  
SMax77

seagate 7200.12 does not respond on terminal commands

Recommended Posts

SMax77    0

Hi, all.

 

I've faced a problem with my 7200.12, looks like a "0 LBA" shown here. After power up it sounds "t-r-r-r-r" 4-5 times and stops.

 

But the main problem is that I can not receive any answer from hdd to terminal 0x1A command (hex Ctrl+z command, isn't it? I'm using very simple "Terminal" with hexadecimal transmitted codes).

 

RS232 - TTL adapter connected correctly (sure by a huge number of forums and oscilloscope - I'm electronic engineer).

 

My hdd do not respond me in any condition of PCB and the brick:

Fully connected - failed,

Motor disconnected (by isolator) - failed,

heads disconnected (by isolator) - failed.

 

hdd "no reply" state is confirmed with oscilloscope (no changes on sygnal).

 

port settings : 38400, 8 data, 1 stop, no parity, no handshaking.

hdd: SN: 6VPEDKLG

        model:ST31000524AS

        firmware: JC4B

        PCB 100574451 rev.B

 

Could anybody help me? May be I need to short something? disconnect something? Send other command?

 

Thanks a lot in advance.

 

 

Share this post


Link to post
Share on other sites

jaclaz    943

There are some models that possibly need to have the "Read Channel" shorted, see:

http://www.msfn.org/board/topic/172245-720012-terminal-unlock/

 

But the issue here is that even once you will have access to terminal you won't know which exact commands to issue :w00t: or how to diagnose the exact problem, the:

"t-r-r-r-r" 4-5 times and stops

 

is likely to be something that you cannot simply recover via terminal commands. :(

 

jaclaz

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×