seagate 7200.10 160GB Failed sys sect. write!

[brockashford]

Hi there,

I am new and could use some direction. I recently repaired a 500GB 7200.11 that was stuck in bsy state..... cleared g-list $ SMART etc.
I am now dealing with an ST3160815AS 7200.10 160GB. It behaves the same as the previous drive with bsy state issue. Not detected in BIOS, but seems to spin up fine. I connected the PCB to a terminal and receive the following:

Reset
4096k x 16 DRAM
NHAWK - 1_Disk S-LE 11-14-07_16:30

Buzz HM SFI
!
(P)SATA Reset
Failed sys sect. write! Nwt Er 33 RdWr 13c88.00.0003

Read Ver Retrys

Read Ver Retrys

Read Ver Retrys

Read Ver Retrys

Read Ver Failure!
Failed sys sect. write! Nwt Er 00 RdWr 13c88.00.0003

I have tried clearing the SMART ---->

1>N1

Can't execute AT overlay calls when cert code is present
smartres.c - ovl L1 failed

I have also tried clearing the g-list ----->

T> (ctrl + r)
T>(VALID Cert Disk Code Detected - Revision # .0BK
T>i4,1,22

...........Then the prompt just stays there like its thinking or trying. I never get any return after that.

I am really starting to beleive that part of the SA is damaged, or there is a bad head. However I really dont know enough to make an accurate diagnostic. Any advice or direction would be soooo awesome. BTW this forum has had the most helpful information i have found.

Brock

[labtech]

The solution for one family of drives does not apply to another family despite the same brand. Suggest to stop playing around with such commands, if not too late already.

Need more advanced tools to be able to move forward toward a successful recovery. Pros have those tools.

[brockashford]

Ok I understand there is a market for such recovery. I have always done my pc repair and networking myself. I have been successfull in some logical data recovery as well as a few PCB replacements. Almost every time I am able to acquire the information I need online. Perhaps you could be more helpful? maybe tell me what the output means. Or perhaps recomend a diagnostic procedure of some sort. not in grave detail but at least something for me to research.

[labtech]

You have a firmware issue that could be caused by bugs, corruption, SA damage, weak heads, combination of these, etc.
You need professional expensive tools to run advanced tests and see if can bypass these problems.
The information is not available online as far as I know.

Either way, info without the tools will not get you too far IMHO.

[BlackST]

And tools without know-how will not get too far too.

The fact that you performed some simple repair or setup finding on the net generic advice, has given certain results UP TODAY.

Good luck with your researching .

Oh , BTW, NHAWK are not F3

[naveed]

test all heads and cut bad head and try back up f/w and run total ss

hope u will got soultion may ALLAH help us all

naveed

[BlackST]

And what will happen to data ?
This is totally destructive if you need to recover data.