Gradius2

The Solution for Seagate 7200.11 HDDs

4,868 posts in this topic

I set things up on a PC here at work that had a serial port, thereby removing the need for the USB to Serial adapter. With that done I received the prompt and was able to successfully recover the drive!!!

I'm not well versed in electronics. Perhaps the USB to Serial adapter was the problem or maybe it was causing a grounding problem, I don't know. I do find the the text regarding what needs to be grounded a bit confusing. To help anyone else having problems does it mean that the ground pin on the hard drive also has to be connected to the GND of the Rs232 to TTL adapter?

Thanks

0

Share this post


Link to post
Share on other sites

To help anyone else having problems does it mean that the ground pin on the hard drive also has to be connected to the GND of the Rs232 to TTL adapter?

YES. :)

I really cannot find what is the deceiving part in:

7. GROUNDING:

Since, as seen above the actual 0's and 1's are obtained by a difference of voltage relative to 0V, it is VITAL, to ensure that TTL level communication works as expected, to have the same 0 V level on ALL equipment involved.

This is obtained by connecting ALL the 0 V or "Ground" of ALL devices involved together (normally and by convention a black wire is used).

I will repeat myself, you NEED a (black) wire connecting:

  • the HD "Ground" pin
  • the (standard PC) Power Supply black wire
  • the converter "Ground" or 0V pin or connector or wire
  • if a battery is used, the - (minus) side/pin of it
  • if a separate Power Supply is used, it's black wire or 0V pin or connector or wire

In other words, ANYTHING marked "GND" or "GROUND" or "-" (minus) or having a black wire should be connected together.

The idea is to create an equipotential "zero", this post by VideoRipper may help understanding the possible problem:

http://www.msfn.org/board/index.php?showtopic=128807&st=2949

as well as point #6 of the read-me-first:

6.SERIAL Voltage and TTL levels:

Serial communication basically works by sending bits as voltage peaks separated by a time interval.

RS-232 sends a "0" by means of a "high level" from +5v to +15v and a "1" by sending a "low level" -5v to -15v.

The above is called "negative logic" (0=high;1=low)

TTL/CMOS sends a "0" "low" when between 0.2 V and 0.8 V and a 1 "high" when between 2.0 V and 5 V

TTL sends a "0" "low" when between 0.35 V and 0.8 V and a 1 "high" when between 2.0 V and 3.3 V

The above is called "positive logic" (0=low;1=high)

Each circuit/board may use a narrower (or wider) interval for the "high" level, but the "low" level is so narrow by design that having the SAME 0 V level on ALL equipment connected is VITAL. (see below "GROUNDING")

If you have an idea or a more accurate wording to better convey this info, please post it (or PM me) and I'll modify the read-me-first.

jaclaz

0

Share this post


Link to post
Share on other sites

Hi all,

thank you for this great post.

Yesterday morning I turned on my pc and the BSY issue came up. I tried contacting Seagate but they said there is no bug, until I finally found many posts on the web.

I've tried searching on the thread without success so excuse me in advance if my question has already been answered.

I have two ST3500320AS, only one of which is currently facing the BSY issue. I'm only interested in recovering data from the dead drive.

What happens if I replace the PCB of the dead drive with the one from the working drive? Is the dead one coming back to life? They are same model and have same firmware.

Thank you.

Ciao!

Max

