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

The Solution for Seagate 7200.11 HDDs

- - - - -

  • Please log in to reply
4721 replies to this topic

#4351
boywondered

boywondered
  • Member
  • 2 posts
  • OS:none specified
  • Country: Country Flag
Hello smart people,

I am having a problem that I can't seem to find much/any info on. I followed the steps for the BSY error, and got all the way to the end message. I plugged the drive into a USB cable and it was recognized (Yay!) and I started pulling files off of it. About half way through my computer stopped recognizing the drive, and I could no longer access it.

There are two partitions on the drive, one of them I can get into (with nothing of importance) and the main one I cannot. I get a mix between:

E:\ is not accessible. The disk structure is corrupted and unreadable

and

E:\ Parameter could not be found.

I have tried repeatedly (unsuccessfully) to try to get into it again, but nothing seems to work. Is this a different issue that popped up, or could it be something to do with the firmware issue.

Thanks in advance for your help.


How to remove advertisement from MSFN

#4352
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,077 posts
  • OS:none specified
  • Country: Country Flag

There are two partitions on the drive, one of them I can get into (with nothing of importance) and the main one I cannot. I get a mix between:

E:\ is not accessible. The disk structure is corrupted and unreadable

and

E:\ Parameter could not be found.

I have tried repeatedly (unsuccessfully) to try to get into it again, but nothing seems to work. Is this a different issue that popped up, or could it be something to do with the firmware issue.

No, this has nothing to do with the bricking or the unbricking, those are related to the device being inaccessible, now you have access to the device (and to one of the structures on it) but not to another structure (partition/volume/filesystem) on it.
This could be caused by a "simple" corruption of the filesystem (or one of the identifiers/indexes) or a physical corruption of some sectors on the device.
Start a new thread, now you are not anymore in the 7200.11 unbricking, but in "generic" data recovery.

jaclaz

#4353
boywondered

boywondered
  • Member
  • 2 posts
  • OS:none specified
  • Country: Country Flag

No, this has nothing to do with the bricking or the unbricking, those are related to the device being inaccessible, now you have access to the device (and to one of the structures on it) but not to another structure (partition/volume/filesystem) on it.
This could be caused by a "simple" corruption of the filesystem (or one of the identifiers/indexes) or a physical corruption of some sectors on the device.
Start a new thread, now you are not anymore in the 7200.11 unbricking, but in "generic" data recovery.

jaclaz


Thanks jclaz. This has definitely been a "journey".

#4354
mre142

mre142
  • Member
  • 1 posts
  • OS:none specified
  • Country: Country Flag
I just received my cable and started going through the steps of fixing my drive. I get up to the step where you use N1 to clear the SMART. When I enter that all I receive is Unknown Diag Cmd Failure 12cc4. I have tried researching this issue with no luck. Has anyone experienced this?

#4355
DeejayF

DeejayF
  • Member
  • 4 posts
  • OS:none specified
  • Country: Country Flag
Hi,

I have a Seagate Barracuda 7200.11 in a busy state, and I've followed all the instructions and read through gazillions of pages and tutorials both here and on other locations.
I got the adapter hooked up to a COM1 port on a XP SP3 Laptop.

The communications are all fine and all of the steps are successful until the final step.
Last step would be:

When the prompt comes back up, turn off power to the hard drive, wait a few seconds, then turn it back on. Wait about 20 seconds, then finally do partition regeneration:

F3 T>m0,2,2,0,0,0,0,22 (enter)


Alright so I turn off the power to the harddrive, wait around 60 seconds to power it on but there's no response anymore from the harddrive, meaning the terminal is not responding to any of my commands.

I've tried:
Disconnecting and reconnecting the cables one by one (Serial cable, SATA cable, AC cable, communication cables).
Two different terminals (Putty and Hyperterminal)
I've remade all of the steps around 10 times, but still the same issue.

Everytime I disconnect the power of the harddrive (Removing the SATA cable and putting it back in after 60 seconds) I lose connection.
Loopback test is successful and rest of the communication is good.
it's just the final step that I can't get to.

I've seen people having problems with NOT powering off the HDD before executing the last step so that's not something I would like to do.

What do you recommend on doing? What is most likely the issue here? As all communication is working until I reconnect the HDD I wouldn't suspect anything wrong with the communication.
Is my controller card faulty? Is the header faulty? Am I doing something wrong in the steps?
This is my second day of trying to solve this and I'm running out of patience. If anyone has an idea or a some simple tips it would be MUCH appreciated.

Thanks,
DeejayF

Edited by DeejayF, 13 December 2012 - 01:32 AM.


