[BlouBul]

eptan, on 10 December 2011 - 07:47 AM, said:

somebody here to help,a question...
who use the dku-2 work in fine or failed?
does the dku-2 can work on it?
how should i know which rx and tx?
sorry for my bad english!

The DKU-5 works the same as the CA-42. See FGA #6 for more info. The link given there will show you how to easily identify Rx and Tx.

[eptan]

BlouBul, on 10 December 2011 - 12:15 PM, said:

eptan, on 10 December 2011 - 07:47 AM, said:

somebody here to help,a question...
who use the dku-2 work in fine or failed?
does the dku-2 can work on it?
how should i know which rx and tx?
sorry for my bad english!

The DKU-5 works the same as the CA-42. See FGA #6 for more info. The link given there will show you how to easily identify Rx and Tx.

thanks for you helping~
but,not is DKU-5,Is DKU-2

[MIKEJOE]

Hi everyone !

I have a Seagate 7200.11 HDD with the BSY bug (ST31000340AS / SD15), and used the Gradius steps to fix it.
Everything was fine - the cable (Nokia CA-42) was adapted, the connections ok, ect.

Even the commands were fine:

1º Attempt

F3 T>/2

F3 2>Z

Spin Down Complete
Elapsed Time 0.149 msecs
F3 2>U

Spin Up Complete
Elapsed Time 9.746 secs
F3 2>/1

F3 1>N1

F3 1>
F3 T>m0,2,2,0,0,0,0,22
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 00, Max Certify Rewr
ite Retries = 0000
User Partition Format   5% complete, Zone 00, Pass 00, LBA 00004339, ErrCode 000
User Partition Format   5% complete, Zone 00, Pass 00, LBA 00008DED, ErrCode 000
00080, Elapsed Time 0 mins 10 secs
User Partition Format Successful - Elapsed Time 0 mins 10 secs

F3 T>

2º Attempt

F3 T>/2

F3 2>Z

Spin Down Complete
Elapsed Time 0.150 msecs
F3 2>U

Spin Up Complete
Elapsed Time 9.723 secs
F3 2>/1

F3 1>N1

F3 1>/T

F3 T>i4,1,22

F3 T>
F3 T>m0,2,2,,,,,22
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewr
ite Retries = 00C8
User Partition Format   5% complete, Zone 00, Pass 00, LBA 00004339, ErrCode 000
User Partition Format   5% complete, Zone 00, Pass 00, LBA 00008DED, ErrCode 000
00080, Elapsed Time 0 mins 10 secs
User Partition Format Successful - Elapsed Time 0 mins 10 secs

F3 T>

But it still not recognized by the BIOS.
Any idea what should be missing here? There's any chance that the cable/connections are not set right, even with the hyperterminal commands results ( as presented) ?
BTW, I respected closely the suggestions of "timing" and "shutdowns" steps.

Thanks

[BlouBul]

eptan, on 10 December 2011 - 01:50 PM, said:

thanks for you helping~
but,not is DKU-5,Is DKU-2

No, DKU-2 will NOT work.

[BlouBul]

MIKEJOE, on 10 December 2011 - 02:47 PM, said:

I have a Seagate 7200.11 HDD with the BSY bug (ST31000340AS / SD15), and used the Gradius steps to fix it.

User Partition Format Successful - Elapsed Time 0 mins 10 secs

But it still not recognized by the BIOS.
Any idea what should be missing here? There's any chance that the cable/connections are not set right, even with the hyperterminal commands results ( as presented) ?

Your cables are definitely connected right if you can talk to your drive through Hyperterminal (that is the only purpose of all the cables). Are you sure all your cables are connected when you test your drive again after the fix (eg SATA data cable )?
You can also try the so-called optional commands given by Aviko here.

This post has been edited by BlouBul: 10 December 2011 - 09:47 PM

[Huygens]

MIKEJOE, on 10 December 2011 - 02:47 PM, said:

1º Attempt

F3 1>N1

F3 1>
F3 T>m0,2,2,0,0,0,0,22

I assume you powered down (and powered up) everything between "F3 1>" and "F3 T>"?

On my 500 Gb disk I isolated the head contacts with a thick card board piece (in such a way that the motor contacts probably also were without contact). This may be more tricky as I had to completely untighten 3 torx screws on one side of the board, but it worked for me.

