ST500DM002 stays busy

[outbreak198x]

Hello,

i'm not able to get this ready
Sounds good. - looks good
but never gets ready:
Can not Ctrl+Z - no terminal command accepted.
Tried shortening - nope - tried another pcb - nope

Boot 0x10M
Spin Up[0x00000000][0x0000B67C][0x0000BA10]
Trans.

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

Any Ideas`?

[outbreak198x]

ohh.. i'm so bad - found another Post with same problem, maybe i had wrong shorting channels or something like that, i'll try

[data-medics]

Usually you have to time the shorting of the read channel just right on these. You can't do it before or right at power on, but rather a few seconds after. Then as soon as you've got terminal access, get in and disable everything in System file 93.

Have fun!

[jermy]

like "data-medics®" said there is an exact timing needed to short the read channels
see here Where and how to short Seagate F3 drives

[outbreak198x]

yes thx, i got this - just had wrong channels, no i've done the "No HOST IS-Ready Status Flags" procedure. drive spins up "normally" - having Initiatemarkpendingreallocaterequest for disc_lba now

reading ID and SA is OK, saved everything so far i can.

but on all sectors he means "UNC" and black block...

what i've forgotten?

[data-medics]

Did you disable everything in system file 93 like I mentioned?

[outbreak198x]

i disabled everything yes, but if i turn off an on again it's here again, but pressed write.

[outbreak198x]

ok now no more of this warnings after saving second sys 93..., but still can not clone data with DE

[outbreak198x]

Thx to jermy - after rewriting sysfile 28 - everything OK again...

[data-medics]

Good to hear that it's working now. Often with these you only get to do one operation per power cycle and only within a few seconds of it coming ready. Sometimes you'll need to read/modifly the file, power cycle, possibly short read channel again, and then write the file. You'd be surprised how often they go unresponsive between reading system file 93, and trying to write it back.

[osity]

Im having this exact problem data-medics describes. I too discovered that the only way to read/write sys files is to turn of/on the drive with a small 1-2 second windows after initialization. I've already unchecked all items in sys93 and that only solved it for a few minutes but now it back to staying BSY again. What can I try? I also noticed there are many sys93 files listed.