[jaclaz]

mlamagna, on 05 August 2010 - 07:35 AM, said:

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.

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/...=128807&st=1821
http://www.msfn.org/...=128807&st=2173
http://www.msfn.org/...=128807&st=2240
And with:
http://www.msfn.org/...howtopic=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....

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

Start from here:
http://www.msfn.org/...-read-me-first/
feel free to ask for help should something be not clear.

jaclaz

[mlamagna]

jaclaz, on 05 August 2010 - 09:32 AM, said:

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.

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

This post has been edited by mlamagna: 05 August 2010 - 10:35 AM

[mongoled]

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?

[fackeid]

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

[jaclaz]

fackeid, on 06 August 2010 - 10:01 AM, said:

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?
http://www.msfn.org/...-read-me-first/
Answer: To avoid having to reply to the SAME questions asked n times before (and also answered n times before)

Please READ it:
http://www.msfn.org/...-read-me-first/
EXPECIALLY ponts #1 and #2

jaclaz

[VideoRipper]

fackeid, on 06 August 2010 - 10:01 AM, said:

Can we use this RX TX method with other Seagate SATA drives as well??

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

And for (older) PATA drives you'll have to connect the convertor to these
pins (and try slower rates, like 9600 Baud):


If you want to know if the "Tricks" in this thread also applies to other
types of (Seagate) drives: read Jaclaz' comment above.

Greetz,

Peter.

[fackeid]

jaclaz, on 06 August 2010 - 03:25 PM, said:

fackeid, on 06 August 2010 - 10:01 AM, said:

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?
http://www.msfn.org/...-read-me-first/
Answer: To avoid having to reply to the SAME questions asked n times before (and also answered n times before)

Please READ it:
http://www.msfn.org/...-read-me-first/
EXPECIALLY ponts #1 and #2

jaclaz

Hi
jaclaz

Thanks for reminding me the basics. :-)
And i apologize for my mistakes.

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.

I will give a try for this area as well.

[jaclaz]

fackeid, on 07 August 2010 - 03:30 AM, said:

Hi
jaclaz

Thanks for reminding me the basics. :-)
And i apologize for my mistakes.

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.

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.

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

Quote

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

Five simple steps :

• Start a NEW thread, here:
  http://www.msfn.org/...e-media-issues/
  
• Title it meaningfully
  
• DON'T EVER use HDD regenerator (if the scope is recovering DATA)
  
• STOP (for the moment ) fiddling with those drives
  
• Post detailing ALL the steps you ALREADY took

jaclaz

[pborut]

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.

This post has been edited by dencorso: 09 August 2010 - 09:29 AM
Reason for edit: Removed unnecessary (and way too long) quotation. Please do quote just what's really needed!

[jaclaz]

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

[mlamagna]

mlamagna, on 05 August 2010 - 10:34 AM, said:

jaclaz, on 05 August 2010 - 09:32 AM, said:

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.

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

[jaclaz]

mlamagna, on 09 August 2010 - 07:26 AM, said:

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

Another happy bunny in the basket!
http://www.msfn.org/...ic=128727&st=10

jaclaz

[VideoRipper]

mlamagna, on 09 August 2010 - 07:26 AM, said:

