Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
Post a reply

Re: Maxtor (seagte) DiamondMax 23 Burnt?

November 21st, 2010, 0:36

The reset pin on a microcontroller is usually held low while the power supply is starting up. After the supplies have stabilised, then the reset pin is released. A typical arrangement might use a capacitor and series resistor to set the time constant. Others may use a special purpose supervisor IC. However, I believe hard drive MCUs are under the supervision of the motor controller IC which generates a POK (power OK) signal when the supplies are within spec. This is discussed in the L7250 datasheet.

If you are intent on probing your board, then measure the Vcore and Vio supplies. Look for 1.2V, 2.5V (or 3.3V), and a negative supply for the preamp. The top two coils should provide convenient test points, as well as the jumper block, and the supply pins of the RAM and EEPROM. I suspect that the negative supply may be present on one of the pins of the 8-pin chip to the right of the third coil.

Re: Maxtor (seagte) DiamondMax 23 Burnt?

November 21st, 2010, 10:50

Schematics disagree...

Re: Maxtor (seagte) DiamondMax 23 Burnt?

November 21st, 2010, 12:10

Thanks fzabkar, i'm on it :) , very helpfull informations.

Re: Maxtor (seagte) DiamondMax 23 Burnt?

May 2nd, 2011, 13:53

BlackST wrote:
momo2010 wrote:I would like to add this session of ASCII Debug mode for the how spin but not access:

Rst 0x10M
Servo Processor Is Reset.
RW: Disc Ctlr Initialization Completed.

ExecuteSpinRequest

No HOST FIS-ReadyStatusFlags 2002B001
ASCII Diag mode

F3 T>/2

F3 2>Z

HighPowerMode
Spin Down Complete
Elapsed Time 0.084 msecs
F3 2>U

HighPowerMode
ExecuteSpinRequest

Spin Up Complete
Elapsed Time 3.663 secs
F3 2>/

F3 T>F712
Byte:05C1: Expansions =
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00
''

F3 T>F,,22

(D) SATA Reset

F3 T>F712
Byte:05C1: Expansions =
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00
''

F3 T>/m0.2.2.0.0.0.0.22

Invalid Diag Cmd

F3 M>m0,2,2,0,0,0,0,22

Invalid Diag Cmd

F3 M>/

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 = not supported

DiagError 0000500D
User Partition Format Failed - Elapsed Time 0 mins 00 secs
R/W Sense 00000002, R/W Error 843200A6, File Error 00000000
Blk Addr 000000000000, Blk Addr Type 00, Cyl 00000000, Hd 00


F3 T>/1

F3 1>N1

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

Rst 0x10M
Servo Processor Is Reset.
RW: Disc Ctlr Initialization Completed.

ExecuteSpinRequest

RW subfile error 2044
RW subfile error 2044
SIM Error 2044
No HOST FIS-ReadyStatusFlags 2002A1A5

ASCII Diag mode

F3 T>i4,1,22

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 = not supported

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

F3 T>



:roll:















==================================

my hdd error message is delow

====================
Rst 0x40M
RW: Disc Ctlr Initialization Completed.

MC Internal LPC Process
(P) SATA Reset

(P) SATA Reset

SIM Error 3005
RW Error 00000080
User Data Base 00991178

MCMainPOR: Start:
MCInitialize: Start: Buffer Words VBM: 00000210
MCMainPOR: EXCEPTION: MC Init Fail. Feature disabled.
MCMainPOR: MCTBufferPtr->Header.MCStateFlagsDisc = E59FF018
MCMainPOR: MCTBufferPtr->Header.MCTStateFlags = 0000F018
MCMainPOR: MCStateFlags = 00000000

MCMainPOR: EXCEPTION: POR Failed General
No HOST FIS-ReadyStatusFlags 0002A1A5
ASCII Diag mode

F3 T>i4,1,22

F3 T>m0,2,2,,,,,22
RW subfile error 201F
RW subfile error 201F
SIM Error 201F
RW Error 00000080
DiagError 0000500E Process Defect List Error
R/W Sense 00000002, R/W Error 841C0087, List Offset 00000000, List Index 00000078, File Error 000000D0

F3 T>

==================================

how can i recover my hdd data?
is anyone can help me?

Re: Maxtor (seagte) DiamondMax 23 Burnt?

May 2nd, 2011, 14:15

Who / what suggested you to send such commands if the problem was not diagnosed properly ? :shock:

P.S. better to start a new thread instead of attaching to an existing post.

Re: Maxtor (seagte) DiamondMax 23 Burnt?

May 2nd, 2011, 22:35

BlackST wrote:Who / what suggested you to send such commands if the problem was not diagnosed properly ? :shock:

P.S. better to start a new thread instead of attaching to an existing post.



hi. i think that your hdd error message is similar to my hdd error message

your hdd error message is
-----------------------------
RW subfile error 2044
RW subfile error 2044
SIM Error 2044
No HOST FIS-ReadyStatusFlags 2002A1A5
ASCII Diag mode


