Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Gradius2

The Solution for Seagate 7200.11 HDDs

Recommended Posts

This may help you take a decision, though the same theme is discussed also in the read-me-first (point 5, to which you were ALREADY pointed to) here it is more explicit:

http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page-187#entry1067976

http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page-119#entry930329

http://www.msfn.org/board/topic/158397-invalid-partition-table-on-my-500gb-hdd/page-2#entry1012499

 

 

WHAT :w00t: is the "difficult part" in those? :unsure:

 

Let's try again. :)

 

Question: OK, I have revived a hard disk, <insert here any number of wordy descriptions and considerations>, can the drive be trusted afterwards? <optionally insert here any number of more logical reasons why you think you repaired the disk and how you think it should be blindly trusted, and how it is not possible that the manufacturer built a bad disk>

Answer: NO, nein, non, ...

More:

http://www.freelang.net/expressions/no.php

 

See if these further clears the matter:

http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/?p=1004448

http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page-161?p=985254#entry985254

 

You have applied a "miracle" cure to an UNDIAGNOSED illness, there is NO way on Earth to know WHAT was the problem and HOW it was fixed (IF it was fixed) and how long this UNKNOWN CURE will prevent the SAME (or other) ILLNESS to affect again the disk.

 

I am not at all offended :), I am exasperated (which is different) as the SAME, SAME, SAME question that has been answered IN ALL POSSIBLE WAYS is asked AGAIN, and AGAIN and AGAIN.

 

Your disk has been by sheer luck revived, if you managed to get the data you already were very lucky, if I were you I would not bet on it working properly again (which does not mean that it cannot happen, only that I would not bet on this).

 

More:

http://www.msfn.org/board/topic/158663-problem-during-firmware-update-drive-is-not-detected/?p=1014387

http://www.msfn.org/board/topic/158663-problem-during-firmware-update-drive-is-not-detected/#entry1014421

 

jaclaz

Edited by jaclaz

Share this post


Link to post
Share on other sites

does anyone know,

when i get to the point where it says take power out of the hdd and then put it back in then wait then type the m,0,,22, command. when i put the power back in, i cant type anything into hyperterminal?

Share this post


Link to post
Share on other sites

nevermind, i plugged it in and it showed the 0mb on BIOS, so i did 0 lba trick.

and its all working!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

 

how do i update firmware so it doesnt happen again, or should i just copy filess over and throw it out?

Share this post


Link to post
Share on other sites

how do i update firmware so it doesnt happen again, or should i just copy filess over and throw it out?

Point #5 of the read-me-first:

http://www.msfn.org/board/topic/143880-seagate-barracuda-720011-read-me-first/

further expanded here:

http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page-121#entry932258

 

jaclaz

Share this post


Link to post
Share on other sites

yeh soz simple google search and i got it.

 

for some reason i first had the bsy error, then playing with the m0,22 thing i then plugged it onto my motherboard and it came up on the bios but as 0 mb so the 0lba error.

fixed that and its all fixed!

 

not sure why this only happened to me now since ive been using it since 2008, and this is my primary storage hard drive, from 08-11 it was my primary hard drive with OS on it.

Share this post


Link to post
Share on other sites

my seagate barracuda 7200.11 hdd isn't recognized by BIOS (BSY error). my hdd was partitioned (one partition for OS and one for data). I have a doubt:

digiting "m0,2,2,,,,,22 (enter)" (partition regeneration), it would appear "User Partition Format Successful" (with other); what it means? it formats my partitions and I lose my data or it recognize the original partitions? or something else?

I hope it's all clear.

thank you for the topic.

Share this post


Link to post
Share on other sites

Normally (i.e. if the cause of the BSY is the original problem) all data remains accessible "as before".

 

IF the cause of the BSY is another, the data recoverable may vary.

 

But the answer to your question is "something else", what happens when you issue that command through terminal is that "user partition (data) is regenerated", i.e. the part of the disk that is accessible to the user is reset to "usable".

 

That "partition" is at a completely different level (much lower) than the "partition" you see in (say) Disk Manager, it is the partitioning of the disk between "Seagate's Data" and "User Data".

 

If you prefer, usually (say 95% or more of cases :yes:) after the disk has been unbricked, it will appear exactly as it was before, though in some instances it happened that partition based recovery was needed (and was rather easily accomplished :)), example:

http://www.msfn.org/board/topic/145574-seagate-750gb-one-partition-is-raw-after-bsy-fix/

