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


Yep :), but as said before, if you can access the terminal without insulating anything you are not in either BSY or LBA0 situation (which are the ONLY ones for which we have some experience) you are in any of the n :ph34r: possible other failure conditions, and as such your drive is outside the scope of this thread and (much) beyond our (limited) level of  competence :(.

Try finding some support on:

http://malthus.mooo.com/viewforum.php?f=2

if spildit or fzabkar (to name a couple of the most friendly and knowledgeable members over there) have some advice for you (provided that no special equipment such a PC-3000 is needed) you still have some chances.

jaclaz
 

Share this post


Link to post
Share on other sites
1 hour ago, jaclaz said:

Yep :), but as said before, if you can access the terminal without insulating anything you are not in either BSY or LBA0 situation (which are the ONLY ones for which we have some experience) you are in any of the n :ph34r: possible other failure conditions, and as such your drive is outside the scope of this thread and (much) beyond our (limited) level of  competence :(.

Try finding some support on:

http://malthus.mooo.com/viewforum.php?f=2

if spildit or fzabkar (to name a couple of the most friendly and knowledgeable members over there) have some advice for you (provided that no special equipment such a PC-3000 is needed) you still have some chances.

jaclaz
 

Thanks Man... You've been awesome through the entire process. I will give Malthus a shot

Share this post


Link to post
Share on other sites
55 minutes ago, CODEBLUE001 said:

Thanks Man... You've been awesome through the entire process. I will give Malthus a shot

You are welcome I am sure :), let us know how it goes.

jaclaz
 

Share this post


Link to post
Share on other sites

Hi Jaclaz,

now i ran in problems. I did the procedure right in the tutorial ..ok one thing i didnt understood is the step

Quote

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

i didnt disconnecte anything an set only the /T order.

All seems to work fine exept after the last input ..nothing happens anymore since 20 minutes now.

I interrupt the motor ..and i heard it also that nothing happens.. so i think all was right.

What can i do now? I let it on power now

Thanks for help

Regards

update 1 ':  i couldnt wait an did it again with a break with at least 60 seconds ..and???.....taddaaaa


Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 00, Max Certify Rewr                                            ite Retries = 0000
User Partition Format   5% complete, Zone 00, Pass 00, LBA 00008DED, ErrCode 00000080, Elapsed Time 0 mins 10 secs
User Partition Format Successful - Elapsed Time 0 mins 10 secs


:)))

so i think first step is done :) .. if now the data is accessable   i am happy

update 2:

data backuped and firmware update done - all is working fine .. and i am happy ..

thanks a lot guys for help

Cyb2017-06-09_2340.png.c9693edd8cc307d72ab81dc2d6c139ef.png

Edited by Cyberurmel

Share this post


Link to post
Share on other sites
16 hours ago, Cyberurmel said:

update 1 ':  i couldnt wait an did it again with a break with at least 60 seconds ..and???.....taddaaaa


Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 00, Max Certify Rewr                                            ite Retries = 0000
User Partition Format   5% complete, Zone 00, Pass 00, LBA 00008DED, ErrCode 00000080, Elapsed Time 0 mins 10 secs
User Partition Format Successful - Elapsed Time 0 mins 10 secs


:)))

so i think first step is done :) .. if now the data is accessable   i am happy

update 2:

data backuped and firmware update done - all is working fine .. and i am happy ..

Good :), that is what we call in jargon the "Bloubul's maneuvre" :w00t:


 

Happy of (yet another) happy bunny in the basket:

jaclaz

Share this post


Link to post
Share on other sites

Hey guys,

I have an ST31000340AS 1TB drive. I can "spin down", remove paper, and spin up successfully, but when I get to the "F3 1>N1" command, I get "Unknown Diag Cmd Failure 12CC4". After this failure, I can successfully spin down the drive before removing power.

I was able to view the drive in Device Manager briefly, and found that the firmware is SX15 (not SD15 as the printed label indicated) like this:

  1. I configured BIOS to allow hot swapping
  2. Did the spin down/remove paper/spin up procedure
  3. Connected the drive via SATA to motherboard
  4. Windows installed driver for the HDD
  5. Found the drive in Device Manager
  6. Viewed the Properties and found the firmware version written somewhere (forget where exactly) 

The drive did not have any volume information, and it did not stay mounted long. It disconnected after several minutes.

Regardless, after getting the 12CC4 error, I tried to do the "F3 T>m0,2,2,,,,,22" command. I got no response through the terminal, even after waiting for 2 HOURS. I tried "CTRL + Z" and it was unresponsive, so I did a power cycle. It still responds to the spin down/up procedure just fine, but I can't get past the N1 step and I'm afraid to try the m0,2,2,,,,,22 step again. :crazy:

Any advice?

