7200.12 ST3750528AS BSY problems.

[mondrian]

I have a ST3750528AS FW CC46 in which seems to have the BSY problem. When attached to DDI SA is read with correct Model Serial and Size, but hangs with BSY until it powers down. MHDD also recognizes it but the drive disappears after any command to it.

Terminal output is as follows:

Code:

Rst 0x20M
Servo Processor Is Reset.
RW: Disc Ctlr Initialization Completed.

ExecuteSpinRequest

(P) SATA Reset


V40 shows no NRG listings so I shorted RW and tried m0,2,2,,,,,22 shorting method as per viewtopic.php?t=18907 but there seemed to be no difference. I see some mentions of m0,6,3,,,,,22 around but I want to get some understanding before I continue throwing commands around. Any ideas?

[data-medics]

I just did one of these that would keep getting stuck busy whenever you attempted to change levels in terminal. But every time it was power cycled, it could access sectors until it hit a bad one. Took about 100 power cycles, but I got it imaged that way.

Here's the thread where I was talking about it: http://www.data-medics.com/forum/viewto ... f=26&t=220

[mondrian]

Unfortunately (or rather fortunately) terminal access seems fine. I can traverse levels, and commands seem to work OK. The drive seems to Ready once after reading SA and any attempt to read user data ends up hanging on BSY and eventually powering down. I would be fine with having to re-power a bunch of times as long as I could get data out

[mondrian]

Perhaps I am wrong. I was using terminal cable with only Power supplied. When I connect terminal while drive is connected to DDI, Terminal commands do in fact freeze. It will read SA once it seems, and as long as no other commands are sent, terminal access is fine. Once User area is read, I get

Code:

(H) Sata Reset

and then Terminal Freezes.

[mondrian]

Alright, a couple of new insights. I am relatively new to the Seagate Terminal interface which probably means I know just enough to be dangerous.

The output of commands looks extremely similar to viewtopic.php?f=1&t=30473 based on two main things:

The user defect list (F3 T>V1) goes on *forever* and upon entering Online mode, I receive a bunch of repeating

Code:

InitiateMarkPendingReallocateRequest for disc_lba: 0000000000CB2AF7!.
(DOS) Read Error - 43110081

after DSC DRDY while it is BSY.

This leads me to believe it is a p-list corruption, possibly from trying the m0,2,2,,,,,22 command earlier and N1 reset?

[mondrian]

Using the information from the previous post, I decided to try to Disable reallocations and retries as described here.

I cannot explain the joy that came to me once I saw the drive ready and then ready again. It is currently scanning with absolutely no problems, hoping I can make it to the end of the drive before chucking this bad boy out of the window.

This has been such a fun ride.

Based on what I have come across so far, just trying to get an understanding of what happened, is it correct to say that the plist was corrupted and that disabling reallocations allowed the drive to not try to read the list and therefore not hang up?