#4356
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,077 posts
  • OS:none specified
  • Country: Country Flag
I don't get it. :unsure:

You do some of the steps, then it comes the (optional) powering down.
You unplug the power SATA connector.
Wait 60 seconds (roughly).
You re-plug the power.
Then you do ctrl+Z and you do not re-access the interface? :w00t: <- maybe this is the step you are missing?

A communication session is initiated by the ctrl+Z, of course since you powered down the disk the previous session is lost.

If you read the recommended guide, here:
http://www.mapleleaf...agatebrick.html

Which will simply return the level one prompt

F3 1>

At this point, many say you need to disconnect the SATA power cable from the drive and wait one minute. Yes, count to sixty. Then plug the SATA power cable back into the drive. There is a bit of debate about this step in the forums but that is what I did and it worked fine in my case. *IF and only if* you choose not to disconnect drive power temporarily, you need to at least change back to the test level prompt (type F3 1>/T (enter)) at this point before continuing.

Now back in HyperTerminal, you'll need to hit CTRL-Z to get a fresh prompt

F3 T>

And it's time to regenerate the partitions with the command (notice the lower case here)

F3 T>m0,2,2,0,0,0,0,22 (enter) <-------- note, those are 'zeros' not 'ohs', i.e. the digit, not the letter

And now you need to be patient. I have reports of this command taking around sixty seconds (as was my case) and up to ten minutes to execute. It will send back several intermediate messages but will eventually return the following message (with a different time):

this is made clear, the snippet you posted is coming from where? :w00t: (I know ;), it comes from here: https://sites.google...ite/seagatefix/ )

As well first post of the present thread specifies how you need to issue the ctrl+Z:

Power OFF/ON the drive (very important!)

Wait 10 seconds and now Power ON your drive.

Press CTRL+Z on terminal and type:

Partition regeneration:

F3 T>m0,2,2,,,,,22 (enter)


Guess why there is a Seagate Barracuda 7200.11 READ_ME_FIRST sticky here:
http://www.msfn.org/...-read-me-first/
with a point #3 citing two tutorials (and NOT the one you seemingly are using)?

jaclaz

#4357
DeejayF

DeejayF
  • Member
  • 4 posts
  • OS:none specified
  • Country: Country Flag
Hello Jaclaz, I really appreciate your fast response.

Yes indeed CTRL+Z would provide me with a new session, but nothing does happen. I cannot reaccess the interface.
I was unable to do anything when re-powering the HDD, as if the terminal hanged.
As said, I've gone through multiple angles when troubleshooting and the exclusion method, testing the cables and power back and forth but I was unable to find a solution.

If you look at my last edit of my troubleshooting you will find that I am now stuck at another problem when trying another controller card.
As the day is leading towards its end I will let this go on through the night and see where it stands tomorrow.

I will continue my path of troubleshooting as well. If you have any other enquires or advice, do not hesitate to write it down here as I will be very active on this thread until I manage to solve this issue.

Thanks,
DeejayF

Edit 1: It seems as if you believe that I've only read through one source of information. As stated in my first post I have indeed read through a large amount of threads/tutorials/posts around here. The reason why I chose mainly the google sites tutorial was because I found it to be most comprehensive.

Edit 2: "optional" powerdown is what you've stated and I've seen stated on multiple instances here. I've also read that if you don't do this powerdown it might result in an eternal wait and loss of data. What information should I go on? If I don't shut it down I will still keep communication although as from I've read on here it might result in data loss. This is the main reason to why I'm here.

Edited by DeejayF, 12 December 2012 - 09:21 AM.


#4358
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,077 posts
  • OS:none specified
  • Country: Country Flag
Well, the power down and then resume with ctrl+Z has worked for at least a few thousands of people, so it is confirmed to work "in most cases".

As a matter of fact this powering down may not be needed as other guides/tutorials/reports do not specify it.

If I gave you the false impression to believe that you had only read through one source of information is because we have two "tutorials" right here, cited in the read me first and you cited the instrctions form a third one, NOT mentoned there.
It was not a false impression, I actually had it and you did everything in your powers to convey it.

It makes no sense (unless *something* else occurred to that disk - i.e. it is not in a "pure" BSY state - or during your previous attempts *something* changed) that you have different behaviour while using a different "controller card" (what do you mean exactly with "controller card"? and with "changing it"? :unsure: )

jaclaz

#4359
DeejayF

DeejayF
  • Member
  • 4 posts
  • OS:none specified
  • Country: Country Flag
Alright so now I am back from yesterday.
New update:

Did all the steps needed except for the "optional powering down".
This has been stuck here for the last 14 hours.

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


