Model : ST_M13FQBL

[datacare]

Anybody having the solution for the following issue

Model : ST_M13FQBL
Serial : QNR_BFW
Firmware : 04081508
Capacity : 3.86 GB (8 089 950)

Original Model is ST3500413AS-FIRMWARE JC4B

With regards
sundar

[ACE_Admin]

Hello Sundar.

This kind of drive identification is taken from hard drive's ROM. This usually
appears in the situation where some part of drive is not functioning good.
Tell me if there is any "Terminal" tab output after you power up the drive is displayed?

Most likely you will need to get a donor drive for that case.

[datacare]

Thank you very much for your reply.

There is nothing in Terminal

With regards
Sundar

[ACE_Admin]

This kind of output says that drive is not able to reach anything from surface. The id is taken from ROM's template.

Necessary overlays and other things are not accessed due to problem logic board or heads stack.
Usually we advise standart procedure:

1. get a same model drive working logic board and install patient ROM chip on it. Then try this board with your patient
if the problem was only with logic board, then drive will start working if not, then
2. make a heads stack transfer from donor drive with its magnets

[AJ2008]

Does the spindle stop after DRDY is reached?

[betty]

Hello AJ2008

Today I have a same problem. But After the DRDY reached , spindle is still working .

(I heard that ,some Chinese tools have solutions for the same problem ).
NB: When I change the PCB then only i got this message. ie, ST_M13FQBL is with new PCB without changing the ROM of Patient.

Other wise Hdd is showing Busy State.

Any solution for this Model: ST500DM002
Firmware: KC48


Betty
Crystal

[AJ2008]

When you see ID of 'ST_M13FQBL' this means ID cant be read from SA and instead some information from ROM is showing.

This happens when heads cant read SA because of mechanics problem, or when SA cant load due to some other error. You should try to short read channels at right time to maintain T> at terminal, then you can make some diagnostic checks.

[rezafarah]

my terminal reply is this:

MSP Read ScratchPad Section 000F DiscLBA 001322CB BlkSize 000009E0 Num Segments 0000004F DiscLba 001322CB RW_RTL 000F4240
Starting LBA of RW Request=001322CB Length=0000013C
ProcessRWError -Read- at LBA 001322CB Sense Code=43110081
ERC TO exceeded, orig value in us:FFFFFFFF
MSP LPCDiscXfrScratchPadSegment detected ERROR: StateFlags 00000600 DiscLBA 001322CB
MSP Reconstruction: EXCEPTION: Read ScratchPad Section 0000000F
MSP Reconstruction: EXCEPTION: Read MSP Segment Error
Segment 000FStartLBA 00991658 ErrorLBA 00991658
Error in MSP Header
Continue MSP Read, PreError Segment Cnt0000
Num Segments 005E
No valid segments found

[AJ2008]

How long do you wait at terminal window? Sometimes they can reach ready state after a long time

[rezafarah]

AJ2008
after 30 second i see the DRD DSC.
after that i can use F3 command but i can not fix the size and access to SA and also if i use regenerate translator it goes busy!

[pclab]

Today I was trying to help a guy whos got a drive with the same failure.
It goes RDY but nothing on terminal.
I see many topics over this problem.
Is there any conclusion of what's the faillure?
Heads or PCB?

[AJ2008]

It means SA isnt read. Could he heads, or PCB. It is not specifically a symptom, it is where SA cant read and ID values load from ROM.

You need to properly diagnose it. If it shuts down motor then comes ready with this ID then it could be some hardware error. If it is present after DRDY and remains spinning then you probably need to short read channels to get T> (usually at this stage with this ID T> is not possible) and you can look into possibility of defective translator etc.

This specific is comparable to the 'XYZ' ID on some WD drives such as Hawk.

[pclab]

Thanks AJ.
I'll Check that.