(I had a few strange error messages, sorted out by tightening the screws on the PCB=-

Don't forget this thread: How to solve Error 1009 DETSEC 00006008 FIX,
but also notice Jaclaz' note about this:

jaclaz, on 05 April 2010 - 07:15 AM, said:

Generally, it is NOT adviced to use "nail thinner" as it could adversely affect the plastic parts of the connectors/PCB, as it usually contains trichloroethane, if using anything like it or acetone:
http://en.wikipedia.org/wiki/Acetone
be very careful NOT to use it on plastic parts.

To clean contacts use isopropil alcohol:
http://en.wikipedia....opropyl_alcohol
or a dedicated electric contact cleaner.

Anyway... good job!

Greetz,

Peter.

[pborut]

Hello jaclaz,

Thanks for reminding me about removing quotation. It's actually first time I'm actively using any forum, so I must learn of how it goes...

About BSY problem. Thank you for clearing that one out too,
Best regards,
Borut.

[Nc1224]

Hi again!

It seems like my HDD is going down again, but I'm not sure why. I'm wondering if it could be the 0 lba error, so I thought I'd check here. As it is now, when i check "my computer", it shows my 2 HDDs. But the seagate one, when you examine it, has a 0 byte capacity. i can't open it and it does now have the windows symbol in the icon.

Thanks in advance

[jaclaz]

Nc1224, on 11 August 2010 - 09:42 AM, said:

It seems like my HDD is going down again, but I'm not sure why. I'm wondering if it could be the 0 lba error, so I thought I'd check here. As it is now, when i check "my computer", it shows my 2 HDDs. But the seagate one, when you examine it, has a 0 byte capacity. i can't open it and it does now have the windows symbol in the icon.

Check how it is seen in BIOS, first.
If it is shown with 0 capacity, then yes,it's a LBA0 symptom.

jaclaz

[GoKart]

Thanks Gradius and all others for posting on the Seagate 7200.11 (Barracuda). My Maxtor 1TB last apprx 5 weeks; put it away for 1 year; busy with life. Issue seem same as others - no power. Have now tried the HDD into 2 other powered caddies still no power. One caddy had a cooling fan and both had indicator lights. With the Barracuda inside, and power on, no lights, and even the fan was no go.
So, 1 QNS, please:-
1. Does the BSY firmware code bug problem result in lock up automatically (shut down) of the hdd drive motor AND power supply intake into the powered caddy, so caddy indicator lights and cooling fan non-op?
2. If the drive motor is burnt out and unserviceable, can the recording medium be removed and reinstalled inside another HDD unit with working HDD drive and optical reader?
thank you from a non-technical GoKart (billy cart)

[jaclaz]

GoKart, on 13 August 2010 - 08:35 PM, said:

So, 1 QNS, please:-

Which means TWO of them....

GoKart, on 13 August 2010 - 08:35 PM, said:

1. Does the BSY firmware code bug problem result in lock up automatically (shut down) of the hdd drive motor AND power supply intake into the powered caddy, so caddy indicator lights and cooling fan non-op?

NO.
http://homepages.tes...no-answers.html

GoKart, on 13 August 2010 - 08:35 PM, said:

2. If the drive motor is burnt out and unserviceable, can the recording medium be removed and reinstalled inside another HDD unit with working HDD drive and optical reader?

YES.
http://homepages.tes...no-answers.html

GoKart, on 13 August 2010 - 08:35 PM, said:

thank you from a non-technical GoKart (billy cart)

You are welcome.

Notwithstanding that you obviously missed the read-me-first:
http://www.msfn.org/...-read-me-first/
whaere you would have learned how your problem is pretty much a non-target and thus should have NOT been posted here, we are good guys after all.

From what you write you have probably had a problem somewhere (can be BOTH on the hard disk AND on the actual power supply) that blowed a TVS.
A TVS is a sort of protection diode (there are normally two of them on modern hard disks, one on the 5V and one on the 12 V rail) that, in case of problems shorts to ground to prevent (in theory) further damage.
In reality if this has happened, STOP moving the hard disk here and there, some power supplies have a protection that simply shuts them off if a short is found, some will simply blow silently.

The drive needs to be checked thoroughfully from an electrical/electronic view point before ANY further step can be taken.

Before you ask, NO, a PCB SWAP won't work (without a procedure outside of your reach) and it is possible that will also damage the donour PCB.

It is technically possible to:

• open the hard disk
  
• remove the platters from it
  
• re-assemple the platters on another identical hard disk
  
• recover the data

BUT it is NOT anything you can do at home as you would need tools and expecially experience that you simply cannot have (otherwise you won't be here asking about it).

If the disk drive contains important data you may want to fork from a relatively huge amount of bucks and have a specialized recovery firm look at it. (only you can judge the value of that data but we are talking of several hundred dollars, probably in the $600÷1,000 range)
If the idea is to just recover a functional drive, forget about it, if the problem can be repaired without opening the hard disk, like replacing the TVS or fixing a cold solder, it would be allright, but a drive with exchanged platters is to be considered functional (hopefully ) only for the sheer time needed to get the data out of it, and should be thrown in the bin immediately after the recovery.

PLEASE, remove from your previous post the integral quote of Gradius' initial post, it only contributes to make this thread less readable.


jaclaz

[psm321]

Hi all,

I am trying to recover my 1TB 7200.11 from BSY lock. After I enter the "N1" command, I get "Unknown Diag Cmd Failure 12CC4". Like the other 2 posters I found on here with this problem, I got my drive (online) from Fry's, but in every respect it looks like a normal Seagate drive. I did not power down the drive at any point during the process, and have double-checked to make sure I followed it correctly. I can spin down and spin-up the drive and it sounds normal.

The last time someone posted with this problem, they were requested to do "/C" and then "Q" to get a list of available commands, but they never responded. I tried that, and get the same "Unknown Diag Cmd Failure 12CC4" when I try to run "Q".

Any ideas would be appreciated. I have looked through the search results within this thread for "unknown diag cmd failure" already [edit: to remove search link that was session-based and include search terms instead]

Thanks!

This post has been edited by psm321: 15 August 2010 - 01:48 PM

[VideoRipper]

psm321, on 15 August 2010 - 01:47 PM, said:

I am trying to recover my 1TB 7200.11 from BSY lock.

And you're sure:

• The drive is really a Seagate 7200.11 drive with SD15 firmware?
  
• When issuing the N1 command, you're in the "F3 1>" menu?

Greetz,

Peter.