I have a SEAGATE 7200.12 that is giving the following terminal error while trying to init:

Rst 0x20M
(P) SATA Reset

(P) SATA Reset

SIM Error 3005
No HOST FIS-ReadyStatusFlags 2002A1A5

The drive doesn't become ready. I have access to terminal.


Can anybody explain what does this means?

Thanks.

_________________
D.R.L Data Revive Lab Services Ltd
Web: https://www.datarevive.net

TRIPLE chk the hdd sound when it powers UP.

_________________
Kuwait Data Recovery - UNIX GTC
The only reason for time is so that everything doesn't happen at once. By: Albert Einstein

The drive sounds like init normally, but it doesn't become ready.
It doesn't make any strange noise.

_________________
D.R.L Data Revive Lab Services Ltd
Web: https://www.datarevive.net

does it sound like tick tick

i had a similar case with head stack, make sure from the power ON sound when it Init. the drive.

try to compare it with another working one and see the Diff. when it powers ON

_________________
Kuwait Data Recovery - UNIX GTC
The only reason for time is so that everything doesn't happen at once. By: Albert Einstein

Finally i resolved the SIM ERROR 3005 problem thanks to bochen415 and the drive comes READY state.

But once it init and become ready, when i try to access any SA or CP or RAM or user's DATA it enters BSY and i can't do anything, until I power off-on again.

Note: only a few seconds just after init i can access SA & CP & RAM. If i try few seconds later, it enters BSY.
Can anyone tell me if this is PCB problem?

_________________
D.R.L Data Revive Lab Services Ltd
Web: https://www.datarevive.net

Being a novice and reading your diagnostics so far is there any chance that your seeing the 7200.11 BSY error message?

Is the PCB hot anywhere after init?

Your thanslator is gone most probably, try to deal with that issue first

_________________
DataRecovery.bg

You can load CERT, APP, ADAPTIVE...to RAM and try to extract data by COM port but only little data.

_________________
* 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.

The problem is not make the drive GO READY as sooner or later, "kicking" it it will happen... the problem is to get DATA and in a decent way.
I.E. randomly applying the "internet fix" without knowing the exact cause that stopped the drive working doens't always solve and it can make a lot of troubles, instead .

To me there is a mild "physical" or a less mild logical problem somewhere (have two ideas) that made the drive hang, but a thorough diagnose (and check) is needed.

I've also got a 7200.12 drive giving SIM Error 3005

and not going ready at the sata interface

Is ok at Seagate terminal and can read and write sectors ok through terminal)

st2000dl001
was originally giving a different not ready issue
but managed to work round that by disabling reallocation as per
viewtopic.php?f=1&t=26895

Now that I've pulled off the previous data
I was experimenting and wanted to low level format it

I used a T>m command ....

which is perhaps NOT a good idea on a 700.12 drive

This reported lots of issues with Hd 4
and gave up after 3-4%
DiagError 0000500D
User Partition Format Failed - Elapsed Time 126 mins 30 secs
R/W Sense 00000002, R/W Error 843200A6, File Error 00000000
LBA 4E4D0022, Cyl FFFFFFFF Hd FF, Phy Sec FFFF, Wedge FFFF


Now getting the SIM Error 3005

Possibly related to messing up the non resident glist as per
viewtopic.php?f=1&t=26367


T>V40 in its current state shows

F3 T>V40
Nonresident GList 0 entries returned
Total entries available: 0
PBA Len Flags Phy Cyl Hd PhySctr SFI


Any suggestions ?