This post has been edited by Huygens: 11 December 2011 - 04:37 AM

[eptan]

BlouBul, on 10 December 2011 - 09:15 PM, said:

eptan, on 10 December 2011 - 01:50 PM, said:

thanks for you helping~
but,not is DKU-5,Is DKU-2

No, DKU-2 will NOT work.

OK,finally i got the ca-42 already,i with try it,and wish me a luck.thanks

This post has been edited by eptan: 12 December 2011 - 12:18 AM

[BlouBul]

eptan, on 12 December 2011 - 12:06 AM, said:

OK,finally i got the ca-42 already,i with try it,and wish me a luck.thanks

Great, that should work better
Use the previous given link to identify Rx and Tx.

And I wish you all the luck you need to fix it (and some more)

[eptan]

BlouBul, on 12 December 2011 - 01:02 AM, said:

eptan, on 12 December 2011 - 12:06 AM, said:

OK,finally i got the ca-42 already,i with try it,and wish me a luck.thanks

Great, that should work better
Use the previous given link to identify Rx and Tx.

And I wish you all the luck you need to fix it (and some more)

omg.please help,i cannot start a port,my port is com8,bits per second is 9600,i change 38400,and when i open the hyper terminal
unable to open com8,please check your port settings,help,help,help
is my driver to out or...?where can found the newest driver?

This post has been edited by eptan: 12 December 2011 - 01:30 AM

[BlouBul]

eptan, on 12 December 2011 - 01:29 AM, said:

please help,i cannot start a port,my port is com8,bits per second is 9600,i change 38400,and when i open the hyper terminal
unable to open com8,please check your port settings,help,help,help
is my driver to out or...?where can found the newest driver?

If you used the original driver cd that came with the cable, it should be the right driver, otherwise your guess would be as good as mine.
Check in Device Manager if your cable is seen, that should mean you have the right driver installed.
If driver is right, unplug/replug cable and see if it is better. Also restart HyperTerminal.

[Huygens]

eptan, on 12 December 2011 - 01:29 AM, said:

when i open the hyper terminal unable to open com8,please check your port settings,help,help,help

Hard to guess what you mean.

You could either search the net for your driver. Or you could try to skip the dialog, perhaps it's some kind of unnecessary setting?

If you provide screen shots, things may be more clear to us.

[MIKEJOE]

BlouBul, on 10 December 2011 - 09:31 PM, said:

MIKEJOE, on 10 December 2011 - 02:47 PM, said:

I have a Seagate 7200.11 HDD with the BSY bug (ST31000340AS / SD15), and used the Gradius steps to fix it.

User Partition Format Successful - Elapsed Time 0 mins 10 secs

But it still not recognized by the BIOS.
Any idea what should be missing here? There's any chance that the cable/connections are not set right, even with the hyperterminal commands results ( as presented) ?

Your cables are definitely connected right if you can talk to your drive through Hyperterminal (that is the only purpose of all the cables). Are you sure all your cables are connected when you test your drive again after the fix (eg SATA data cable )?
You can also try the so-called optional commands given by Aviko here.

Hi Bloubul,

Yes I plugged everything, even tested the cables with other 2 HDDs and they worked fine.

I tried the commands you said (Aviko):

F3 T>/2
F3 2>Z
Spin Down Complete
Elapsed Time 0.152 msecs
F3 2>U
Spin Up Complete
Elapsed Time 9.686 secs
F3 2>/
F3 T>F712
Byte:0712:       RealTimeUpdatedFlags = 00 00
Byte:0712:           Bit:0, HPA_SET_BY_SETMAX = 0
Byte:0712:           Bit:1, HPA_SET_BY_SETMAX_EXT = 0
Byte:0712:           Bit:2, DCO_SET_ACTIVE = 0
Byte:0712:           Bit:3, CONGEN_READ_FROM_MEDIA = 0
F3 T>F,,22
Drive Configuration restored to defaults.
F3 T>F712
Byte:0712:       RealTimeUpdatedFlags = 08 00
Byte:0712:           Bit:0, HPA_SET_BY_SETMAX = 0
Byte:0712:           Bit:1, HPA_SET_BY_SETMAX_EXT = 0
Byte:0712:           Bit:2, DCO_SET_ACTIVE = 0
Byte:0712:           Bit:3, CONGEN_READ_FROM_MEDIA = 1
F3 T>/1
F3 1>N1
F3 1>
F3 T>     <----shutdown!! (10 sec)
F3 T>i4,1,22
F3 T>     <----shutdown!! (10 sec)
F3 T>m0,2,2,0,0,0,0,22
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 00, Max Certify Rewr
ite Retries = 0000
User Partition Format   5% complete, Zone 00, Pass 00, LBA 00004339, ErrCode 000
User Partition Format   5% complete, Zone 00, Pass 00, LBA 00008DED, ErrCode 000
00080, Elapsed Time 0 mins 10 secs
User Partition Format Successful - Elapsed Time 0 mins 10 secs
F3 T>/2
F3 2>Z
Spin Down Complete
Elapsed Time 13.033 secs
F3 2>
     <----shutdown everything!!

