Jump to content

Seagate ST2000dl003


Recommended Posts

Helllo

my Drive was not found anymore on my computer!

I read much bout firmware problems.

I build some parts to contact the drive,

Here is the output of putty:

Rst 0x40M

RW: Disc Ctlr Initialization Completed.

MC Internal LPC Process

(P) SATA Reset

User Data Base 00991AE8

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 00004548

[RSRS] 09EF

Reconstruction: EXCEPTION: Segment Overall Sequence Number Mismatch

00001BA4 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

Can anyone help me ?

What commands i had to type?

Link to comment
Share on other sites


  • 1 month later...
  • 1 year later...

I have ST2000DL003 with firmware CC98. When i connect to PC it takes a while show it self for few second , after few second it will make itself inaccessible. i connected to serial console to get rid of bsy error because it spins continuously . When i place card on motor or head terminal it will not respond but if i connect to serial console without placing car it show following

Rst 0x40M

(P) SATA Reset

and shows FT> prompt when i press ctrl+z

Can someone please help me what to do from this point onward?

Link to comment
Share on other sites

Can someone please help me what to do from this point onward?

The ONLY set of instructions we have are here (and they are not validated by any other member, so more than the usual YMMV :ph34r:)

(already linked to thread):

specifically the quote in this post:

jaclaz

Link to comment
Share on other sites

I completed all the steps but drive is still in busy state, continuous spinning

here is the log

Rst 0x40M

(P) SATA Reset

ASCII Diag mode

F3 T>

Banshee Bogart, RAP17, add 6k SAP csys 4K QNC

Product FamilyId: 4F, MemberId: 02

HDA SN: 5YD3CMXZ, RPM: 5939, Wedges: 1F8, Heads: 6, OrigHeads: 6, Lbas: 00001D326C41, PreampType: A8 15

PCBA SN: 0000K1364D7E, Controller: BANSHEEST_2_0(8000)(4-00-0-0), Channel: Unknown, PowerAsic: MCKINLEY DESKTOP LITE Rev 91, BufferBytes: 4000000

Package Version: BGC15D.CCD9.AAB600.CC98 , Package P/N: 100655416, Package Global ID: 00188399,

Package Build Date: 01/05/2011, Package Build Time: 13:03:40, Package CFW Version: BGC1.CCD9.00310163.00188399,

Package SFW1 Version: D556, Package SFW2 Version: ----, Package SFW3 Version: ----, Package SFW4 Version: ----

Controller FW Rev: 01051303, CustomerRel: CC98, Changelist: 00310163, ProdType: BGC1.CCD9, Date: 01/05/2011, Time: 130340, UserId: 00188399

Servo FW Rev: D556

RAP FW Implementation Key: 11, Format Rev: 0302, Contents Rev: BB 03 09 00

Features:

- Quadradic Equation AFH enabled

- VBAR with adjustable zone boundaries enabled

- Volume Based Sparing enabled

- IOEDC enabled

- IOECC enabled

- DERP Read Retries enabled

- LTTC-UDR2 compiled off

Edited by fjaved
Link to comment
Share on other sites

Yes , it respond to all commands perfectly. Do i need to short the pins? If i place card under pcb to block access to motor or head it will not respond, so i am connecting without placing any card .

Edited by fjaved
Link to comment
Share on other sites

Yes , it respond to all commands perfectly. Do i need to short the pins? If i place card under pcb to block access to motor or head it will not respond, so i am connecting with placing any card .

No.

You are not in the same situation as described in the mentioned thread.

In that situation the firmware enters in a kind of loop, doesn't accept commands, shows continuoausly a LED:00000xyz FAddr:0000mnop kind of error and detaching the board (completely and/or just the head or the motor and - in some cases shorting the read channel) is a way to exit that loop and make the interface accept the commands.

The whole point, in your situation, is that we don't know WHICH commands (if existing at all) may correct the issue that makes the drive spin continuously and be BSY.

The "common" issue is a continuous loop of the firmware that creates the BSY state, your particular one is evidently - while still a BSY - caused by "something else".

You have to understand that all we know are "crumbs" :w00t: , see:

jaclaz

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...