Seagate Barracuda LP Green is not recognized in BIOS suddenly.

[limax]

I have a Seagate Barracuda LP Green 5900rpm HDD

S/N: 5YD15W0C

ST2000DL003

P/N:9VT166-300

F/W:CC31

Date:11243

Site:WU

after 1 year of use, last week when i take it to another PC to transfer data, it suddenly cant recognized in BIOS, i change to 3 PC, the same problem the pc is a litter longger to continue compare to a good HDD

then i google the issue and find this great Forum.

i bought the USB-TTL converter and follow the hep topic to try to fix it

ctrl-z

F3 T>

F3 T>/2

F3 2>Z

F3 2>U

F3 2>/1

F3 1>

F3 1>N1

F3 1>/T

F3 T>

F3 T>i4,1,22

POWER OFF wait 10s and POWER ON

ctrl-z

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

...

F3 T>m0,2,2,,,,,22

...

F3 T>m0,2,2,0,0,0,0,22
Max Wr Retries = 00, Max Rd Retries = 00,  Max Iterations = 00, Max Certify Rewr
ite Retries = 0000

User Partition Format Successful - Elapsed Time 0 mins 00 secs
Zone re-format was skipped.
F3 T>m0,2,2,,,,,22
Max Wr Retries = 0D, Max Rd Retries = 0D,  Max Iterations = 01, Max Certify Rewr
ite Retries = 29D1

User Partition Format Successful - Elapsed Time 0 mins 00 secs
Zone re-format was skipped.

NOW IT IS THIS STATUS

Rst 0x40M
RW: Disc Ctlr Initialization Completed.

 MC Internal LPC Process
(P) SATA Reset

 User Data Base  00991DF8

 MCMainPOR: Start:
 Check MCMT Version: Current
 MCMainPOR: Non-Init Case
 MC Seg Disc and Cache Nodes:  4011985C  4011796C
 Seg Write Preamble VBM start: 000010A7 end: 000010CE
  Footer - start: 000010D0 end: 000010F7
 Seg Read Preamble VBM - start: 000010F9 end: 00001120
  Footer - start: 00001122 end: 00001149
Reconstruction: MCMT Reconstruction Start
  Max number of MC segments 22E0
 Nonvolatile MCMT sequence number 00004D4E
 [RSRS] 0DD4
Reconstruction: EXCEPTION: Segment Overall Sequence Number Mismatch
 00001FE9 00000000
[MCMTWS]
Reconstruction Fail: Burly Case
 MCMainPOR: MCTBufferPtr->Header.MCStateFlagsDisc = 00001001
 MCMainPOR: MCTBufferPtr->Header.MCTStateFlags = 0000002A
 MCMainPOR: MCStateFlags = 00001001

 MCMainPOR: Feature Disabled...
No HOST FIS-ReadyStatusFlags 0002A1E1

IT STILL CANT BE RECOGNIZED IN BIOS, PLEASE HELP ME.

if there is some step wrong?

[limax]

add

the spin is working, seems no BUSY problem.

[dencorso]

I have a Seagate Barracuda LP Green 5900rpm HDD

... which is *not* a 7200.11.

if there is some step wrong?

Yes! You used the right fix on the *wrong* drive!

Now, it's gone ENIAC's way.

[limax]

oh...no

and if there is some methord to make it up.

[jaclaz]

Yes! You used the right fix on the *wrong* drive!

Now, it's gone ENIAC's way.

Unfortunately, yes.

For the record a thread dedicated to the "green" series does exist:

and the *NOT* confirmed method DOES HOWEVER SAY:

page__view__findpost__p__990707

DONT GIVE m0,2,2,,,,,22 m,6,2,,,,,22 OR ANY SAME

ALL THE TERMINAL LOG AS YOU CAN SEE REGARDING

"No HOST FIS-ReadyStatusFlags 0002A1E1"

IN THIS POST ARE VICTIMS OF THIS M-FORMAT COMMAND AS PER MY KNOWLEDGE

EVEN I HAVE MADE SAME MISTAKE.

The general idea is to ask for help/suggestions BEFORE doing something that is IRREVERSIBLE or that you are anyway not sure, double sure AND triple sure about..

jaclaz

[limax]

thanks jaclaz

I asked a friend for help, he just successful fixed the same issue with his 7200.11 500G HDD, he suggested me to try his way to fix my problem so i used the 7200.11 METHOD.

and being too eager to fix it, I wasn't careful enough.

thank you again.

[jaclaz]

and being too eager to fix it, I wasn't careful enough.

Yep, you did not take into account Murphy's Law.

What we don't really know is if the disk is still recoverable (by a "Pro" with tools like the PC3000 or similar), what we do knw is that "at the state of the art" it is NOT recoverable with DIY tools.

thank you again.

You are welcome .

jaclaz

[n0bby]

Seagate Barracuda LP Green 5900rpm HDD
S/N: 5YD17GBZ
ST2000DL003
P/N:9VT166-300
F/W:CC31
Date:11246
Site:WU

Used in an external docking station for 2 years HDD disappeared once and for all (not present in OS nor in BIOS).

Terminal status is:

Rst 0x40M
RW: Disc Ctlr Initialization Completed.
MC Internal LPC Process
(P) SATA Reset