P.S. - "F3 C>Q" also yields the "Unknown Diag Cmd Failure 12CC4" error.

Edited by rustyNISSAN

Share this post


Link to post
Share on other sites
On 9/21/2013 at 7:03 PM, BFeely said:

I just found an answer to the dreaded 12CC4 error! My ST31000340AS bricked while I was installing an SSD in my PC, and I ran into the 12CC4 error when attempting to run the N1 command. Apparently the SX15 drives don't have the overlay to fix the firmware, but I stumbled upon a workaround:

Step 1: Download and burn the SD1A firmware update ISO from the Seagate website at http://www.seagate.com/staticfiles/support/downloads/firmware/MooseDT-SD1A-3D4D-16-32MB.iso (download from http://www.seagate.com/staticfiles/support/downloads/firmware/MooseDT-SD1A-2D-8-16-32MB.iso if you have a 500GB drive).

Step 2: Detach the PCB and put card stock under the head contacts.

Step 3: Attach the serial to TTL converter to the drive.

Step 4: Connect the drive to your PC's power supply.

Step 5: Wait for the drive to spin up then come to a complete stop.

Step 6: Open a terminal (38400 bps, 8 data bits, 1 stop bit, no parity, no flow control)

Step 7: Press CTRL+Z.

Step 8: Enter /2 then press Enter.

Step 9: Enter Z then press Enter.

Step 10: If you get the LED error, disconnect the power and start from step 3. Make sure the motor comes to a complete stop before entering the Z command. If you get "Spin Down Complete" then continue to step 11.

Step 11: Remove the card stock from under the head contacts and reattach the circuit board.

Step 12: Enter H then press Enter.

Step 13: When "Spin Up Complete" appears, attach a SATA cable from your PC to the drive.

Step 14: Insert the firmware CD, reboot your PC (make sure the power does NOT cycle) and boot from the CD.

Step 15: Follow the instructions to update the firmware.

Step 16: Turn your PC off then on again.

Step 17: Back up all data from the now recovered drive then don't use the drive for anything important.

@BFeely, I noticed step 12 you suggest the "F3 2>H" command. Did you mean "F3 2>U" to spin up the drive? H is a command on the Head...

Has anyone else had luck with this method on an already bricked ST31000340AS with SX15 firmware?

Share this post


Link to post
Share on other sites

Yes :), it is very likely that it is a "H" mis-typed instead of the "normal" "U", as Step 13 is referring to "Spin Up complete".

jaclaz
 

Share this post


Link to post
Share on other sites
On 7/18/2017 at 3:30 PM, rustyNISSAN said:

@BFeely, I noticed step 12 you suggest the "F3 2>H" command. Did you mean "F3 2>U" to spin up the drive? H is a command on the Head...

Has anyone else had luck with this method on an already bricked ST31000340AS with SX15 firmware?

Bump.

I have read everywhere that updating the firmware is to be avoided at all costs...

Is this really a valid solution? Has anyone had success with this other than @BFeely ?

On 7/19/2017 at 6:00 AM, jaclaz said:

Yes :), it is very likely that it is a "H" mis-typed instead of the "normal" "U", as Step 13 is referring to "Spin Up complete".

jaclaz
 

Word. Didn't know if there was some magical command specific to fw SX15 I was unaware of.

Share this post


Link to post
Share on other sites

The point is that we don't know much about how the whole thing works.

Updating the firmware is not "to be avoided at all costs", in the "normal" "common" BSY/LBA0 issue is simply NOT useful and  unneeded, but being anyway a risky operation (always, but particularly when the disk drive is not working properly for *unknown* reason) it is only advised after having recovered data, when, in the worst case, it will re-brick the drive (possibly in such a way that it is not recoverable) but since the priority (recovering the data) went fine, it wouldn't matter.

In case of a LBA0 issue it won't probably do anything, in case of BSY the disk is not recognized so the update cannot be performed.

That "strange" condition of a SX15 firmware on a drive marked SD15 (and 12CC4 error) you have is seemingly not a common one, so we don't have any other report that I can remember. :(

jaclaz

Share this post


Link to post
Share on other sites
On 7/21/2017 at 9:01 AM, jaclaz said:

The point is that we don't know much about how the whole thing works.

Updating the firmware is not "to be avoided at all costs", in the "normal" "common" BSY/LBA0 issue is simply NOT useful and  unneeded, but being anyway a risky operation (always, but particularly when the disk drive is not working properly for *unknown* reason) it is only advised after having recovered data, when, in the worst case, it will re-brick the drive (possibly in such a way that it is not recoverable) but since the priority (recovering the data) went fine, it wouldn't matter.

In case of a LBA0 issue it won't probably do anything, in case of BSY the disk is not recognized so the update cannot be performed.

