Overclock.net › Forums › Components › Hard Drives & Storage › Seagate Bricked Firmware Drive Fix (With Pics)
New Posts  All Forums:Forum Nav:

Seagate Bricked Firmware Drive Fix (With Pics) - Page 12

post #111 of 261
I have the same issue with my Seagate St3500320AS 500GB 7200.11 hard drive.
It just died one day and stopped being recognized by BIOS any more. The only way of booting the system from another drive with this one disconnected.

To make a story short. I read the whole thread here and there, did the cable, connected my drive but cannot go any further after the step where you remove plastic card and use U command in Putty (HyperTerminal).

My problem is:
Once i plug the power in, it spins loudly with 7-10 clicking noises and then slows down.
The error i am getting after removing plastic from the SPIDER and using U commnad is the following:
"Error 1009 DETSEC 00006008
Spin Error
Elapsed Time 13.923 secs
R/W Status 2 R/W Error 84150180".

Who knows what is that and if it can be fixed?
I cannot move on to another step with this error. ;(

My Firmware is SD15. Disk is being recognised by Seagate Seatools and by Windows Disk Management, But any test with Seatools FAILED, and in Windows Drive Management recognises it, but says that it has 0 MB on it and that it is not initialised.

Can you offer me a solution to my problem please?
The data on disk is vital and i am trying to recover it ASAP.

Look forward for your replies and suggestions.
post #112 of 261
Quote:
Originally Posted by Kumchak View Post
I have the same issue with my Seagate Once i plug the power in, it spins loudly with 7-10 clicking noises and then slows down.

Look forward for your replies and suggestions.

Kumchak,

although you have some of the symptoms of the BSY/0 LBA problem, you actually have a bigger physically issue with the clicking sounds.

In all the posts in various forums, there is no clicking sound associated with this issue.

I'm afraid you actually have a physical problem that this solution cannot fix. Time to return it for a replacement IMHO.
post #113 of 261
too bad! ;( i will try to find someone who will be able to fix it and to restore my data....

Thank you for the reply though....
post #114 of 261
I have a Seagate St3500820AS 500GB 7200.11 SD25 firmware hard drive. I had it connected as a internal drive for extra storage. I used a pci to sata card to connect the drive. About a week ago I turned my pc on and it froze at the splash screen where it says windows xp with the blue bar going across. After a few test I disconnected the seagate drive and my pc booted up fine. I have another drive connected the same way through the sata to pci card, I switched the cables around to see if thats the problem but it froze again at the windows xp splash screen.

I read the forums and tried the solution. I had a max232 adaptor I connected the hard drive to it and used 2 AA batteries to power it. When I press ctrl Z i get nothing in hyperterminal I double checked all cables and reversed the tx/rx still nothing. I also tried it with the nokia CA-42 cable its got 3 cables blue, red and orange. I tried a loopback test and when I connect the blue and red wires together I get these wierd characters in hyperterminal without typing anything. Assuming that the blue and red wires are the tx/rx and orange being ground I tried again but I still didn't get an response when pressing ctrl Z. I switched the cables around but still no luck.

The pin layout for the CA-42 cable is:
blue - pin 12
orange - pin 6
red - pin 4

Is there anything I'm doing wrong?
Do I need to get a proper RS232 to TTL adaptor?
Is the CA-42 cable that I have one of the working ones?
Edited by M.A.H - 8/24/10 at 4:04pm
post #115 of 261
Just wanted to say thanks. I was able to fix my seagate using these instructions.
Big thanks to Dia, I got the same "ca-42" cable. My wire colors were a little different but everything else was the same.
Hackintosh
(13 items)
 
  
CPUMotherboardGraphicsRAM
E6300 Wolfdale @3.59ghz GA-G31M-ES2L PNY 9600 gt OCZ 4GB 1066 MHz DDR2 
Hard DriveOptical DriveOSMonitor
WD Black 640GB, 1TB Samsung F3 Asus DVD Snow Leopard & Windows 7 Samsung P2450 
KeyboardPowerCaseMouse
Logitech Illuminated Corsair 400w Antec 300 Illusion Logitech MX 518 
  hide details  
Reply
Hackintosh
(13 items)
 
  
CPUMotherboardGraphicsRAM
E6300 Wolfdale @3.59ghz GA-G31M-ES2L PNY 9600 gt OCZ 4GB 1066 MHz DDR2 
Hard DriveOptical DriveOSMonitor
WD Black 640GB, 1TB Samsung F3 Asus DVD Snow Leopard & Windows 7 Samsung P2450 
KeyboardPowerCaseMouse
Logitech Illuminated Corsair 400w Antec 300 Illusion Logitech MX 518 
  hide details  
Reply
post #116 of 261
Hello
I have a "Barracuda.ES.2" affected by the "BSY error".

Serial N°: 9QM8DLBE
Model: ST3500320NS
Part N°: 9CA154-052
Firmware: MA07
DateCode: 09173
(manufac. date): (2008 October 27th)
SiteCode: KRATSG
PurchaseDate: ????-??-??
FailedDate: 2010-07-08
OEM/RETAIL: OEM (Dell)
UserName: HallBert
Country of User: Canada
fail reason/fine: no detect in bios (BSY error)
OS: WinXP

I'm trying to un-brick the drive using a CA-42 cable (chinese clone).
A problem arise when i type "Ctrl+z" in the hyper terminal, i don't get the prompt "F3 T>". Nothing happens.

When the PCB is mounted on the HDD in a normal way (no isolation between the contact head and the PCB),i get this message about every minute:
"LED: 000000CC FAddr: 0024AFF9" (should indicate that the drive is in a busy state ?)

I'm stuck there...Bad cable??? problem specific to the HDD model ???
I have done some research without finding a solution.
So i need some HELP!!!
Thank you!!!

P/S A soldering between a point on the USB PCB and a small black cable was broken.After resoldering,the loopback test was OK.
post #117 of 261
Quote:
Originally Posted by mundy5 View Post
That's correct, wrench. There should be no odd sounds at all with the BSY and the BIOS problems. It is actually a firmware issue. "clicking" indicates something is physically wrong with the head or its components which a firmware fix will not correct. sorry.
Thanks, but now I have an update.

I removed the drive from the factory external case. I plugged it into another USB external case and get normal sounds from the drive now and spin up is fine. Yet now, the bios does not recognize the drive.

Any chance I have the BSY issue?
post #118 of 261
Quote:
Originally Posted by wrench View Post
Thanks, but now I have an update.

I removed the drive from the factory external case. I plugged it into another USB external case and get normal sounds from the drive now and spin up is fine. Yet now, the bios does not recognize the drive.

Any chance I have the BSY issue?
It looks like it might be the case if you say that there are no odd clicking sounds.
post #119 of 261
Quote:
Originally Posted by M.A.H View Post
I have a Seagate St3500820AS 500GB 7200.11 SD25 firmware hard drive. I had it connected as a internal drive for extra storage. I used a pci to sata card to connect the drive. About a week ago I turned my pc on and it froze at the splash screen where it says windows xp with the blue bar going across. After a few test I disconnected the seagate drive and my pc booted up fine. I have another drive connected the same way through the sata to pci card, I switched the cables around to see if thats the problem but it froze again at the windows xp splash screen.

I read the forums and tried the solution. I had a max232 adaptor I connected the hard drive to it and used 2 AA batteries to power it. When I press ctrl Z i get nothing in hyperterminal I double checked all cables and reversed the tx/rx still nothing. I also tried it with the nokia CA-42 cable its got 3 cables blue, red and orange. I tried a loopback test and when I connect the blue and red wires together I get these wierd characters in hyperterminal without typing anything. Assuming that the blue and red wires are the tx/rx and orange being ground I tried again but I still didn't get an response when pressing ctrl Z. I switched the cables around but still no luck.

The pin layout for the CA-42 cable is:
blue - pin 12
orange - pin 6
red - pin 4

Is there anything I'm doing wrong?
Do I need to get a proper RS232 to TTL adaptor?
Is the CA-42 cable that I have one of the working ones?
Do note that you are trying a solution on a different firmware. The most common firmware for this problem was SD15. You also might not be following the instructions verbatim. Please look at it again. You need to be able to unscrew the pcb and screw it back on once it spins down.
post #120 of 261
You too have a different firmware than the one for this problem. SD15 was the most common one. You very well might have a different problem than BSY or it might require a different solution than this one.

Quote:
Originally Posted by HallBert View Post
Hello
I have a "Barracuda.ES.2" affected by the "BSY error".

Serial N°: 9QM8DLBE
Model: ST3500320NS
Part N°: 9CA154-052
Firmware: MA07
DateCode: 09173
(manufac. date): (2008 October 27th)
SiteCode: KRATSG
PurchaseDate: ????-??-??
FailedDate: 2010-07-08
OEM/RETAIL: OEM (Dell)
UserName: HallBert
Country of User: Canada
fail reason/fine: no detect in bios (BSY error)
OS: WinXP

I'm trying to un-brick the drive using a CA-42 cable (chinese clone).
A problem arise when i type "Ctrl+z" in the hyper terminal, i don't get the prompt "F3 T>". Nothing happens.

When the PCB is mounted on the HDD in a normal way (no isolation between the contact head and the PCB),i get this message about every minute:
"LED: 000000CC FAddr: 0024AFF9" (should indicate that the drive is in a busy state ?)

I'm stuck there...Bad cable??? problem specific to the HDD model ???
I have done some research without finding a solution.
So i need some HELP!!!
Thank you!!!

P/S A soldering between a point on the USB PCB and a small black cable was broken.After resoldering,the loopback test was OK.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Hard Drives & Storage
Overclock.net › Forums › Components › Hard Drives & Storage › Seagate Bricked Firmware Drive Fix (With Pics)