Seagate 7200.11 1TB - Spinup, Clicking, Spindown...

[_TK_]

When ZZnn shows instead of correct firmware version it usually indicates Terminal interface is not accessible. Did this FW rev change after LED fix ?

Terminal interface is not accessible, like usual. But after "/2 - Z - U" you can access.
Talking with controller is ok, but every time I try to access data (e.g. SMART reset) the LED:000000CC message comes up.

[scratchy]

Looks like terminal commands are being blocked ..

PM me.

[lcoughey]

I encountered a similar issue a few weeks ago...but, before spending too much time fighting with it, I opened the drive and discovered that the heads had crashed.

[_TK_]

I encountered a similar issue a few weeks ago...but, before spending too much time fighting with it, I opened the drive and discovered that the heads had crashed.

I don't want to open the drive at the moment (warranty), but the sound is pretty ok. No scratching head. And the customer (a professional photographer) said, that the drive was never fallen down.

[BlackST]

Head can be OK physically (external) but can be KO from electrical point of view. No rings, no scratches, no weird sound. But only noise from preamp... simply gone.

[_TK_]

Head can be OK physically (external) but can be KO from electrical point of view. No rings, no scratches, no weird sound. But only noise from preamp... simply gone.

You're right. I'll check with the oscilliscope next week. Today I don't want to see defective discs, and the weekend is coming very soon

Thomas

[N.C.]

I encountered a similar issue a few weeks ago...but, before spending too much time fighting with it, I opened the drive and discovered that the heads had crashed.

I don't want to open the drive at the moment (warranty), but the sound is pretty ok. No scratching head. And the customer (a professional photographer) said, that the drive was never fallen down.

Just a note:
You expected, if the drive not fallen, the heads can't be crashed/damaged?

This drive have never been fallen or dropped:

http://adatmentes24.hu/hun/galeria_kepek/P1030143.JPG

(From my photo gallery.)

Janos

[_TK_]

Gentlemen,

after some weeks and a lot of effort (2 very experienced date recovery companies were busy with these drive) I can tell you, that i365 in Amsterdam was able to recover almost all data.

Root cause was not only a defective pre-amp, also the firmware had a mismatch.
For that tricky job the price is very ok, compared to that, what other companies offered to me ( >1500 kEUR + VAT).

Regards,

Thomas

[Rousie]

After buying this drive to LOOK AFTER my data, it's given up on me last night.

Switch it on, it spins up, makes a rumble noise as though its reading, then makes a slight clunk noise, then starts to spin down again... Before the drive has stopped spinning, the above procedure starts again...

No idea what to do or where to look?

Anyone help me?

Dean

[_TK_]

Hi gents,

long time ago...
Meanwhile I had a couple of drives with Firmware ZZ7L. Most of them I could repair by using the standard solution:
- insulate PCB motor contacts, switch on, go into terminal window with ^z
- "/2", "Z"
- remove isolating business card
- "U"
- Reset S.M.A.RT. with "/1", "N1"
- switch power off and on
- reset Translator with "m0,2,2,,,,,22" - wait a couple of seconds
- switch iff / on again.

One ST31000333AS disc with FW SD35 was starting spindle motor, made a little noise, and stopped spindle motor then. Busy.
I tried S.M.A.R.T. reset as described above - and got correct type and S/N, but Firmware ZZ7L, and 0 MB.
Several experiments later I found the solution: I typed "m0,2,2,,,,,22", the spindle motor stopped, and then I took our little son and the dog, and went the daily round. Coming back 30 minutes later, the spindle motor was turning!
Disc off / on again - and everything was cured!!
So in most of all cases, Firmware ZZ7L is caused by a firmware failure, and not by a defective head.

Regards,

Thomas

[Doomer]

So in most of all cases, Firmware ZZ7L is caused by a firmware failure, and not by a defective head.

you missing the point here
you need to make a proper diagnostic before you can jump to conclusions
W/o diagnostic you can not tell what is "the most of all cases"
For example the drive from the beginning of this thread had bead heads, there is no doubt in this

Because you didn't post start up log of you second drive we can only guess what was wrong with it. I suggest you not to mix assumptions and facts

[_TK_]

Doomer, you/re right. Unfortunatelly I did not save the terminal log, because it was inconspicuous.
So let's say, in most of my mentioned cases the heads were ok, firmware data not.

[ponyon]

My first post on this forum.

Am having the "ZZ7L" firmware issue on my Seagate 1.5TB ST31500341AS.
Contacted Seagate and they told me based on my serial number mine doesn't have the "firmware issue".
Drive would click 10 times when turned on computer and can be seen in bios with ZZ7L firmware and paused there for 5 minutes.
However, cannot see drive at all when in windows.

Tried to flash it to SD1B, no luck.
Tried modding the flash.bat to bypass checking and flash it to SD1B, no luck.
Tried the terminal trick as well, however, after the U command it would give spin error.
F3 T>/2

F3 2>Z

Spin Down Complete
Elapsed Time 0.123 msecs
F3 2>U

DiagError 00006008
Spin Error
Elapsed Time 40.442 secs
R/W Status 2 R/W Error 84150180

_TK_ told me I would need to send it to i365 and pay around 1500 EUR.
There is some data on there I want but I don't have that kind of money to spend on this.
Any other ideas I can try?

[hddguy]

Drive would click 10 times when turned on computer and can be seen in bios with ZZ7L firmware and paused there for 5 minutes.
However, cannot see drive at all when in windows.

DiagError 00006008
Spin Error
Elapsed Time 40.442 secs
R/W Status 2 R/W Error 84150180

The problem is not firmware related.

[_TK_]

Looks like a defective head, or weak motor driver - spin up time 40s is much too long.

To clarify my words regaring "firmware failure": Of course NOW something is wrong in firmware area - this will show firmware "ZZ7L".
But the root cause for that behaviour is not a firmware (programming) failure - this comes from somewhere else: e.g. defective head, external voltage drop(?), ... - if somebody knows about the root cause, please let us know.

[Doomer]

Here is exactly the example
Now "the most of all cases" does not look as "the most" as before does it?

[_TK_]

again:
in most of my mentioned cases..
Also my first here described disc had a firmware mismatch - swapping heads failed.

Do you have a statistic, in how many (percent) cases it was only an easy to repair firmware mismatch, and in which cases a defective head / pre amp caused the trouble? Would be helpful, also and especially for me.

Thanks!

Thomas

[hddguy]

Statistics are irrelevant. correct diagnosis is only thing that is important here.

[hddguy]

Of course NOW something is wrong in firmware area - this will show firmware "ZZ7L".

Take a 100% functional model, unscrew PCB from HDA and connect PCB alone to a PC. You will see firmware 'zzzl'.

This does NOT strictly mean there is firmware problem, just that SA has not completely initialised. While it is a symptom of SA failure, it is also a symptom of multiple other causes also where SA is not read, whether recording heads are bad, spindle is damaged, media is bad...

Again, good diagnosis is absolutely crucial...

[_TK_]

hddguy, thanks!

Hmm, when I connect(ed) PCB only, I can see correct Model, Serial, Firmware - only Capacity is MB (). Newer saw wrong firmware, only by isolating PCB from disc.
But of course there must be a root cause for this mismatch. You all are right - good diagnosis is essential. Next time I'll do, I promise.