That "strange" condition of a SX15 firmware on a drive marked SD15 (and 12CC4 error) you have is seemingly not a common one, so we don't have any other report that I can remember. :(

jaclaz

7

I definitely have the BSY error (and I think the LBA0 error as well). I HAVE NOT been able to recover the data yet using the "safe and tested" methods.

I can get it to "spin down", reconnect the motor, and actually spin up. At this point I plug in the SATA cable, the OS recognizes the drive, installs driver, and reports no partitions on the disk, but only for a short time. I am powering with a second power supply to maintain power to the drive when computer is shut down.

What I will try next:

  1. get drive to spin up
  2. shut down computer with drive still powered/spinning
  3. turn on computer and enter BIOS
  4. if drive is recognized in BIOS, attempt to boot from firmware update CD

Share this post


Link to post
Share on other sites

Hi everyone, thanks for all the valuable information here - highly useful.

I  followed the steps all the way through and got the below message:

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

User Partition Format Successful - Elapsed Time 0 mins 00 secs

Note that 'Elapsed time 0 mins and 00 secs', unlike like the one that everyone else got that says 'Elapsed time 0 mins and 05 secs'

I am also missing this line (the line that is supposed to be in between the two above:

User Partition Format 10% complete, Zone 00, Pass 00, LBA 00004339, ErrCode 00000080, Elapsed Time 0 mins 05 secs 

Now the first time I completed the process and restarted the PC with the SATA cable connected to the affect HDD (which does not have an OS installed), my bios automatically went into a screen after initial boot up that was similar to it checking and repairing a drive - this took around 10mins. I then logged into windows and my drive was there!

I was so excited that I tried to see if all my files were still available. I must have clicked on files too quickly and an error popped up and then the HDD disappeared from windows - unfortunately I was not sharp enough to get a screen print of the message.

Since then I've been going through the entire process again and again. Sometimes it my bios detects it with the correct size, but most of the time it doesn't detect it. Even when the bios does detect it, windows doesn't after I logged in.

I've also noticed that so far every time it's appeared detected by my bios, its because I done the following:

1) completed BSY solution

2) disconnect hdd, turn off hdd power, turn off pc

3) turn on pc, log into windows (no drive detected)

4) restart pc, go into BIOS and the drive is there!

And then when I log back into windows its gone again...

 

please help me!!!

Edited by dznuk90

Share this post


Link to post
Share on other sites

Which contacts did you insulate?

i.e. motor or heads ones?

Or did you completely remove the PCB?

In some cases the contacts between the PCB and the disk may be "irregular", in wich case a good idea may be to use a pencil eraser to clean the contacts and/or use a (teeny-tiny quantity of) electric contact cleaner and/or (sometimes needed) tighten a little bit more the screws.

Also, do not underestimate the possibility that the actual SATA cable is bad (the SATA connector is re-known to have been poorly engineered and to come loose after a finite number of insertions/removals).

First thing (after having made sure that contacts between PCB and disk are clean would be to try anothe SATA cable, new and/or surely working, and try the disk on another machine (most probably not your case, but you never know which kind of mess can be a Registry and what issues it can create) or use (on the same machine) a definitely "clean" environment, such as a PE or a Live Linux distro.

More generally, you don't really want to access the volume(s) on the disk (on Windows, say via Explorer) you actually should be ready to image the disk (of course if it can beseen as \\.\PhysicalDrive), it is not uncommon that while the disk (the \\.\PhysicalDrive) is "revived"  *something* is stil amiss/corrupted, preventing the volumes in it to be mounted and assigned a drive letter.

Once you will have managed to make an image of the \\.\PhysicalDrive, then it will be possible to (hopefully) check it and recover the volumes or the files.

jaclaz

Share this post


Link to post
Share on other sites

Thanks for the quick reply! Really didn't expect it, much appreciated.

Not sure which one is which, but think the motor is the slightly diagonal contact - I didn't insulate this one, but insulated the other one with a card (and then pulled it out before entering the U command).

Only removed the PCB at the very beginning to get the card underneath, then lightly screwed it back, before fully tightening it after I pulled the card out. I've tried using a small bit of nail polish remover on both the head and the motor contacts to clean it - and lightly scratching off what appeared to be scorch marks to bring back the shine. 

SATA cable is quite new too so doubt it can be this, but will try a new one tomorrow. I have a live Ubuntu USB stick so will boot from that tomorrow at the same time with the new cable.

How to I make an image of the \\.\PhysicalDrive?

BTW I just tried again and now its in the Windows 10 'scanning and repairing' screen. Might be because I manually hard shut down the computer from the last report, or might be its detected the drive - its scanning and repairing drive F right now and last time when I first thought I fixed it, it was assigned drive letter F before the error came up. Fingers crossed maybe?

Edited by dznuk90

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.

×