in an even minor number of cases, partition recovery was not possible :ph34r: or only partially possible :(, examples:

http://www.msfn.org/board/topic/157671-need-help-with-data-recovery-on-hdd/

http://www.msfn.org/board/topic/157688-still-no-partition-on-seagate-after-successful-unbrick/

http://www.msfn.org/board/topic/170881-seagate-720011-malediction/

 

There is no real way to know in advance as we don't have a way to diagnose the actual cause of the problem.

 

jaclaz

Share this post


Link to post
Share on other sites

Hi, i have recently bought a USB-->TTL adapter for fix my ST3500320AS. I have installed the driver on 2 pc: 1 on Windows 8.1 x64 and another with Windows 7 x32.

The adapter works fine if i put together the TX-RX connector (i see loopback on hyperterminal), but when i connect the hdd there are nothing on the screen, only blink cursor.

Now i cannot tried to remove the PCB because i don't have a Torx T6. there is a possibility that work if i try to remove the PCB? Or is possible to a driver problem?

 

The HDD was visible in bios, before the issue, but now isn't.

Share this post


Link to post
Share on other sites

Hi, i have recently bought a USB-->TTL adapter for fix my ST3500320AS. I have installed the driver on 2 pc: 1 on Windows 8.1 x64 and another with Windows 7 x32.

The adapter works fine if i put together the TX-RX connector (i see loopback on hyperterminal), but when i connect the hdd there are nothing on the screen, only blink cursor.

Now i cannot tried to remove the PCB because i don't have a Torx T6. there is a possibility that work if i try to remove the PCB? Or is possible to a driver problem?

 

The HDD was visible in bios, before the issue, but now isn't.

 

If the disk is bricked, it is bricked.

 

If you do not remove (or loosen enough) the PCB and insulate either the motor or head contacts you won't normally have access to the disk interface via TTL.

 

 

 

Consider the usual carpenter comparison:

To join two planks of wood together you need (at least) three nails (of suitable length) and a hammer.

Put the two planks one over the other and drive the nails vertically in both the planks by hitting with the hammer the heads of the nails.

 

Q. I have the hammer but no nails. I tried banging the hammer on the planks really hard, but they don't stick together.

A. You need the nails.

 

The procedure REQUIRES that one set (or the other) of contacts are insulated (or the whole PCB is removed).

You *need* a suitable Torx screwdriver to losen or remove the screws.

If you really-really cannot afford (or procure one) usually these screws can be undone with *any* flat screwdriver of suitable size of which you have filed down a bit the edges, i.e. from:

 

 

 _| || ||_|
 

to

 

 

/ \| |\ /
 

However, quick check list:

  • Is the disk powered?
  • Did you try hitting CTRL+Z?
  • Have you tried inverting Tx and Rx?
  • Are all devices properly grounded?
  • Have you made sure that the USB->TTL adapter provides the right (lower) TTL levels?
jaclaz Edited by jaclaz

Share this post


Link to post
Share on other sites

I have tried hit CTRl+z (not uppercase), swapped TX RX. I have bought a pl2303hx adapter, i think that is good for this job.

I thought that even without removing the PCB, something appeared on the screen, just for test.

Today i buy the Torx screwdriver and i will try to remove the PCB. I hope that will work! Thanks for now!

Edited by gogeta

Share this post


Link to post
Share on other sites

i have tried with PCB removed, with only isolation for the contact with a stripe of paper, but same situation... Driver problem for the TTL adapter?

Hyperterminal is correctly configured. OS: Windows 8.1 and Windows 7.

Share this post


Link to post
Share on other sites

Driver problem for the TTL adapter?

NO, if a virtual COM port is created and the loopback test works then the driver is fine.

Have you checked ALL the points I listed in my previous posts?

Have you double-checked them?

Have you also double checked the speed/parity/etc?

JFYI, by convention when I terminate a sentence with that little "hook" which is called a "question mark", it means that the sentence is a question, for which I would like to have an answer.

There are cases where the PCB needs to be completely detached from the disk (as in the first original attempts/tutorial).

jaclaz

Share this post


Link to post
Share on other sites

 

Driver problem for the TTL adapter?

NO, if a virtual COM port is created and the loopback test works then the driver is fine.

Have you checked ALL the points I listed in my previous posts?

Have you double-checked them?

Have you also double checked the speed/parity/etc?

JFYI, by convention when I terminate a sentence with that little "hook" which is called a "question mark", it means that the sentence is a question, for which I would like to have an answer.

There are cases where the PCB needs to be completely detached from the disk (as in the first original attempts/tutorial).

jaclaz

 

 

Yes i have checked all the points on the previous post, many times. Now i have completely remove the PCB, swapped the TX-RX and i can finally enter in the terminal!!

Now another problem. When i put this commands the terminal give me these codes:

F3 T>/2F3 2>ZLED:000000CE FAddr:00280569LED:000000CE FAddr:00280569 

Last row is repeated about every minute.

I have isolated only the contact on the lower side of the PCB, that is listed on the guide.

I will wait your info, thanks!

Edited by gogeta

Share this post


Link to post
Share on other sites

Type SLOWLY :w00t:;), AFTER having waited 15 or 20 seconds after having powered the PCB:

http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/?p=841755

 

There isn't a "lower" or "upper" side (it depends on the way you look at it), there are the "motor" contacts (which are near the motor) and the head contacts (which are the other set), the recommended guide:

http://www.mapleleafmountain.com/seagatebrick.html

suggests to try insulating the "motor" contacts, but it may depend on the actual disk and the situation in which it is "bricked", just like the Tx/Rx (if it doesn't work invert the wires), if one sets of contacts does not work, try again insulating the "other" one.

 

jaclaz

Share this post


Link to post
Share on other sites

I have successfully send all the commands!

F3 T>/2       F3 2>Z      Spin Down CompleteElapsed Time 0.154 msecsF3 2>USpin Up CompleteElapsed Time 6.399 secsF3 2>/1F3 1>N1F3 1>/TF3 T>i4,1,22F3 T>F3 T>EchoInterfaceCmds: OnEchoInterfaceCmds: Offm0,2,2,,,,,22Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewrite Retries = 00C8User Partition Format Successful - Elapsed Time 0 mins 00 secsF3 T>

But still not recognized by windows! What to do now?

Thank you for your patience!

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.

×
×
  • Create New...