[jaclaz]

From what you report that drive does not spin UP.

Check if it does first thing:
http://www.msfn.org/.../page__st__1213

If it does not, the ONLY possibility you have (VERY, VERY, VERY risky for the integrity of the drive) is some "percussive maintenance":
http://www.msfn.org/...te/page__st__29

In a limited (very limited amount of cases, holding it in a vertical position may be enough to allow initiating the spinning.

jaclaz

[locitman]

yes i tested another drive i had around and now i know the 7200.11 wont spin up. does that mean its not a BSY error and just a stuck/broken disc? the drive was never dropped or bumped. just disappeared from the BIOS.

[jaclaz]

locitman, on 17 February 2012 - 02:00 PM, said:

yes i tested another drive i had around and now i know the 7200.11 wont spin up. does that mean its not a BSY error and just a stuck/broken disc? the drive was never dropped or bumped. just disappeared from the BIOS.

The "normal" sequence at power on is AFAICU something along the lines of:

• read *something* from the onboard ROM
  
• spin up
  
• read *something else* from the actual disk platters
  
• present to the BIOS query some data

If the disk does not spin up it simply cannot read part of the information, it gets into a "busy" or BSY state and as such the BIOS won't detect it.

The symptoms could be - with the same possibility - a stuck bearing or a head stuck.

If the first, in some rare cases it can become free with either percussive maintenance or with the "freezer trick".
If the second it is more likely that it can be freed with some percussive maintenance BUT it is very likely that you will have a head crash.

To have an idea of the force that is needed to free a stuck bearing (if really stuck) check this:


And this to understand what happens with stuck heads:


jaclaz

[smandurlo]

What do you think of this log? Everything seems perfect, but the drive is not recognized properly and it does a not so correct sounds, it is not motor -it spins up correctly- and it is not heads crash -it is not so loud and it is not immediately-

Any idea?


F3 T>/2

F3 2>Z

Spin Down Complete
Elapsed Time 0.146 msecs
F3 2>U

Spin Up Complete
Elapsed Time 6.763 secs
F3 2>/

F3 T>F712
Byte:0712: RealTimeUpdatedFlags = 00 00
Byte:0712: Bit:0, HPA_SET_BY_SETMAX = 0
Byte:0712: Bit:1, HPA_SET_BY_SETMAX_EXT = 0
Byte:0712: Bit:2, DCO_SET_ACTIVE = 0
Byte:0712: Bit:3, CONGEN_READ_FROM_MEDIA = 0

F3 T>F,,22

Drive Configuration restored to defaults.

F3 T>F712
Byte:0712: RealTimeUpdatedFlags = 08 00
Byte:0712: Bit:0, HPA_SET_BY_SETMAX = 0
Byte:0712: Bit:1, HPA_SET_BY_SETMAX_EXT = 0
Byte:0712: Bit:2, DCO_SET_ACTIVE = 0
Byte:0712: Bit:3, CONGEN_READ_FROM_MEDIA = 1

F3 T>/1

F3 1>N1

F3 1>
F3 T>
F3 T>
F3 T>
F3 T>i4,1,22

F3 T>
F3 T>
F3 T>
F3 T>m0,2,2,,,,,22
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewr
ite Retries = 00C8

User Partition Format Successful - Elapsed Time 0 mins 00 secs

[AVIATEL]

hello,

i have a problem whit my seagate freeagent pro 1Tb 7200.11,
SN : 9QJ0WZFN
ST31000340AS
Firmware ; SD81


i have conect to rs232+ hyperterminal but give me this error:
F3 T>/2

F3 2>Z

LED:000000CE FAddr:00280575

before send enter for F3 2>Z i wait 60 seconds

i try many times, no result! Motor i can hear working : Brr...Brr.Brr....etc

what i must do ?
i will realy appreciate a quickly reply..

thank you
sorin

[jaclaz]

AVIATEL, on 21 February 2012 - 01:25 PM, said:

before send enter for F3 2>Z i wait 60 seconds

Try waiting some 20-30 seconds after powering the device and before issuing Ctrl+z:
http://www.msfn.org/.../page__st__1005

jaclaz

[AVIATEL]

HI
THANK you..
i have do until here :


F3 T>/2

F3 2>Z
?
Spin Down Complete
Elapsed Time 0.149 msecs
F3 2>U
after i press enter...nothing is happen,just bzz..bzz..bzz.. i have wait 2-3 minutes....
maybe U is not ok for my model

This post has been edited by AVIATEL: 22 February 2012 - 12:58 PM

[jaclaz]

AVIATEL, on 22 February 2012 - 12:30 PM, said:

F3 2>U
after i press enter...nothing is happen,just bzz..bzz..bzz.. i have wait 2-3 minutes....
maybe U is not ok for my model

It sounds like another disk that does not want (or cannot) spin up (read a few posts just above yours)

jaclaz

This post has been edited by jaclaz: 22 February 2012 - 01:14 PM

[AVIATEL]

thank you
i have solve my HDD ! many thanks to Jaclaz !
can you tell me how i must update the firmware? Now i have SD81..
regards!
sorin

This post has been edited by AVIATEL: 22 February 2012 - 04:27 PM

[DirkR]

Hi All,

I'm trying to figure whether I have the problem described here or not, so whether it makes sense for me to try the solutions described here.

I have a couple 7200.11 for occasional backup, i.e. most of the time they are powered down on the shelf. I use them in an external disc enclose (toaster), so I don't need cases for all of them.

Now one of them is doing the following: on power-up it spins up and I can hear heads clicking. The clicking persists for 30 seconds (10 tries), after which the disc spins down and is inaccessible. In the syslog (this is on Linux, Fedora 14) I see the following (the first part is normal for switching discs in the toaster):

Feb 24 09:28:34 destiny kernel: [1799439.032641] ata6: exception Emask 0x10 SAct 0x0 SErr 0x4050002 action 0xe frozen
Feb 24 09:28:34 destiny kernel: [1799439.032647] ata6: irq_stat 0x00000040, connection status changed
Feb 24 09:28:34 destiny kernel: [1799439.032652] ata6: SError: { RecovComm PHYRdyChg CommWake DevExch }
Feb 24 09:28:34 destiny kernel: [1799439.032662] ata6: hard resetting link
...
Feb 24 09:28:59 destiny kernel: [1799464.777348] ata6: link is slow to respond, please be patient (ready=0)
Feb 24 09:29:00 destiny kernel: [1799465.693551] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 24 09:29:05 destiny kernel: [1799470.683619] ata6.00: qc timeout (cmd 0xec)
Feb 24 09:29:05 destiny kernel: [1799470.683631] ata6.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Feb 24 09:29:05 destiny kernel: [1799470.683638] ata6: hard resetting link
Feb 24 09:29:06 destiny kernel: [1799470.988021] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 24 09:29:11 destiny kernel: [1799475.970027] ata6.00: failed to IDENTIFY (I/O error, err_mask=0x100)
Feb 24 09:29:11 destiny kernel: [1799475.970064] ata6: limiting SATA link speed to 1.5 Gbps
Feb 24 09:29:11 destiny kernel: [1799475.978140] ata6: hard resetting link
Feb 24 09:29:11 destiny kernel: [1799476.282550] ata6: SATA link down (SStatus 0 SControl 310)
Feb 24 09:29:11 destiny kernel: [1799476.282561] ata6: EH complete

Does this sound familiar to anybody? Are these the BSY symptoms, or does this sounds more like jammed heads or something else physical? Many years ago I remember seeing comments about heads getting stuck in the lubricant of the platters, and given that the disk has been unpowered for a couple months I think something physical would be possible, even though I wouldn't expect to see it nowadays.

Any hints welcome!

[jaclaz]

DirkR, on 24 February 2012 - 09:42 AM, said:

Does this sound familiar to anybody? Are these the BSY symptoms, or does this sounds more like jammed heads or something else physical? Many years ago I remember seeing comments about heads getting stuck in the lubricant of the platters, and given that the disk has been unpowered for a couple months I think something physical would be possible, even though I wouldn't expect to see it nowadays.

Any hints welcome!

Forget about Linux (or DOS or windows or any OS).

Just boot with the disk attached and check the BIOS, is it detected?

If NO, it is a BSY of some kind
IF yes, BUT with a size of 0, it's a LBA0.

Please note that there could be many reasons for a BSY, but yes, what you describe does sound like a BSY status.

For the record there is NO lubricant of ANY kind on the platters (only air), there is lubricant inside the (motor) bearing - which yes, can lead to a stuck bearing.
Stuck heads are usually due to physical contact (usually connected to a fall or a hard hit) between heads and platters.

The behaviour you describe is that of:

• a functional motor/bearing (spins up/spins down)
  
• a functional head arm (clicks - as opposed to "buzz")
  
• an issue with the ability to read some "initial" data on the platters (BSY or LBA0, cannot say which just from the description)

@AVIATEL
BEFORE upgrading the firmware, do get all your DATA and make a backup.
Then proceed normally with the instructions from Seagate.
In any case DO NOT consider the disk to be "reliable" or - maybe better said - "more reliable" than it was before the firmware upgrade.
(we don't know if your issue was due to the original cause - which is relatively innocuous - or by *something else* and only by *sheer luck* the solution worked on your disk - only because it is a sort of "general reset")


jaclaz

This post has been edited by jaclaz: 24 February 2012 - 10:04 AM

[vuudush]

I have the following:

ST2000DL003
P/N: 9VT166-301
F/W: CC32
DATE: 11451
SITE: WU

It was connected using an external case with its own power supply through an e-sata port to my laptop.

Three days ago i was copying some files from it and it made a click noise, halt for a few seconds than finished copying the files.
Right away i ran seagate tools but nothing was found, both fast as full tests.

No noises were made after, so a turned it off and went to bed.

Next day when i turned it on it made some noises and after that it has been recognized as "st_m13fqbl" with 3,86GB.

So, my question is:

Is this the case of trying this method?

If so, i've been trying this using an USB to Serial cable but i get nothing on Hyper Terminal.
When i press ctrl+z, a small arrow appears and nothing else. No messages, no commands, nothing at all.

I've tried with RX/TX only, RX/TX/GND, swapping RX/TX. All different ways possible and still got nothing.

Any ideas?

Thx.

[BlouBul]

vuudush, on 28 February 2012 - 03:26 PM, said:

I have the following:

ST2000DL003
...
...
... it has been recognized as "st_m13fqbl" with 3,86GB.

So, my question is:

Is this the case of trying this method?

Well, since this method is for 7200.11 Drives and NOT for Seagate LP Green drives and your Drive are neither in the BSY, nor 0LBA state, the short answer is NO (and you are in the wrong thread ).

However, IIRC , there has been some reports where a failed fix resulted in a wrongly displayed model, which has been resolved by doing the fix again (on a 7200.11).

So, since this is like a "general reset" the method might work, if you can get it to work in Hyperterminal (which has been a problem for LP Green drives ). See if anything here helps http://www.msfn.org/...-ceases-to-tal/

This post has been edited by BlouBul: 29 February 2012 - 01:09 PM

[cefs21]

Hello. I have followed the same procedure, I came and me everything you know that message came from the hdd, ending with the final partition sucecs user. All well and good my Seagate 320gb hdd in bios and it sees 320gb capacity but when you boot windows 7 from the hdd and repaired it at his side and when the system starts to appear buteze icons screen turns black, mouse I can move on the screen and not do anything. What can I do them again to make it start. Specific certainly not anything I did wrong procedure. I tested now on a system with win xp and I installed the 2nd hdd hdd and they try to start Windows blue screen appears and begins checking hdd and everything is one line that says 63,600 can not read and so, after 8 o'clock arrived at 76,000 and counting. Why is that? Thank you in advance for response

[vuudush]

BlouBul, on 29 February 2012 - 12:43 PM, said:

vuudush, on 28 February 2012 - 03:26 PM, said:

I have the following:

ST2000DL003
...
...
... it has been recognized as "st_m13fqbl" with 3,86GB.

So, my question is:

Is this the case of trying this method?

Well, since this method is for 7200.11 Drives and NOT for Seagate LP Green drives and your Drive are neither in the BSY, nor 0LBA state, the short answer is NO (and you are in the wrong thread ).

However, IIRC , there has been some reports where a failed fix resulted in a wrongly displayed model, which has been resolved by doing the fix again (on a 7200.11).

So, since this is like a "general reset" the method might work, if you can get it to work in Hyperterminal (which has been a problem for LP Green drives ). See if anything here helps http://www.msfn.org/...-ceases-to-tal/

I had the feeling that i might be in the wrong place,but nothing else seems to work. Saddly i think my drive "is no more" at this time. Maybe i'll use a hammer to tear it apart and send as a gift to Seagate.

Thx.

[BlouBul]

cefs21, on 01 March 2012 - 11:00 AM, said:

Hello. I have followed the same procedure, I came and me everything you know that message came from the hdd, ending with the final partition sucecs user. All well and good my Seagate 320gb hdd in bios and it sees 320gb capacity but when you boot windows 7 from the hdd and repaired it at his side and when the system starts to appear buteze icons screen turns black, mouse I can move on the screen and not do anything. What can I do them again to make it start. Specific certainly not anything I did wrong procedure. I tested now on a system with win xp and I installed the 2nd hdd hdd and they try to start Windows blue screen appears and begins checking hdd and everything is one line that says 63,600 can not read and so, after 8 o'clock arrived at 76,000 and counting. Why is that? Thank you in advance for response

Ok, at least you can see your hdd.

Now your first priority is to recover any data that you do not have a backup of.
Try putting that hdd as a secondary hdd, boot from the good hdd and see if you can see your data and copy that to a safe location.
Once your data is safe, you can worry why the disk is not bootable.

[BlouBul]

vuudush, on 01 March 2012 - 11:52 AM, said:

I had the feeling that i might be in the wrong place,but nothing else seems to work. Saddly i think my drive "is no more" at this time. Maybe i'll use a hammer to tear it apart and send as a gift to Seagate.

Thx.

Well, if you have no important data on the disk of which you have no backup of, and can afford a new hdd, that is certainly a good way to get rid of your frustration

Otherwise, let us see if we can find a solution to your problem. On further searching, I found a couple of very similar symptoms on the 7200.11's (but no solution yet ), so it might be caused by "something else". I will look some more and hopefully find something helpful.

[vuudush]

I've just dissassembled the drive and found on the first disk a huge scratch with 2mm wide. So, mistery solved. Maybe a power surge caused this.

[BlouBul]

vuudush, on 01 March 2012 - 12:14 PM, said:

I've just dissassembled the drive and found on the first disk a huge scratch with 2mm wide. So, mistery solved. Maybe a power surge caused this.

_TK_here (August 10, 2010) had exactly same problem as you on an ES.2, which was solved by the shorting trick, so there is hope, we just have to find the right answer for your problem.

Maybe start a new thread and we can see if we can find more info on that problem for your drive.

This post has been edited by BlouBul: 01 March 2012 - 12:54 PM

[cefs21]

BlouBul, on 01 March 2012 - 11:53 AM, said:

cefs21, on 01 March 2012 - 11:00 AM, said:

Hello. I have followed the same procedure, I came and me everything you know that message came from the hdd, ending with the final partition sucecs user. All well and good my Seagate 320gb hdd in bios and it sees 320gb capacity but when you boot windows 7 from the hdd and repaired it at his side and when the system starts to appear buteze icons screen turns black, mouse I can move on the screen and not do anything. What can I do them again to make it start. Specific certainly not anything I did wrong procedure. I tested now on a system with win xp and I installed the 2nd hdd hdd and they try to start Windows blue screen appears and begins checking hdd and everything is one line that says 63,600 can not read and so, after 8 o'clock arrived at 76,000 and counting. Why is that? Thank you in advance for response

Ok, at least you can see your hdd.

Now your first priority is to recover any data that you do not have a backup of.
Try putting that hdd as a secondary hdd, boot from the good hdd and see if you can see your data and copy that to a safe location.
Once your data is safe, you can worry why the disk is not bootable.

Problem solved. My mistake was that you had typed the last command "Z" than I typed "z" small and I think something happens and does not work well. After I repeated the procedure and I typed that last command in hyperterminal "Z" great everything worked perfectly. Thank you so much for this thread.