ST3000DM001 NO ID BSY and Spins.

[danielholm]

Hi,

I have an ST3000DM001 7200.14 with the PCB 100664987 Rev B

Code:

Rst 0x40M
MC Internal LPC Process
Spin Up
TCC-001D
(P) SATA Reset

MCMainPOR: Start:
Check MCMT Version: Current
MCMainPOR: Non-Init Case
MCMainPOR: EXCEPTION: MCMT PRI copy corrupt
MCMainPOR:  MCMT SEC copy valid
Reconstruction: MCMT Reconstruction Start
  Max number of MC segments 0A61
Nonvolatile MCMT sequence number 003AEAA5
[RSRS] 06DB
ProcessRWError -Read-   at LBA 0000000000058B15  Sense Code=40000087
InitiateMarkPendingReallocateRequest for disc_lba: 0000000000058B15!

Reconstruction: EXCEPTION: Seg Read Fail: Status = 0000
Reconstruction: EXCEPTION: Error in Header
Reconstruction: EXCEPTION: Error in first Header disc sector

I not understand the explanations.:
Make a bridge between pin 1 and 3 ?
or pin 1 + 2 + 3 ?

This is a bridge welding or just for a moment before power the hd ??

Thanks for your help

Just short pin 1 and 3. Try from boot, during boot - pretty much just go to town with the shortening until you get access. You can use any tool to do the shortening, but do not solder.

[grig85]

what was happening when You were shorting it?
i have one like that does not click when I short it

it does not click because the shorting 18 and 16 is wrong. Maybe someone already mentioned it, but for this PCB# 100664987 short points are 18+17 for the read channel

[LarrySabo]

what was happening when You were shorting it?
i have one like that does not click when I short it

it does not click because the shorting 18 and 16 is wrong. Maybe someone already mentioned it, but for this PCB# 100664987 short points are 18+17 for the read channel

Are you sure?

[grig85]

what was happening when You were shorting it?
i have one like that does not click when I short it

it does not click because the shorting 18 and 16 is wrong. Maybe someone already mentioned it, but for this PCB# 100664987 short points are 18+17 for the read channel

Are you sure?

yellow square for read channel. I just had a drive with BSY signal, shorted right before Trans. drops in the terminal and drive comes ready and system files can be modified via Terminal without problems

[LarrySabo]

yellow square for read channel. I just had a drive with BSY signal, shorted right before Trans. drops in the terminal and drive comes ready and system files can be modified via Terminal without problems

Great! Those are pins 16 & 18, if I'm not mistaken.

[gameboybin]

Sorry for digging this up, Dealing with the same exact issue

Code:

Boot 0x40M
Spin Up
TCC-0017[0x00026F7C][0x000273E8][0x00027854]
Trans.

Rst 0x40M
MC Internal LPC Process
Spin Up
TCC-0017
(P) SATA Reset

MCMainPOR: Start:
Check MCMT Version: Current
MCMainPOR: Non-Init Case
Reconstruction: MCMT Reconstruction Start
  Max number of MC segments 0A61
Nonvolatile MCMT sequence number 00107224
[RSRS] 0080
ProcessRWError -Read-   at LBA 00000000000069FB  Sense Code=40000087
InitiateMarkPendingReallocateRequest for disc_lba: 00000000000069FB!

[SW] 0061
[SW] 002D
[SW] 002A
Reconstruction: EXCEPTION: Seg Read Fail: Status = 0000
Continuing after error
ReadFooters (Forward): Segment 0083 StartLBA 0000000000034F68 Starting Footer LBA 0000000000034FB0
  SeqNum 00107228  TotalUserBlocks 0000
ProcessRWError -Read-   at LBA 00000000000069FB  Sense Code=40000087
InitiateMarkPendingReallocateRequest for disc_lba: 00000000000069FB!

  Footer Status = 0000
  Footer Status = 0001
  Footer Status = 0001
  Footer Status = 0001
  Footer Status = 0001
  Footer Status = 0001
  Footer Status = 0001
  Footer Status = 0001
  Footer Status = 0001
  Footer Status = 0001
  Footer Status = 0001
  Footer Status = 0001
  Footer Status = 0001
  Footer Status = 0001
  Footer Status = 0001
  Footer Status = 0001
  Footer Status = 0001
  Footer Status = 0001
  Footer Status = 0001
  Footer Status = 0001
  Footer Status = 0001
  Footer Status = 0001
Reconstruction: EXCEPTION: Segment Overall Sequence Number Mismatch, No Valid Footer  00107228 FFFFEDFF
Reconstruction: ProcessIncompletelyWrittenSegment


[Amarbir[CDR-Labs]]

Well,
Did you solve this case like you read in thread ,Lots of updates have happened in seagate world since those days