ST3160827AS pending bug? - AutoRd Err 43 47

[helpless]

Hi mates!
This drive has a lot of bad sectors, Seatools trying to repair them, but in fact no repair was done. Maybe G-list is full?
Upon terminal connection I get a never ending output of AutoRd Err 43 and 47 and CE Log EC=43 I read that it may be a pending bug, which can be fixed by a certain command. SD claims it is a SA damage caused by bad sectors. Can I fix it in terminal? No data on drive. Someone here in another topic suggested to test heads before attempting to repair, how do I go about it? Thanks for any help.

Attachments

puma.txt

(3.61 KiB) Downloaded 625 times

[BlackST]

Likely the drive is worn out, you are wasting your time - especially with SD tool.

[BlackST]

Problem : this drive seems to have been kicked VERY HARD or the outcome is like it has.

If it was so simple....

[helpless]

I gave the drive another chance, it went thru a SS lite, but maybe that is not enough.
Now it shows in terminal:

Code:

Interface task reset
4096k x 16 buffer detected
PUMA - 1_Disk    M-22d 11-11-04 10:47

Buzz  - Head Mask FFFF - Switch to full int.
              Spin Ready
3.42  01-04-05 12:57

without (P)SATA Reset. What's wrong?

[helpless]

STUFF is empty. I set it to defaults, it is filled, re-power and empty again. says: Not configured-0
PUMA with four heads, serial 4MT0****
Age=50 Type=AB MxCyl=164F8 MxHd=3 MxSct=44C BSz=2000 TCode=00000000
Any hints on this?

[helpless]

Just to keep the topic alive I keep asking questions until someone else pops in with an answer.
I tried N2 on the drive, finished at age 50, but STUFF was empty and drive had a default modell name ST2Disk4Head (maybe after setting STUFF to defaults?). Thought that writing back original vendor track (again) could fix the issue, but that didn't help, tried an identical vendor from this site - no change. First Intf System Cylinder changed its position after SS, so I sent it to the new place. But I could finally fix model name by :

Code:

T>F
SetStuff->ASCI1B53543331363038323741532020202020202020202020202020202020202020202020202020202020
Stuff key 1b -> 53 54 33 31 36 30 38 32 37 41 53 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20

It was a 160gb drive, but BIOS sees only 131 GB (it can detect bigger drives of course), MHDD reports LBA 268 435 455, while HDSentinel (dos version) reports roughly correct size. Original capacity I looked up in the internet and it should be LBA 312581808.
2>x gives (at the end)
Total KBAs = 12AF8560 What is KBA? It is 313 492 832 (dec) more than the original drive size? Playing in terminal doesn't work either.

Code:

T>F
SetStuff->ASCI839EB012A1
Stuff key 83 -> 9e b0 12 a1

Size doesn't change, but in this case it matters. Maybe I didn't do it correctly.
Looking for the answer to 3 questions. How to fix (fill up) STUFF and drive size? But maybe that is just 1 question. And the 3rd, why there is no Master (or Slave) at the terminal output?

[helpless]

I entered lba size in the wrong order, corrected, got unreadable STUFF, sent vendor to the drive again, size is back to 160gb. STUFF is full and configured-1.
It is a great feeling, to find the solution myself, maybe that was the reason gurus didn't step in?

[Matiw]

Hi Helpless,

Could you tell us what the symptoms were to begin with ? Was the HDD busy, clicking .... ?

[helpless]

Hi,
Symptoms described in the first post. Drive clicked when heads hit a bad sector, there were continous bads, lots of them, on powering on pc bios warned of hdd smart error. After a short time of erase by MHDD it reported: Catastrophic failure, broken drive.