EDIT: I found some posts of people asking the same question but I found no answers :-(

Edited by mlamagna
0

Share this post


Link to post
Share on other sites

What happens if I replace the PCB of the dead drive with the one from the working drive? Is the dead one coming back to life? They are same model and have same firmware.

What SURELY happens is that your drive WILL NOT come back to life.

Additionally you risk that EVEN the now working drive WILL NEVER come back to life. :ph34r:

The procedure called in jargon "PCB SWAP" can work:

  • easily on drives that have NO specific calibration/setup data (very, very old ones)
  • anyway on drives that have calibration/setup data in a eeprom (BUT you need to either backup and restore the eeprom or physically de-solder it form the old PCB and re-solder it on the "new" PCB)

It CANNOT work on drives where calibration/setup data is stored on the actual hard disk reserved sectors, such as the 7200.11.

Compare with (what you could have found if searching for the right keywords):

http://www.msfn.org/board/index.php?showtopic=128807&st=1821

http://www.msfn.org/board/index.php?showtopic=128807&st=2173

http://www.msfn.org/board/index.php?showtopic=128807&st=2240

And with:

http://www.msfn.org/board/index.php?showtopic=145290

Basically, every few tens posts comes a new guy thinking that the rather complex procedure this thread is about can be bypassed easily with a plain PCB SWAP, and someone, usually yours truly :), has to convince him that it won't work....:whistle:

So, NO, you need to use this procedure, there are no known workarounds.

Start from here:

feel free to ask for help should something be not clear.

jaclaz

0

Share this post


Link to post
Share on other sites

What SURELY happens is that your drive WILL NOT come back to life.

Additionally you risk that EVEN the now working drive WILL NEVER come back to life. :ph34r:

Hi Jaclaz,

thank you very much for the explanation. Actually I used the wrong search words (I used "replace PCB" "working PCB" etc.)

For sure I don't want to make things more broken than they currently are so I will try going with the standard procedure and let you know the outcome.

Ciao!

Max

Edited by mlamagna
0

Share this post


Link to post
Share on other sites

Just registered to say thanks to all that contibuted to this fix.

Also want to add that this fix was applied to a ST31000528AS which is a 7200.12 drive with firmware version CC35.

I am currently looking to see if there are any firmware updates for this drive, can anybody post information relevant to this?

0

Share this post


Link to post
Share on other sites

Hi

anyone please guide me...

Can we use this RX TX method with other Seagate SATA drives as well?? ( I mean, with Seagate Momentus 5400.6 SATA Drives)

Or we should perform this tricks only on Seagate 7200.11 drives only?

Please guide me

0

Share this post


Link to post
Share on other sites

Hi

anyone please guide me...

Can we use this RX TX method with other Seagate SATA drives as well?? ( I mean, with Seagate Momentus 5400.6 SATA Drives)

Or we should perform this tricks only on Seagate 7200.11 drives only?

Please guide me

Question: Guess why there is a read-me-first? :unsure:

Answer: To avoid having to reply to the SAME questions asked n times before (and also answered n times before)

Please READ it:

EXPECIALLY ponts #1 and #2

jaclaz

0

Share this post


Link to post
Share on other sites
Can we use this RX TX method with other Seagate SATA drives as well??

If you mean "Talk" to other Seagate drives: yes :yes:

And for (older) PATA drives you'll have to connect the convertor to these

pins (and try slower rates, like 9600 Baud):

seagate_pata_diag.png

If you want to know if the "Tricks" in this thread also applies to other

types of (Seagate) drives: read Jaclaz' comment above. :unsure:

Greetz,

Peter.

0

Share this post


Link to post
Share on other sites

Hi

anyone please guide me...

Can we use this RX TX method with other Seagate SATA drives as well?? ( I mean, with Seagate Momentus 5400.6 SATA Drives)

Or we should perform this tricks only on Seagate 7200.11 drives only?

Please guide me

Question: Guess why there is a read-me-first? :unsure:

Answer: To avoid having to reply to the SAME questions asked n times before (and also answered n times before)

Please READ it:

EXPECIALLY ponts #1 and #2

jaclaz

Hi

jaclaz

Thanks for reminding me the basics. :-)

And i apologize for my mistakes. :no:

Can you please tell me the solutions for Seagate Momentus 5400.6 drives?

Because I have few Momentus drives which are not getting detected. (Basically they are USB Portable Drives, so disconnected disk from it and) I performed direct F3 T>m0,2,2,0,0,0,0,22 on it.

So disk started detecting in BIOS as well as in Windows but with no file system on it(no NTFS/FAT32). So when i further diagnose it i found non repairable bad sectors on it (I tried with HDD Regenerator).