User Data Base 00990B18

MCMainPOR: Start:
Check MCMT Version: Current
MCMainPOR: Non-Init Case
MC Seg Disc and Cache Nodes: 4011985C 4011796C
Seg Write Preamble VBM start: 000010A7 end: 000010CE
Footer - start: 000010D0 end: 000010F7
Seg Read Preamble VBM - start: 000010F9 end: 00001120
Footer - start: 00001122 end: 00001149
Reconstruction: MCMT Reconstruction Start
Max number of MC segments 22E0
Nonvolatile MCMT sequence number 00004063
[RSRS] 051F
Reconstruction: EXCEPTION: Segment Overall Sequence Number Mismatch

000016D2 00000000
[MCMTWS]
Reconstruction Fail: Burly Case
MCMainPOR: MCTBufferPtr->Header.MCStateFlagsDisc = 00001001
MCMainPOR: MCTBufferPtr->Header.MCTStateFlags = 0000002A
MCMainPOR: MCStateFlags = 00001001

MCMainPOR: Feature Disabled...
No HOST FIS-ReadyStatusFlags 0002A1E1

I tried softer version of "the old Barracuda way" (no formatting commands) with the terminal but nothing happened.

Having access to all terminal commands, I tried disconnecting the heads, but then there is no access to the terminal.

I read here that only enforced firmware update can save the day, but as there is no other access for me to the drive than

terminal I am wondering how could this be done with just terminal commands. Since I do not have PC-3000 nor any

device hacks I could use, maybe my second fully operational Barracuda drive could be a solution.

What I am thinking about is physically replacing the ROM chip from the bricked drive to the PCB of the operational drive

and replacing the PCB. Do you think this could work?

Edited February 12, 2014 by n0bby

[submix8c]

Ahem... Post #5? Did you read this whole thread or just decide it was good to bump?

Quite sure that jaclaz will be along soon. (Thinking, though, that the answer may be maybe )

[n0bby]

Hi there,

Well, my think reading good so yes, i did the job, below from quoted by jaclaz procedure

...DONT GIVE m0,2,2,,,,,22 m,6,2,,,,,22 OR ANY SAME
ALL THE TERMINAL LOG AS YOU CAN SEE REGARDING "No HOST FIS-ReadyStatusFlags 0002A1E1" THIS IN THIS POST ARE VICTIM OF THIS M-FORMAT COMMAND AS PER MY KNOWLEDGE EVEN I HAVE MADE SAME MISTAKE...

...so I DID NOT do the formatting part.

Thanks for the reply, I hoped this place not to be dead, but it seems Seagate brilliant boys have managed to keep us all very active

Edited February 12, 2014 by n0bby

[jaclaz]

Do you think this could work?

No. (meaning that I do not think that this could work, nothing more, nothing less).

I have no idea how much (or what) is stored in the actual ROM chip and how much (or what) is stored on the actual HDD platters, but common sense tells me that it is not a good idea to do that ROM swapping, as there is no evidence of any kind of a failure of some electronic component on the PCB (which would be the normal reason for a PCB and ROM swap).

Specifically the cited reference:

http://www.hardmaster.info/news13/13-13-2013.html

links to an older post from the same Author:

http://www.hardmaster.info/news11/15-06-2011.html

where I seem to read that (via Google translate):

On the forums, there were reports that the problem is in the electronics board and supposedly someone even get access to user data by replacing the motherboard with a known good. The fact that a similar problem have hybrid drives Seagate, with on-board electronics chip NAND Flash and thus in some way by combining technology and classic SSD drives. In the portion of the hybrid SSD HDD stores the most frequently used pieces of FS, such as a table MFT.

But described in this article drives the problem is not the board with a known good replacement does not lead to success, while the broken board with disk works fine on the disc proper.

jaclaz

[n0bby]

Thanks for Your immediate response jaclaz

I assume Your diagnosis does not leave me much hope for home solution to the problem.

Since that russian guy strongly suggests something is messed up with the microcode

of the drive, and recommends updating the firmware over, maybe one day an instruction

how to do that is released, unless of course data recovery pros want to keep it mystery

Greets all,

n0bby

[jaclaz]

Yep, unfortunately NO dice .

An IMHO lesser known possible resource is this newish Forum:

http://malthus.zapto.org/index.php

basicaly a handful of (advanced) "amateurs" , already members of the reknown hddguru forum (in practice ALL the good guys over there ) took the plunge and (after having been told for countless years, over and over - and over again - how a professional is needed always and anyway) started this new Forum.

Seemingly only one or two of the "professionals" joined there (still posting again and again the same thing), so the place is - unlike hddguru - very friendly.

Of course there is not (yet) much info (and unfortunately even the info available is still largely cryptical/unexplained/unexplicable ) , but that would be probably the best place to ask for help or to keep an eye on for future developments.

jaclaz

[n0bby]

Hi there,

Once again have I read something that encourages me to do what I previously had planned.

Look here please.

Is this promising or what?

n0bby

[jaclaz]

Hi there,

Once again have I read something that encourages me to do what I previously had planned.

Look here please.

Is this promising or what?

n0bby

I am failing to see which kind of "news" the provided link imply?

Can you explain?

jaclaz