Hi,

I have a ST3160815AS, firmware 3.ADA, site code WU, first three of the serial is 5RX. The drive spins up and stays busy in HD Doctor and DDI. In terminal mode on HD Doctor, I get the following:



I'm thinking weak heads, but if I'm way off please let me know also. Reason I think that is because it states "failed sys sect. write" (assuming that's the test write during initialization), but I don't have much knowledge on discerning terminal outputs (only what I've read and seen spelled out on this forum). On that note, does anyone know where I could come across a manual or series of white papers on terminal inputs and appropriate and/or common error outputs?

Thanks in advance,

Dizi

What you need, the drive or the data?
Some china website had explanation of terminal error codes you could try to google it.
This is common error for Nhawk, usually data still can be read without changing heads.

_________________
DataRecovery.bg

Samo,

Data is important, drive is to be trashed after recovery is complete.

Dizi

Try to find someone with UDMA close to you. I think here are several people from North America which can handle the job - Doomer, Quasimodo, drc, jono-ats... I bet they wont refuse this job.

Regards

_________________
DataRecovery.bg

Samo,

While aware of those around me with PC3K, if possible I would like to repair/recover myself. Any chance on recovery using SD tools? Is this a head thing, or possible SA damage (preventing reading and writing in important test areas)? Any input on the terminal log and what it means?

Dizi

Could be both...
CTRL+D twice and you'll get detailed output of what drive is trying to read and from where, how many times and etc...
SD does not have any documentation?

_________________
DataRecovery.bg

Can you load Cert code + Cert table and run Factory test 4?
I think maybe bad SA.

_________________
* Có ba thứ ngu dốt :

Không hiểu biết những gì mình đáng biết.
Hiểu biết không rành những gì mình biết.
Hiểu biết những gì mình không cần biết.

And what about the valuable data?

_________________
DataRecovery.bg

Are you sure you know what Factory test 4 stand for?

_________________
* Có ba thứ ngu dốt :

Không hiểu biết những gì mình đáng biết.
Hiểu biết không rành những gì mình biết.
Hiểu biết những gì mình không cần biết.

Just one observation : if you are doing DR on a regular basis or at least trying to offer this kind of services , some things like personal KB are pre-requisite. AND , if you bought tools, maybe (if possible of course) you should ask TS or search their KB first.
The observation above comes out from the variety of case, posts and requests from you seen on this board.
Last advice : get a more sophisticated (and supported) tool and most of all get all the necessary training - it will mean investing a quite important amount of $$$ / time but it will pay itself.

So said, I have some ideas about the cause of the problem (NHAWK are known for being not brilliant drives...) but without having the drive at hand and making some tests to pinpoint / exclude one cause or another it would be difficult to do.

To me may be heads, errors in SA, mechanical or a combination of them.

The following is from the SD forum which may help you to diagnose the problem......

Clearing the Glist is a really BAD idea.

No, do you know?

_________________
DataRecovery.bg

Yes, I did. I can tell you that no problem with data after run Factory test 4. Sure.

_________________
* Có ba thứ ngu dốt :

Không hiểu biết những gì mình đáng biết.
Hiểu biết không rành những gì mình biết.
Hiểu biết những gì mình không cần biết.

Are you both talking about same thing or is it a different name for something else ?

Did you know since when factory test 04 was removed from Seagate Ss?
Since 7200.8 - Tonka family there are no test named 04. And this drive is NHAWK (7200.10)

_________________
DataRecovery.bg

In fact. Unless it's another... TEST.

OK, things become quite unclear here!
I'll try to explain:
Drive have a problem and someone advice to fix it using factory test , no matter does it exist or not.
Ok, but You do not know what is the problem with that drive even You know what does the test do.
For perfectly working drive it will be OK, but for drive with uncertain problem, how are You sure DATA will be untouched?

_________________
DataRecovery.bg

!!

@BlackST,

Definitely noted, and I know this myself. However, just because I post things does not mean that what I post is who I am. If one were to look at your posts at first glance, they would think your sole profession is to insult those who know less than you. Now I respect you because I know that behind all the back-handed comments you do know your field very well. But this is a place for collaborative learning, so please can we have some? I do know some about DR, and when I see something on the boards that I know the solution to I post it to help people learn. But usually someone else beats me to it, and I spend most of my time on here either reading up on other problems people have had or trying to work out my own. Firmware and electronics are new to me and with so many variables it is difficult to cover all of them in the training I had. Regardless, while I would love to have better equipment that is not the case and so I have to work with that I have.

@dick,

Thank you for the input, I searched the SD forum and did not find that, but when I searched it I was searching a longer string than just the "Failed sys sect..." - I searched the first few lines of error. So that is an oversight on my part and a lesson learned to do more thorough research.

@hddlab,

Do you know what Factory Test 4 does (and will others please affirm this)? I don't feel comfortable running random tests on drives which I need the data from...

Lastly,
@Samo,

You are being very helpful, and I appreciate your patience. What we got from SD was a basic user's manual. Now from Ann LeFlore (poehere), we have a wonderful guide, but as it takes great time I have yet to fully read and test all the commands on working good drives and commit to memory what good and bad outputs look like.

Outputs will be in their own messages to follow, as I cannot fit them in this one.

Dizi