my hdd error message
------------------------------
RW subfile error 201F
RW subfile error 201F
SIM Error 201F
RW Error 00000080
DiagError 0000500E Process Defect List Error
R/W Sense 00000002, R/W Error 841C0087, List Offset 00000000, List Index 00000078, File Error 000000D0

i updated my patient hdd firmware module with doner hdd'firmware
and this error message appeared

my hdd is ST2000DL003, firmware is CC31
can you help me please?

Re: Maxtor (seagte) DiamondMax 23 Burnt?

May 2nd, 2011, 23:31

Too late...
Did you BACKUP all the previous firmware and ROM ?
P.s. It wasn't my hdd !

Re: Maxtor (seagte) DiamondMax 23 Burnt?

May 2nd, 2011, 23:56

BlackST wrote:Too late...
Did you BACKUP all the previous firmware and ROM ?
P.s. It wasn't my hdd !


yes. i backuped the patient's firmware and rom.
but i can't update back to old firmware.
because it is being "busy error"

and i effort to fix the busy error like below , but failed

-------------
F3 T>m0,2,2,,,,,22
RW subfile error 201F
RW subfile error 201F
SIM Error 201F
RW Error 00000080
DiagError 0000500E Process Defect List Error
R/W Sense 00000002, R/W Error 841C0087, List Offset 00000000, List Index 00000078, File Error 000000D0

can you help me?

Re: Maxtor (seagte) DiamondMax 23 Burnt?

May 3rd, 2011, 2:20

Yes but not remotely. Note that data could have been affected, and that 'busy fix' was a really bad idea beside having nothing to do with the original problem...

Re: Maxtor (seagte) DiamondMax 23 Burnt?

May 3rd, 2011, 7:06

BlackST wrote:Yes but not remotely. Note that data could have been affected, and that 'busy fix' was a really bad idea beside having nothing to do with the original problem...


humm.. BlackST. your answer looked so bad.
you look don't have helping mind from the first time.

No Thank you your answer anymore.
do not answer like this to anyone who need help. :twisted:

and i fix the busy error today.

with help from kind another man.

Re: Maxtor (seagte) DiamondMax 23 Burnt?

May 3rd, 2011, 8:57

BlackST wrote:Yes but not remotely. Note that data could have been affected, and that 'busy fix' was a really bad idea beside having nothing to do with the original problem...
rksk707 wrote:
you look don't haveelping mind from the first time.

No Thank you your answer anymore.
do not answer like this to anyone who need help. :twisted:

and i fix the busy error today.

with help from kind another man.


I am not obliged to help everyone who come and ask (especially on compromised drives) and don't want moral or material responsability in loss of data or further damage so I help remotely / use remote desktop only with other professionals , otherwise it's necessary to see the drive LIVE.
It's good that your drive is not busy anymore, good luck for all the remaining fixing.

Re: Maxtor (seagte) DiamondMax 23 Burnt?

May 3rd, 2011, 14:21

BlackST wrote:
BlackST wrote:Yes but not remotely. Note that data could have been affected, and that 'busy fix' was a really bad idea beside having nothing to do with the original problem...
rksk707 wrote:
you look don't haveelping mind from the first time.

No Thank you your answer anymore.
do not answer like this to anyone who need help. :twisted:

and i fix the busy error today.

with help from kind another man.


I am not obliged to help everyone who come and ask (especially on compromised drives) and don't want moral or material responsability in loss of data or further damage so I help remotely / use remote desktop only with other professionals , otherwise it's necessary to see the drive LIVE.
It's good that your drive is not busy anymore, good luck for all the remaining fixing.

-----------------------------
Yes,you are not obliged to help otherman ,
but you must not make cynical remarks to anyone who need help.
it is not good and not helpful to anyone. i think
thank you for reading. and good luck, too.

Re: Maxtor (seagte) DiamondMax 23 Burnt?

December 12th, 2011, 22:37

momo2010, Hi you, I also like you. you have a fix yet? please just help:
==================

F3 1>N1

Init SMART Fail
==================
I tried the command, but failed
V4
V1

==================

F3 T>m0,6,3,,,,,22
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 16, Max Certify Rewr
ite Retries = not supported

DiagError 0000500D
User Partition Format Failed - Elapsed Time 0 mins 00 secs
R/W Sense 00000002, R/W Error 843200A6, File Error 00000000
Blk Addr 000071030001, Blk Addr Type D0, Cyl 00000000, Hd 01

can you help me?

Re: Maxtor (seagte) DiamondMax 23 Burnt?

December 13th, 2011, 0:12

, Hi you,
i"m from Recovery Viet nam
My web: http://cuudulieu.com/data-recovery.html
My chat yahoo (hope to familiarize): khoiphucdulieu
Email: datviet@cuudulieu.com
I also like you. you have a fix yet? please just help:
==================

F3 1>N1

Init SMART Fail
==================
I tried the command, but failed
V4
.............

can you help me?

Re: Maxtor (seagte) DiamondMax 23 Burnt?

September 10th, 2016, 3:00

does anyone explain the problem of
"RW subfile error 201F"
Post a reply