And still not recognized...
I'm really frustated...

[BlouBul]

MIKEJOE, on 12 December 2011 - 02:20 PM, said:

Hi Bloubul,

Yes I plugged everything, even tested the cables with other 2 HDDs and they worked fine.

I tried the commands you said (Aviko):

...
F3 T>F,,22
Drive Configuration restored to defaults.
...
F3 T>m0,2,2,0,0,0,0,22
...
User Partition Format Successful - Elapsed Time 0 mins 10 secs

And still not recognized...
I'm really frustated...

That is strange . The User Partition Format Successful normally means the disk is reset to defaults and the BSY error is fixed. I wonder if your disk does not suffer from *something else* that cause it not to be recognised by BIOS.

This post has been edited by BlouBul: 12 December 2011 - 09:21 PM

[Huygens]

MIKEJOE, on 12 December 2011 - 02:20 PM, said:

And still not recognized...
I'm really frustated...

Something isn't properly reset, I don't know why, but having read some posts I would also suggest the following.

Could you try:
F3 T>/2
F3 2>Z

<--- (remove paper piece, tighten torx screws)

F3 2>U
F3 2>/
F3 T>F,,22
F3 T>m0,2,2,0,0,0,0,22

<--- (now, power down everything and then test HD in BIOS)

with no power down between (F,,22 and m0,2,2,0,0,0,0,22 commands) and _not_ doing the i4 and _not_ doing the N1 command. There has been some debate concerning the power down, if it's needed or if it could potentially be bad.

I think aviko claimed that the i4 command could potentially be harmful, but anyone may correct me, I also think gradius had a different opinion on this i4 matter than aviko. Also, aviko gave this alternative (!) m0 command in this post, when the HD still wasn't detected in BIOS. It may be worth taking a look at.

It my be worth noting that there has been some discussion if some commands may destroy data as in this post.

The last resort will be to read all 4000 posts in this thread and see if anything rings a bell.

[BlouBul]

Huygens, on 13 December 2011 - 06:16 AM, said:

I think aviko claimed that the i4 command could potentially be harmful, but anyone may correct me, I also think gradius had a different opinion on this i4 matter than aviko. Also, aviko gave this alternative (!) m0 command in this post, when the HD still wasn't detected in BIOS. It may be worth taking a look at.

It my be worth noting that there has been some discussion if some commands may destroy data as in this post.

It is the M0,1,... command that wipes the disk. See here http://www.msfn.org/...051#entry962051

[jaclaz]

If needed; DO NOT EVEN THINK of EVER using/suggesting/mentioning the M0,1,1 command!
In the best case it will completely wipe the hard disk, MOST probably it will also render the disk UNUSABLE!

Once you set apart the spite, Gradius collected and translated some info, while Aviko knows what he is talking about BUT by chance or by design he posted half truths or incomplete info.
This is among the reasons why the tutorial by CarterinCanada is advised (by me), it may not cover all issues but it covers the specific one without any deceiving or dangerous instructions.

jaclaz

[Huygens]

jaclaz, on 13 December 2011 - 10:50 AM, said:

Once you set apart the spite, Gradius collected and translated some info, while Aviko knows what he is talking about ...
This is among the reasons why the tutorial by CarterinCanada is advised (by me), it may not cover all issues but it covers the specific one without any deceiving or dangerous instructions.

If we assume it's too expensive to send the bricked HD to a data recovery company:

