ST1000DM003 - BSY

[gtd4242]

I have a 1TB Seagate that is staying in a BSY state. However, I can gain terminal access, but before I start doing anything with it in PC3K, I'm curious if anyone else has seen this type of output?

Code:

Boot 0x40M
Spin Up
Trans.

Spin Up
SpinOK
TCC:0020

SNOOOZZZZZZEEE Retry
SNOOOZZZZZZEEE Retry
MCMainPOR: Start:
User Data Base  0043E340
Check MCMT Version: Factory Init
MCInitialize: Start:  Host VBM Size (Bytes): 00000210 Metadata VBM Size (Bytes):
ClearMC: Start Full  Starting LBA 0000BA00, Count 00432940.
ClearMC:  Completed, Last LBA 000043E340
MCInitialize:  MC Cleared
MCInitialize:  MCTBufferPtr->Header.MCTStateFlags = 0000000A
MCInitialize:  MCTBufferPtr->Header.MCStateFlagsDisc = 00000001
MCInitialize:  MCStateFlags = 00000001

Set MCMT Version Current
[MCMTWS] Tail/Head 0000 0000
MCInitialize: Init complete:
MCMainPOR: MCTStateFlags 00000022  MCStateFlags 00000041  Tms 0000330D
SNOOOZZZZZZEEE Retry
SNOOOZZZZZZEEE Retry

SP200: MSPMainPOR Start
MSP MainPOR: 00003000  Tms 0000330D  00000082  0000476B
MSP MainPOR: Complete


No HOST FIS-ReadyStatusFlags 0002A1A1
TCC:0020

TCC:0020

TCC:0020

TCC:0020

TCC:0020

TCC:0020

TCC:0020

TCC:0021

TCC:0021

TCC:0021

****KEEPS REPEATING ABOVE UNTIL I HIT CTRL-Z****

ASCII Diag mode

F3 T>


I do have access to some commands. For example, I can check for non-resident G-list without an issue...

Code:

F3 T>V40
Nonresident GList                    0 entries returned
Total entries available: 0
          PBA           Len  Flags  Phy Cyl Hd  PhySctr    SFI

F3 T>


So it doesn't seem to be completely locked up, but it does stay in a constant BSY state, and I'm not sure what might be the proper method for getting out of this BSY condition, given the terminal output that is presented.

If you have any ideas, please feel free to PM. Thanks!

[data-medics]

It's probably just an issue with the media cache or sector reallocation functions as it usually is with this series.

You'll probably need to modify system file 93 to disable everything.

[gtd4242]

Ended up being a translator issue. Backed up all the critical modules, regenerated the translator, and all is well.