(data isn't important, just trying to resurrect or partially resurrect the drive)

Also mentioned here
ie that 7200.11 low level formatting stuff not working on 7200.12

If you mean m0 command it is NOT low level format, it doesn't work UNLESS THE DRIVE HAS ONLY SOFT ERRORS and if so you don't need it at all. It takes a lot more to completely refurbish F3 drives .
This m0 bullshit is usual copy/paste from other sources having no background.

Should the User Slip defect list also have got cleared ?

And what exactly are the entries and slips ??


F3 T>V
User Slip Defect List
log log log phys phys
LBA span cumm cyl hd sctr zn cyl sctr SFI PBA
0 0 0 0 0 0 0 0 0 A 0

Head 0: entries 1 slips 0
Head 1: entries 0 slips 0
Head 2: entries 0 slips 0
Head 3: entries 0 slips 0
Head 4: entries 0 slips 0
Head 5: entries 0 slips 0
Total Entries 1 Total Slips 0

Whats this (new) entry for sector 0 ?


Luckily I noted them down in a previous post for this drive

half way down viewtopic.php?f=1&t=26068&start=20

Head 0: entries 660 slips A0E
Head 1: entries 511 slips 1496
Head 2: entries 184 slips 372
Head 3: entries 33A slips 8B1
Head 4: entries 588 slips 8C6
Head 5: entries 3F1 slips 809
Total Entries 19A8 Total Slips 3B96

Does that help me at all
assuming I still have the log that showed to individual entries (but cant find it)

Looks like the Terminal 'R' command
can now only read the (zeroed) user sectors up to where the 'format' failed
Reading after that gives
DiagError 00005003 R/W Status 2 R/W Error C4090082

which is very annoying

Can anyone confirm that is expected ?

The 'r' (long read?) can read above there
but I don't know how to understand the data


Can probably still 'R' read the system area cylinders

I can 'W' write to sectors, including those that I previously couldn't 'R' read anymore
and that makes them 'R' readable again

Found some info on
No HOST FIS-ReadyStatusFlags 2002A1A5

on http://www.computersciencelabs.com/news.php?News=57

"Although the drive will now successfully complete the Spin-up and Spin-down operation, the initialisation of the SMART module fails leaving the drive still unable to move on from a permanent ‘Busy’ state. This new fault is not restricted to the larger capacity 7200.12 drives such as the 500GB or 1TB, but can affect drives of any size from this series."

http://computersciencelabs.blogspot.ca/ ... fault.html
says to use the m0 command first

Still failed after 3% for me
But terminal now sees SATA resets form the sata interface even though shows busy

and V now shows lots of stuff again
V40 shows stuff again

Ah, maybe its back to my older 'not ready' issue
but disabling reallocation again doesn't help

Slowly making some progress

And some info here
viewtopic.php?t=24883&start=

Got to 6% that time
but still stuck non ready at sata interface

Dear Friend kyriakosxn

Your Problem Is Normal And Reguler Take Max To Max 10 Minut To Solve All Your Drive problems.
if u still not resolved ur case contact me on my skypee i will give u solution for this problem.
my skpyid is : smart.computech

yours friend
jignesh pankhania

Just for info

Forgot to mention, the later article viewtopic.php?t=24883&start= etc
seemed to fix the SIM Error 3005
and the V40 non resident glist and V1 full user slip list all came back fine ! ?
But still got problem both due to whatever the original problem with the drive was (bad area and remapping problems)
and due to messing it up further with the F3 T>m commands
viewtopic.php?f=1&t=27319

But its good practice and training

"and the V40 non resident glist and V1 full user slip list all came back fine ! ?"

No they didn't

V1 before was
....
Head 0: entries 660 slips A0E
Head 1: entries 511 slips 1496
Head 2: entries 184 slips 372
Head 3: entries 33A slips 8B1
Head 4: entries 588 slips 8C6
Head 5: entries 3F1 slips 809
Total Entries 19A8 Total Slips 3B96

Now its
...
Head 0: entries 7 slips 19E
Head 1: entries 2 slips E0B
Head 2: entries 1 slips 184
Head 3: entries 4 slips 464
Head 4: entries F slips 1EA
Head 5: entries 3 slips 2DF
Total Entries 20 Total Slips 1A5A

which hasn't even included the 19E4 p-list entries !!??