Hi! hddgurus, I had been reading your forums for some time and using the information posted to repair some Seagates drives with bsy error.

But now i had one that does something that is new to me.

First i thought that it was an usual BSY fail, but, in bios it can't be detected (no lba, no 0 size...), the same as in Windows 10 pro and device manager.

Sometimes when it is attached to the computer, it makes the computer to take a loooong time to start, around 3-4 minutes to do the POST and around 10 more to boot (my computer has an ssd and the entire proces uses to take 30 sec)

And the more strange thing. The first time I had pluged it... it works! well, it was shown in device manager, appears on my computer, and a window show the folders on the root. When I had tried to open a folder this made the explorer to become unresponsive, and opening the properties on my PC has done the same. so i cant do

In fact all i can say (whithout conecting the drive to terminal (i cant find the usb to ttl, so probably i will buy a new one)) is the same as posted here: http://forum.hddguru.com/viewtopic.php?f=1&t=18907

Stated in the post is said to PM ROb for the solution, but i dont want to disturb him if it can be easy solved.

The drive data:

Barracuda 7200.12 1 TB
S/N: 9VP5HGVK
ST31000528AS
p/n: 9SL154-302
Firmware: CC38
Datecode: 10366
Site Code: TK

The drive never dropped. When initializing it does not make any strange sound, clicking...
The drive failed months ago, but i started to working with it now (may be related with it to be recognized for a moment in the computer).
The board doesn't shows any burn spot or smells burnt

Thanks in advance!

Hi,
if your drive is still detected from your computer bios and in windows (even if sometimes) i would say problem most likely is bad surface or bad heads or both.
If it was in busy state you wouldn't be able at all to make it detectable even in the bios.

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

Thanks for your response.

That is one of the things I'm thinking, just im worry because would be great to recover the data, but is not essential.
In the other hand, there is any chance to make the disk work again? Just for store movies on the TV or something with non essential files?

Ps: sorry for my poor English.

Hi!
Im using USB to TTL PL2303HX based coverter. The board is isolated from the drive with a piece of paper.

This is what i got when connecting it and using Putty



any idea of how to proceed?

I dont want to wrong proceed with the BSY fix

Many thanks

Ok, as i dont worry about that data and by now the drive is just a paperweight i throw it to the pool and try to use de BSY fix, and this is what returns..



Any idea or advise?

thank you very much

No HOST FIS-ReadyStatusFlags 2002B001 --> problem maybe with the translator loading.


the most likely cause, bad heads/surface.



PS: This is not the correct sequence to busy fix in this model, and if you continue along this path, without checking the NRG -List will probably have a nice paperweight

Ok i wont continue that, but any clue about how to solve it?

Before giving any command that would make things worse, at the moment is safer if you give only some disgnostic commands so that we can figure out what's wrong!

Show us defects list by inserting the following commands...
F3 T>V1

F3 T>V2

F3 T>V4

F3 T>V8

F3 T>V10

F3 T>V40

F3 T>V80

Save log in TXT file and upload it on forum.

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

hi there
this is Sequence for solve your problem

1- check NRG List by V40 if it empty continue to other sequence
if not Clear NRG then continue

2- m0,6,2,,,,,22 to Regen translator
3- m0,2,1,,,,,22
4- /1N1 for smart Clear

then tell me result
also if you need remote help you can PM me

_________________
http://www.hpwlab.com

hpw333
you think is necessary to "play" with the translator ?


+1

colanco i agree with you, translator regeneration command is one of those that can make things worse, as i wrote on my previous post.
DO NOT enter the commands that hpw333 reported until we don't know what's wrong with the drive, if translator is good but the problem is bad surface or bad heads (or both) then you can make things worse.

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

also may be heads no prb
and test head is easy for determine are heads bad or no

_________________
http://www.hpwlab.com

if V40 is empty no prb to regen translator
read command carefully
and he can test heads R&W by terminal to check bad heads
not so difficult

and also if V40 have entries can clear it to avoid partial access

_________________
http://www.hpwlab.com

smart module is damaged

Init SMART Fail
LED:000000CC FAddr:0024E481
LED:000000CC FAddr:0024E481

This only indicates that the process failed to initialize SMART. Not that this damaged


V1 would tell us if the translator is loaded, and if the head can read SA

What if the Prolema is damaged heads or sectors in SA ?

Bring drive to closest/cheapest/whatever (but professional enough) DR company/person, if data is important enough. Let me explain why. You've got one of the classical error in that drives.
"No HOST FIS-ReadyStatusFlags 2002B001" means that ovl get failed during process of SMART and couldn't form a FIS. In normal situation it can be solved by SMART/translator re-init. So you had been try to do that but got

"Init SMART Fail
LED:000000CC FAddr:0024E481
LED:000000CC FAddr:0024E481"

It means that one or both system heads can't (has problem with) write. By default drive do this operation by both system heads. Here is necessary, at least, to be able to work with FID's and heads separately. As I see, you have no any kind of tools that allows you to do that. Probably, it can be done using only TTL, but in first, I'm not sure that you are qualified enough to do that, and in second, drive conditions could be an obstacle to do that.

_________________
http://www.alfadatarecovery.com

did you see if condition for probability about may head bad or no
i need to be sure that heads or 1 of them 100 % bad not talk about if or if-else
problem have many reason
i can't tell user your heads are damaged and trash your HDD
cauz there are many reason for this problem
and FISXXXX always refer to bad translator
and init Smart Failed LED CC have Direct solution
not always mean bad head or bad smart module

and even if bad head there , it's easy to depop head now in all F3

_________________
http://www.hpwlab.com

the main question now is where is karl_azytzeen?/
why you didn't reply back to ur thread ?

_________________
http://www.hpwlab.com