What you say is that if the CarterinCanada commands plus the i4 & the F,,22 commands don't work, meaning the HD still isn't detected by BIOS, the HD should be regarded as dead?

This post has been edited by Huygens: 13 December 2011 - 11:23 AM

[BlouBul]

jaclaz, on 13 December 2011 - 10:50 AM, said:

If needed; DO NOT EVEN THINK of EVER using/suggesting/mentioning the M0,1,1 command!
In the best case it will completely wipe the hard disk, MOST probably it will also render the disk UNUSABLE!

I agree with the using/suggesting part, but about mentioning, since it is already out there in the public domain: forewarned is forearmed. It is better if people know beforehand NOT to use it.

Huygens, on 13 December 2011 - 11:21 AM, said:

If we assume it's too expensive to send the bricked HD to a data recovery company:

What you say is that if the CarterinCanada commands plus the i4 & the F,,22 commands don't work, meaning the HD still isn't detected by BIOS, the HD should be regarded as dead?

Good question. That depends on what your definition (and degree) of dead is. Like I said earlier, my theory (I might be wrong) is :

BlouBul, on 12 December 2011 - 09:19 PM, said:

The User Partition Format Successful normally means the disk is reset to defaults and the BSY error is fixed. I wonder if your disk does not suffer from *something else* that cause it not to be recognised by BIOS.

The drive might not necessarily be dead in the strictest sense of the word, but the symptoms is not caused by the BSY bug, since everything has been reset to defaults and error codes cleared, but the symptoms still persists. It might be something simple like a SATA data connection that doesn't make contact for some reason or something more serious that cause the drive not to be recognised by BIOS.

[jaclaz]

Huygens, on 13 December 2011 - 11:21 AM, said:

jaclaz, on 13 December 2011 - 10:50 AM, said:

Once you set apart the spite, Gradius collected and translated some info, while Aviko knows what he is talking about ...
This is among the reasons why the tutorial by CarterinCanada is advised (by me), it may not cover all issues but it covers the specific one without any deceiving or dangerous instructions.

If we assume it's too expensive to send the bricked HD to a data recovery company:

OBVIOUSLY.
But since you (and I) have NO idea of the amount of damage that issuing such a senseless (in the sense of "since we do not know exactly what it does nor a way to undo", thus senseless) command may provoke, it should NEVER be advised, EVEN if the disk is going to be given to a PRO anyway.
I mean, the diffference between (say) 500$ (drive with problems BUT NOT with some internal tables wiped) and (say) $1000 (or NO way to recover) is too big to be underestimated.

Huygens, on 13 December 2011 - 11:21 AM, said:

What you say is that if the CarterinCanada commands plus the i4 & the F,,22 commands don't work, meaning the HD still isn't detected by BIOS, the HD should be regarded as dead?

No.
What I am saying is that we know FOR SURE that a given set of commands is capable of reviving a bricked disk IF the bricked disk is suffering from a certain given issue (actually two of them) AND IF the cause of such issue(s) derives from a given firmware problem.
We also know that in some cases the same fixing procedures, since they represent a kind of "reset" for the disk, may help also with a few different issues.
We know nothing (or not enough) about different procedures, it is IMNSHO irresponsible to suggest something that you don't know for sure what is and how it works unless you know FOR SURE that it is NOT "desctructive".
We are supposed to be here helping people solving problems, NOT inducing them to create some (see the previous issues about swapping boards, you plainly suggested something that was plainly wrong AND dangerous for the integrity of the device).

You are perfectly free to suggest everything that you think fit, as well I am free, EACH TIME you will IMHO post something dangerous or senseless or both, to SCREAM about this VERY ALOUD.

If the procedures in the Tutorial by CarterinCanada + a few other NON DESTRUCTIVE command do not work, it means that the issue is outside our (very limited) sphere of competence.


jaclaz

[mvajdi]

Hi, I hope someone can help me here and I will be very appreciated. I have done all the procedures on the link but when I try the U step(Spin up the motor) I will get another message like an error and it repeats that row of error in highper terminal. A picture of this is attached. Any idea what can cause that error?
Thank you in advance
Kind regards
Mehdi

Attached File(s)

•  SeagateTerminal test.jpg (74.37K)
  Number of downloads: 10