Following the tutorials did not help me unfortunately.
As you mentioned "jaclaz", it might be some other "unknown" error as well.

Update 2:
Alright we had another HDD with the BSY error. Following the tutorials and all I managed to solve the issue within 10 minutes with a successful outcome.
So there is most certainly some other "unknown" error within the original HDD I was testing.

Over and out,
DeejayF

Edited by DeejayF, 13 December 2012 - 03:14 AM.


#4360
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,077 posts
  • OS:none specified
  • Country: Country Flag
What you may want to try on the "problematic" hard disk is inserting a F712 sequence.
WARNING
I have NO idea if it is "appropriate" for the situation that hard disk is and never like in this case "no guarantee of any kind" :ph34r:
WARNING
See:
http://forum.hddguru...ize-t11040.html
This post:
http://forum.hddguru...80.html#p131011

TO ALL:
this is NOT "recommended" it is NOT part of the "standard" unbricking procedure, it is normally NOT needed and should NOT be attempted if not as a "last resort", when the "normal" commands in the tutorials fail!

jaclaz

#4361
DeejayF

DeejayF
  • Member
  • 4 posts
  • OS:none specified
  • Country: Country Flag
Thing is that there's no communication working to the HDD when it is assembled.
I can only get communication to it when I block out the head or the motor.
I know it may sound strange but this is the phenomenon I'm getting.

I know my recent posts may have been lacking a bit of practical information due to me only describing the problems I was currently experiencing, but the phenomenon is basically the major thing that keeps me from accessing the HDD properly.

With this in mind, I don't think I'm willing to send in other commands that could hurt the data even more. Best thing for me to do in the future with this disc is to FULLY identify the problem and get it displayed to me. If it's not possible the best thing to do would obviously be to send it to a data recovery company. I'm not sure how valuable the data is due to the disc not being my own.

Either way,
Thanks for the fast responses jaclaz, it is people like you who makes the internet a valuable place to consider when problems are being encountered.
If I get to the point where the data gets fully recovered I will make sure to post here again on how I resolved it, as I have a few things left on my list to try.

Thanks,
DeejayF

#4362
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,077 posts
  • OS:none specified
  • Country: Country Flag

Thing is that there's no communication working to the HDD when it is assembled.
I can only get communication to it when I block out the head or the motor.

Yes, this is the "strange" part. :unsure:

Normally a "working" hard disk (not in BSY state) does connect when "fully assembled".
The disconnecting of either the head or the motor (of both as in the original tutorial) is only a way (or rather a "trick") to exit the "loop" that is causing the BSY state.

jaclaz

#4363
elloco4ever

elloco4ever
  • Member
  • 2 posts
  • OS:none specified
  • Country: Country Flag
Hi to everyone.
With this method, will i be able to recover the data inside the disc?
I mean, i follow the procedure and when i boot again ill be able to see all the data so i can make a back up? :P
Thanks in advanced

#4364
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,077 posts
  • OS:none specified
  • Country: Country Flag

Hi to everyone.
With this method, will i be able to recover the data inside the disc?

Who knows?
It depends from which issue is your disk suffering from, actually WHAT caused the issue.
NO guaranteee of any kind.

Take some time reading ATTENTIVELY the read-me-first:
http://www.msfn.org/...-read-me-first/

I mean, i follow the procedure and when i boot again ill be able to see all the data so i can make a back up? :P

Normally yes, the data is back "as it was before", BUT sometimes partition or file based recovery is necessary (and sometimes even these fail)

In any case you DO NOT attempt booting from that disk, you try first thing (if the BSY or LBA0 issue is resolved) imaging it on another disk surely working and attempt recovering the data.

jaclaz

#4365
Gradius2

Gradius2

    IT Consultant

  • Member
  • PipPip
  • 240 posts
  • OS:Windows 7 x64
  • Country: Country Flag
Just to report (because is a new record!).

A ST2000DM001 just died (out of nothing) with less than 250 working days!

And yes, it was using the last FW available to the public.

I can't see (or wait) the time when 1TB (and more) SSDs would be cheaper.
"Two things are infinite: The Universe and Human stupidity; and I'm not sure about the Universe." Albert Einstein

#4366
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,077 posts
  • OS:none specified
  • Country: Country Flag

I can't see (or wait) the time when 1TB (and more) SSDs would be cheaper.

So that WHEN one of those will fail you will have even LESS chances to recover data from them? :unsure: :w00t:

We add here to the existing "internal translation" and "G-list" possible issues also the SSD brand new ones, such as "wear leveling" and "garbage collecting". :ph34r:

