Barracuda Green ST1000DL002 terminal log for gurus

[Friedrich]

The drive is detected in bios after 10/15 seconds, but not in windows.
Neither in MHDD is detected (the screen remains black with a flashing white dash in the upper left corner of the screen).


Drive specification:

Code:

ST1000DL002 Barracuda Green
F/W: CC3C
Date: 12353
Site: WU

No clicking sounds, i hear head calibration.
The motor doesn't spin down.
PCB contacts have been cleaned

Terminal log, hope some of you gurus can understand what's wrong:

Code:

Boot 0x20M
Spin Up[0x000246DF][0x000246E4][0x00021889][0x000218A9][0x000218AA][0x000218AD]
[0x000218CA][0x000218E6][0x000218E9][0x000218E9]ZZZZMMMMMMMMMMMMMMMZZZZZZZZZZZZZ
ZZZZZZZZZZZZZZZZZZZZZZZMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMddddddWYWYWMMMMMMSxxx
xZWZWZWZWZWZWZWZWBBWYWYdd
Trans.

Rst 0x20M
MC Internal LPC Process
Spin Up
(P) SATA Reset

  MediaPartition:

                        Host LBA  Length    Disc LBA  Length   Start Cyl  Head
       Media Partition  00000000  00998E08  00000000  001331C1  00000000  000000
00
               MC       00000000  00989748  00000000  001312E9  00000000  000000
00
               MSP      00990CC8  00000BC0  00132199  00000178  000003D9  000000
01
        User Partition  00998E08            001331C1            000003CE  000000
01

MCMainPOR: Start:
Check MCMT Version: Current
MCMainPOR: Non-Init Case
MC Seg Disc and Cache Nodes:  40134924  40132A34
Seg Write Preamble VBM start: 000011B2 end: 000011D9
  Footer - start: 000011DB end: 00001202
Seg Read Preamble VBM - start: 00001204 end: 0000122B
  Footer - start: 0000122D end: 00001254
Reconstruction: MCMT Reconstruction Start
  Max number of MC segments 22E0
Nonvolatile MCMT sequence number 000FB664
[RSRS] 0586  DiscLba 00030548  RW_RTL FFFFFFFF
Reconstruction: Completed 1:
[MCMTWS]
MCMainPOR: MCTBufferPtr->Header.MCStateFlagsDisc = 00000041
MCMainPOR: MCTBufferPtr->Header.MCTStateFlags = 0000002A
MCMainPOR: MCStateFlags = 00000041

MCMainPOR: Feature Enabled...


MSP MainPOR:
MSP Init Metadata
     Buf Bytes/VBM 00000210  DBA Base 40000000
     Metadata size in bytes 0040
     Num Segments 005E
     Logical Sector Alignment 00000000
MSP Reconstruction
MSP Read ScratchPad Section 0000  DiscLBA 00132199  BlkSize 00000BC0  Num Segme
nts 0000005E  DiscLba 00132199  RW_RTL 000F4240
     No valid segments found

MSP MSP Main Store Verify  Reconstruction Status 10003000
     Reconstruction Status 00003000
MSP Init ScratchPad on DiscDiscLBA 00132199  DiscSize 00000178  PhyBlkLBA 00990
CC8  BlkSize 00000BC0
     Write MSP Segment   PhyBlkLBA 00990CC8  BlkSize 00000BC0  DiscLba 00132199
RW_RTL FFFFFFFF
MSP MainPOR: Complete
MSP MainPOR: Feature Enabled...
     ScratchPad restore NOT required

InitiateMarkPendingReallocateRequest for disc_lba: 00135338!
InitiateMarkPendingReallocateRequest for disc_lba: 00135339!
InitiateMarkPendingReallocateRequest for disc_lba: 0013533A!
InitiateMarkPendingReallocateRequest for disc_lba: 0013533B!
InitiateMarkPendingReallocateRequest for disc_lba: 0013533C!
InitiateMarkPendingReallocateRequest for disc_lba: 0013533D!
InitiateMarkPendingReallocateRequest for disc_lba: 0013533E!
InitiateMarkPendingReallocateRequest for disc_lba: 0013533F!
InitiateMarkPendingReallocateRequest for disc_lba: 00135340!
InitiateMarkPendingReallocateRequest for disc_lba: 00135341!
InitiateMarkPendingReallocateRequest for disc_lba: 00135342!
InitiateMarkPendingReallocateRequest for disc_lba: 00135343!
InitiateMarkPendingReallocateRequest for disc_lba: 00135344!
InitiateMarkPendingReallocateRequest for disc_lba: 00135345!
InitiateMarkPendingReallocateRequest for disc_lba: 00135346!
InitiateMarkPendingReallocateRequest for disc_lba: 00135347!
(DOS)ATI NEED: 0x00146AFC - 0x00146FCC - 0x0000045C - 0x0000045E Count 0099
(DOS) Refresh Start.
(DOS) Read Error - .
(DOS) Read Error - .
(DOS) Read Error - .
(DOS) Read Error - .

[BlackST]

Get a real diagnose with PC3000 UDMA or so then post the results.

[Friedrich]

BlackST thank you for your answer.
I do not have pc3000, it's too expensive tool, i'm not rich as you.

I need to know at least roughly where I should direct research of the fault (pcb, firmware, or internal damage).
Thanks.

[Doomer]

I need to know at least roughly where I should direct research of the fault (pcb, firmware, or internal damage).
Thanks.

You need to pack it and ship it to somebody who knows what to do

[Friedrich]

Someone of you never seen such a thing in terminal?

[dmarques]

I think a lot of people here already saw that kind of terminal messages, but as you understand, will not give you any step by step guide into solving the problem, by 2 reasons as I understand, the protection of your data and the protection of their business.

[freakzy]

Someone of you never seen such a thing in terminal?

Each & everyday..... I love these new models

[BlackST]

I think a lot of people here already saw that kind of terminal messages, but as you understand, will not give you any step by step guide into solving the problem, by 2 reasons as I understand, the protection of your data and the protection of their business.

Sometimes it is not possible to earn money giving services only with hyperterminal and MHDD.
If drive/data is personal (and let me have a doubt) , dmarques has already pointed out what the problem is.

P.S. I'm not exactly RICH, but if you think I really am, guess how I became so .

Good luck.