Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

Seagate BSY state.. Can it go away, and come again another day?!

- - - - -

  • Please log in to reply
4 replies to this topic

#1
hunted22

hunted22
  • Member
  • 5 posts
  • Joined 06-May 14
  • OS:Windows 8.1 x64
  • Country: Country Flag

Hello all

My Maxtor DiamondMax23 STM31000528AS (Maxtor's version of ST31000528AS) had a problem during firmware update, which left it undetectable, although it spins, with a delay when PC boots. BSY state, right?
Well, the drive had this issue for a year. During this year I tested the drive several times on different PCs. Always the same except two times I powered up the PC to find that the driver was detected and functional, and I successfully updated the firmware the 2nd time. but both times after a while of operating the PC, Windows crashed, and the drive went back to the bricked state.

Anyone has any advice here? Does this mean that BSY is ruled out as the problem and fix?

PS1: The drive never had any problems or physical damage before or since the issue. Also SATA controllers, cables, etc. are not causing the issue.

 

PS2: I'm not trying to recover my data. I'm just trying to salvage the drive itself as a project in my free time. HDDs are kinda expensive here.

 

Thanks in advance


Edited by hunted22, 17 January 2015 - 07:37 PM.



How to remove advertisement from MSFN

#2
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,998 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

I guess that you are somehow mixing the effects with the cause.

The BSY or "busy" state is a symptom (or effect) of an illness (cause).

If a disk gets onto BSY state, it is because *something* in not working and causes this state.

I am sorry I don't believe you :w00t: :ph34r:, in the sense that you missed to detail something that happened (or missed to notice it), it is the first time I hear of a Seagate 7200.1x (please read as Maxtor DiamondMax2x) spontaneously going into BSY state and then "randomly" exiting it (and later "randomly" re-entering it), I mean, there must be *something* that is not affected by or connected to the firmware update that causes this behaviour. :unsure:

The BSY state could be the result of n different issues, but unfortunately we don't have a way to diagnose it (if not running the Seagate Short and Long tests, which however will only tell if the disk is "good" or "bad") and thus no real way to pinpoint the cause  :( , all we know is a procedure that can exit the BSY state and "recover" the drive IF the cause is the known firmware bug or more generally a procedure capable of getting the drive out of it (and then in the case of the original issue the "final fix" is the updated firmware)

jaclaz



#3
hunted22

hunted22
  • Member
  • 5 posts
  • Joined 06-May 14
  • OS:Windows 8.1 x64
  • Country: Country Flag

(I could swear that I already responded to jaclaz's post couple days ago and saw my replay posted!!.. weird..)

There is not much to miss really. The drive spend most of the time in a drawer except for the few times I took it out to test. the only thing I could add is that the drive had a few bytes of bad sectors, but nothing else.

 

The issue I'm having right now is that I can't establish a terminal connection with the drive. I was trying to get a post from the terminal (without actually tying the fix. not yet.). I'm using a USB-TTL PL2303HX adapter, the drive is connected to the adapter with GND,TX,RX wires, and using an external PSU to power up the drive. My setup has passed the loop test. but when connected to the drive I get no response at all.. like I don't even get the F3 T> prompt when pressing Ctrl+Z. Checked all the connection and they are OK. switched RX and TX wires, no change.

As I understood, 7200.11 PCB should be isolated before the fix, while in 7200.12 drives read channels should be shortened. I haven't done any of these thing as I'm only trying to get a terminal report. Could this be why I can't get any terminal response?


Edited by hunted22, 23 January 2015 - 12:58 AM.


#4
hunted22

hunted22
  • Member
  • 5 posts
  • Joined 06-May 14
  • OS:Windows 8.1 x64
  • Country: Country Flag

Bump...



#5
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,998 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

(I could swear that I already responded to jaclaz's post couple days ago and saw my replay posted!!.. weird..)
 

Which is good, as jaclaz could swear that he replied to that reply :w00t:, most probably a glitch in the matrix :ph34r: (there have been a few issues with the board in the last few days):

http://www.msfn.org/...slow/?p=1092824

 

Till now we don't know if your disk is in BUSY state or not.

You should try to check with mhdd or hdat1 or victoria to make sure that it is (or it is not).

 

IF the disk is in BUSY state, it won't communicate properly through the serial (hence the need to "force" a "loop exit" by generating a hardware error, i.e. insulating the PCB contacts, the head ones, or the motor ones or both and/or additionally shorting the Read Channel, depending on models and situation).

 

Imagine that the disk is running DOS and an endless loop batch was started.

You need to press CTRL+C to stop the execution and get to command line, BUT IF BREAK=OFF was specified:

http://www.computerh...om/breakhlp.htm

you cannot anymore, but if you generate a hardware error execution may well be stopped....

 

There is however a difference between the insulating of one or the other (or both) the contacts and the Read Channel shorting, the first is to access the interface, the second is a way to avoid that a specific command enters another loop of it's own.

 

jaclaz


Edited by jaclaz, Today, 02:41 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users