I am not able to figure out my mistakes in this process. ( I know these firmware reset command is designed for seagate 7200.11 series only, but for me it worked with these momentus 5400.6 drives as well..)

And hey special thanks for VideoRipper for wonderful tips about IDE drives. :thumbup

I will give a try for this area as well.

0

Share this post


Link to post
Share on other sites

Hi

jaclaz

Thanks for reminding me the basics. :-)

And i apologize for my mistakes. :no:

Can you please tell me the solutions for Seagate Momentus 5400.6 drives?

Because I have few Momentus drives which are not getting detected. (Basically they are USB Portable Drives, so disconnected disk from it and) I performed direct F3 T>m0,2,2,0,0,0,0,22 on it.

So disk started detecting in BIOS as well as in Windows but with no file system on it(no NTFS/FAT32). So when i further diagnose it i found non repairable bad sectors on it (I tried with HDD Regenerator).

I am not able to figure out my mistakes in this process. ( I know these firmware reset command is designed for seagate 7200.11 series only, but for me it worked with these momentus 5400.6 drives as well..)

And hey special thanks for VideoRipper for wonderful tips about IDE drives. :thumbup

I will give a try for this area as well.

The point that I evidently completely fail to explain :( is that THIS THREAD is for 7200.11 ONLY, and ONLY for those affected by the LBA0 or BSY state. :realmad:

Don't you think that otherwise it could have been titled:

Post here any crazy question about any dead hard drive and also any other question that crosses your mind?

:unsure:

Five simple steps :):

  1. Start a NEW thread, here:
    http://www.msfn.org/board/forum/169-hard-drive-and-removable-media-issues/
  2. Title it meaningfully
  3. DON'T EVER use HDD regenerator (if the scope is recovering DATA)
  4. STOP (for the moment ;)) fiddling with those drives
  5. Post detailing ALL the steps you ALREADY took

jaclaz

0

Share this post


Link to post
Share on other sites

Hello Gradius!

Thank you for sharing your knowledge.

I also came to BSY problem with my sister's Seagate 7200.11, however, disk still doesn't to boot after procedure I've gone through.

- I've made first BSY step change.

- Bios now recognizes HDD

- Tried to boot from disk, no go.

- I've made first second BSY step change.

Here is serial console log from second (optional) BSY step:

F3 T>i4,1,22

F3 T>

F3 T>m0,2,2,,,,,22

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewr

ite Retries = 00C8

User Partition Format Successful - Elapsed Time 0 mins 00 secs

- Partition format was very quick, instant.

- Disk still doesn't boot.

- Now I've used diagnostic SeaTools from Seagate.

- Done Short test and I've received answer ADEACE62, that I dish has bad blocks

- Done Long test and I've received answer that there are 100 errors (error was at all but very first block ).

I didn't have any problems with RS232 part or moving powered PCB back to HDD body.

My question is, if you can confirm me, if I've done something wrong.

I'm not sure if it was correct to do (second) optional BSY step, because first one already solved BSY problem (but disk didn't boot).

Thank you in advance,

Borut.

Edited by dencorso
Removed unnecessary (and way too long) quotation. Please do quote just what's really needed!
0

Share this post


Link to post
Share on other sites

pborut,

please edit your post removing the WHOLE Quote from Gradius' initial post, it makes no sense and only contributes to make the thread less readable.

There is nothing wrong in the procedure.

You shouldn't even THINK of booting from that drive.

Your next step should be to image that drive to another one and then attempt to recover the DATA you may have on it (if of value).

jaclaz

0

Share this post


Link to post
Share on other sites

What SURELY happens is that your drive WILL NOT come back to life.

Additionally you risk that EVEN the now working drive WILL NEVER come back to life. :ph34r:

For sure I don't want to make things more broken than they currently are so I will try going with the standard procedure and let you know the outcome.

Hi all,

I've just completed the procedure and it worked! (I had a few strange error messages, sorted out by tightening the screws on the PCB=-

Thank you very much.

Ciao!

Max

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.