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

If you perform the /1 N1 command and then you fart and open and close the window, and then do ten push-ups and shout "FIX ME! FIX ME! FIX ME!!" it will work as well, if the drive suffers just from the 7200.11 bug. Should all of us trying to repair our drives fart and open the window, and then do the push-ups and shout three times FIX ME!? Powering it off at that point has nothing to do with the problem you are trying to solve. If it really makes a difference - then your drive needs to meet the doctor, or the rubbish.

I hope that's clear enough!! Regards

Edited by Azurlake

Share this post


Link to post
Share on other sites

@kostas275

Try doing the power off by disconnecting the power cable, and waiting one minute.

No matter if *needed*, it has worked fine with the power off step.

@Azurlake

Shouting really hard at hardware is a known technique that I personally use, when needed, but you need to be trained to use it, and often some plainer threatening works fine:

http://www.msfn.org/board/topic/139328-disc-drive-unable-to-eject/?p=891753

(farting is of course a no-no for the obvious minimum level of education and dignity :ph34r:, and the push-ups serve no purpose whatever :no:)

fb3fb929-ea63-4d82-a9de-752060850816.jpg

jaclaz

Share this post


Link to post
Share on other sites

@kostas275

Try doing the power off by disconnecting the power cable, and waiting one minute.

No matter if *needed*, it has worked fine with the power off step.

@Azurlake

Shouting really hard at hardware is a known technique that I personally use, when needed, but you need to be trained to use it, and often some plainer threatening works fine:

http://www.msfn.org/board/topic/139328-disc-drive-unable-to-eject/?p=891753

(farting is of course a no-no for the obvious minimum level of education and dignity :ph34r:, and the push-ups serve no purpose whatever :no:)

fb3fb929-ea63-4d82-a9de-752060850816.jpg

jaclaz

@jaclaz

:thumbup intimidating things is one of the funniest and dumbest things humans do when things stop working - or when they smash their toes with the door or the head with the window :lol:

Share this post


Link to post
Share on other sites

help after this point (F3 1>N1 (enter)

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.

my ) no response to write the Type m0,2,2,0,0,0,0,22 nothing responding to my HyperTerminal what to do?

Share this post


Link to post
Share on other sites

You need to re-issue the Ctrl+Z to access the disk, you know, like:

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

If the above doesn't work, start again the whole procedure since the beginning, and this time do not remove power and only change level to get to the F3 T> prompt.

I assure you that my eyesight, as well as that of most members of the site, is good enough :yes: to read what is written in "normal" characters, NO need to post in large characters, which is BTW common netiquette and against the Board Rule #11:

http://www.msfn.org/board/index.php?app=forums&module=extras&section=boardrules

11. Do not use CAPITALIZATIONS in the topic title or when participating in threads because they will not attract attention - instead it will annoy many of MSFN's members. Using unnecessary font formatting (i.e., bold font, increased font sizes, colored fonts, etc.) on the full body of posts is also discouraged.

jaclaz

Share this post


Link to post
Share on other sites

ok everything i see bios but the windows not see what to do ?

Start a NEW thread detailing your current issue, your next step would be (if possible) to image the disk "as is" on another drive partition (NTFS) of suitable larger size or clone it to a disk of the same size, READ this:

http://www.msfn.org/board/topic/170938-damaged-logical-structure-of-seagate-720011/

as an example to understand the tools needed/general approach.

update the firmware ?

NO, NO, NO!

READ AGAIN:

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

Point #15

AND READ this:

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

The whole point is that you simply CANNOT go on and on (and on) asking questions about things that are ALREADY (hopefully clearly) written all over the place and that you were additionally ALREADY being pointed to and ALREADY told to READ attentively.

jaclaz

Share this post


Link to post
Share on other sites

The next step is to read ALL the links that jaclaz pointed you to. In fact, read them all three times. Only after that, before you do anything else, come back and explain, in detail, exactly what you believe is the situation with your drive and what you understand are the steps, in order, you need to take to fix or analyze the situation further. But if the situation is that your BIOS can see the drive but Windows can not, then your post does not belong in this thread because you have a different problem than what is being discussed here. Start a new thread somewhere else instead.

Cheers and Regards

Share this post


Link to post
Share on other sites

the only broblem is the drive not leaves to update the firmware . what to do ?

The xolution to that broblem may require you to READ AGAIN (for the fourth or fifth time, unless I am mistaken) the given resources.

jaclaz

Share this post


Link to post
Share on other sites

now to fix my drine and update the new firmware, i trust the hard drive after that ?

Share this post


Link to post
Share on other sites

now to fix my drine and update the new firmware, i trust the hard drive after that ?

Oh, my. :(

READ (now for the 6th or 7th time, I lost the count) point #5 of the READ-ME-FIRST:

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

and/or see if these slightly differently worded posts (to the same effects) are clearer:

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/?p=1012499

Compare with flippism:

http://en.wikipedia.org/wiki/Flipism

and with "is it safe"?

http://www.imdb.com/title/tt0074860/quotes?item=qt0247572

jaclaz

Share this post


Link to post
Share on other sites

Want to make sure I'm properly differentiating BSY vs LBA 0. Until a month ago, I was blissfully ignorant of this wonderful feachur from Seagate.

I had two Seagate 7200.11 (500GB) SD15 in a ReadyNAS, they have been in this unit for over 5 years. They haven't seen a lot of activity. After filling a root partition on the ReadyNAS, and having to reboot because of hangs, both drives susipiciously stopped working after a forced power down. Since one came with the unit and the other was purchased in a Seagate box, they were different ages, and had different power-on times, I feel this is a strong indicator.

When I placed both drives in a stand-along Dell Optiplex GX620 (with their A11 Bios), in the Bios setup I get a Drive Failure message and see the following in the Bios screens.

1. The Vendor and model number is correctly listed.

2. The Capacity is listed as "unknown" (not 0)

Because of #1, can I assume that I don't have the BSY problem? By my reckoning, no recognized would mean that there would be absolutely no information about the drive.

Is "unknown" really the same as 0, and just an artifact of this Dell Bios?

Also, what is the exposure if I run the BSY or LBA 0 procedure on the drives, if I don't really have that specific problem, having incorrectly diagnosed it.

I realize I'm being cautious. Most likely I will eventually proceed as if this is the LBA 0 problem.

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...