jaclaz

#4367
Phaenius

Phaenius

    Member

  • Member
  • PipPip
  • 177 posts
  • OS:Windows 7 x64
  • Country: Country Flag
So far, every storage system can fail. Even Johnny Mnemonic's brain.

#4368
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,077 posts
  • OS:none specified
  • Country: Country Flag

So far, every storage system can fail. Even Johnny Mnemonic's brain.

For NO apparent reason :whistle: :
Spoiler


Posted Image

jaclaz

#4369
elloco4ever

elloco4ever
  • Member
  • 2 posts
  • OS:none specified
  • Country: Country Flag
Hi
Sorry to bother again but i wanted to ask what does exactly do the last step for fixing the BSY bug. Because ive read the last step and it says:
Partition regeneration:
F3 T>m0,2,2,,,,,22 (enter)
Does this format the hhd? How can i recover the data after doing that?
Thanks in advance

#4370
Phaenius

Phaenius

    Member

  • Member
  • PipPip
  • 177 posts
  • OS:Windows 7 x64
  • Country: Country Flag
You shouldn't normally need to. Normally the data should be already there after the command and reboot. No need for an additional action.

#4371
neosource

neosource
  • Member
  • 2 posts
  • OS:Windows 7 x64
  • Country: Country Flag
Thank you for this information, I managed to restore a clients hard drive using it :)

Though I found the instructions on this page a little easier to follow and apply (not sure who the author is though).

https://sites.google...seagatefix/Home

They suggested using a small piece of cardboard to break the connection between the PCB and the head contacts during the spin down phase. I removed the 2 screws near and to the bottom left of the head contacts to allow the cardboard to slide in/out. I also loosened the long screws near the corner edges. After I performed the spin down I then gently removed the cardboard and carefully inserted just the one the screw near the head contacts (helped to use a magnetic tip to position the screw), as that seemed to be the simplest and most efficient way to do it.

I had the "Error 1009 DETSEC 0000600" when trying to spin the drive up. A quick fix for me was to simply place a piece of cardboard on top of the PCB (to shield from any electrical discharge) near where the head contacts are and apply some gentle pressure with my finger then try the spin up command again. That allowed me to restore the drive, though cleaning the contacts can also help prevent any further problems.

I hope that helps.

#4372
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,077 posts
  • OS:none specified
  • Country: Country Flag

Though I found the instructions on this page a little easier to follow and apply (not sure who the author is though).

https://sites.google...seagatefix/Home

That guide, though good, is NOT the recommended one, which is this one (as sticked AND pointed to in the READ ME FIRST):
http://www.mapleleaf...agatebrick.html
which is a more complete one.

If you need to use a piece of cardboard to press down the PCB to obtain spin up it means any (or more than one) of three things:
  • you used the cardboard on the head contacts AND the cardboard was a bit too thick
  • the head contacts were not properly cleaned
  • you failed to re-tighten appropriately the screws near the contacts

The workaround you used is potentially a VERY dangerous one :ph34r: , what you had was a "bad" contact that you "patched" (possibly only temporarily) by pressing a bit on the PCB.

That PCB should be disassembled, contacts cleaned and the "springy effect" of the contacts on the disk be verified, then all screws re-tightened firmly before further use of the disk.

jaclaz

#4373
Phaenius

Phaenius

    Member

  • Member
  • PipPip
  • 177 posts
  • OS:Windows 7 x64
  • Country: Country Flag
It is said that what you don't know can't hurt you. Now you made me worry again, jaclaz. I fear I have might tightened the screws too hard. Also, the contacts between PCB, head and motor were so corroded, I wonder how it works. But it does. :wacko:

Edited by Phaenius, 04 January 2013 - 06:24 AM.


#4374
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,077 posts
  • OS:none specified
  • Country: Country Flag

It is said that what you don't know can't hurt you. Now you made me worry again, jaclaz. I fear I have might tightened the screws too hard. Also, the contacts between PCB, head and motor were so corroded, I wonder how it works. But it does. :wacko:

JFYI:
http://www.crcind.co...3 KONTAKT60.PDF
http://www.crcind.co...3 KONTAKTWL.PDF
http://www.crcind.co...3 KONTAKT61.PDF

jaclaz

#4375
Phaenius

Phaenius

    Member

  • Member
  • PipPip
  • 177 posts
  • OS:Windows 7 x64
  • Country: Country Flag
Too expensive. How about this, found at a local store at about 2.75 euros ?

Posted Image




7 user(s) are reading this topic

0 members, 6 guests, 0 anonymous users


    Bing (1)


How to remove advertisement from MSFN