Reply
Byte
uttuk2009
Posts: 3
Registered: ‎01-23-2009
0

Updated firmware on a bricked hard disk but not working

[ Edited ]

One Seagate hard disk ST3500320AS has just died, the same one I tried to update the firmware last year but it did not work. I did not tried to update the firmware again as it was working fine. After it has disconnected from my computer I tried to update it firmware by running MS-SD1A.exe hopefully it wound help.  however, i think it did not help with the bricked and disconnected hard disk. The boot part is long and the hard disk light is on all the time. So I unplugged it, any suggestion to do with the bricked hard disk. Any chance to bring the hard disk back. Thank you. 

Yottabyte
fzabkar
Posts: 4,651
Registered: ‎01-27-2009
0

Re: Updated firmware on a bricked hard disk but not working

Your drive may be a victim of the Seagate 7200.11 BSY bug.

Here are repair procedures for Seagate 7200.11 drives:
http://sites.google.com/site/seagatefix/
http://www.msfn.org/board/index.php?showtopic=128807

Tutorial with photos:
http://www.overclock.net/hard-drives-storage/457286-seagate-bricked-firmware-drive-fix-pics.html

Pinout of Nokia CA-42 cable's Pop-port connector (use pins 6,7,8):
http://pinouts.ru/CellularPhones-Nokia/nokia_pop_pinout.shtml

See the following technical bulletin:
http://atulchitnis.net/files/seagate.pdf

Seagate were at one time offering free data recovery services to those customers whose drives were affected by the bug. This may still be the case.

After you have repaired your drive, you can apply the following firmware update.

Firmware Update for ST3500320AS, ST3500620AS, ST3500820AS, ST3640330AS, ST3640530AS, ST3750330AS, ST3750630AS, ST31000340AS [207951]:
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207951

If the Windows based updater rejects your drive, then use the CD ISO version. The difference is that one version compares the drive's existing firmware specs against an update matrix file, whereas the other version just checks the drive's model and family.

Byte
uttuk2009
Posts: 3
Registered: ‎01-23-2009
0

Re: Updated firmware on a bricked hard disk but not working

Thank you. 

 

I have more questions. From this website

 

http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/

 

They said

 

There are two common errors on Seagate 7200.11 HDDs (caused by bugs on firmware):

- 0 LBA error: it happens when your BIOS can recognize your HDD at POST moment, but as an 0MB drive.
- BSY error: it happens when your HDD enter on a halt state, or BuSY state. In this condition, your HDD will not be recognized by BIOS at POST moment.

 

How to check which one is my hard disk error? where to check and see. I do not understand at POST.

 

Yottabyte
fzabkar
Posts: 4,651
Registered: ‎01-27-2009
0

Re: Updated firmware on a bricked hard disk but not working

POST = Power On Self Test

When a PC powers up, it runs through several tests, one of which is to identify all the storage devices, ie hard drives and optical drives (CD & DVD). Normally you will see a list of these drives on your screen before Windows starts.

If your drive appears, but is displayed with a capacity of 0GB, then you have the 0 LBA problem.

If, OTOH, your drive does not appear, but is spinning, then it may be affected by the BSY bug.

Regular Visitor
Ajju
Posts: 1
Registered: ‎11-04-2010
0

Re: Updated firmware on a bricked hard disk but not working

Hi Brother

 

I tried with CA42 cable but the computer is not recognizing the com port  please tell me the exact procedure or if anyone has done it and he is residing in India ( Maharashtra) please help me

Yottabyte
fzabkar
Posts: 4,651
Registered: ‎01-27-2009
0

Re: Updated firmware on a bricked hard disk but not working

It would appear that not all CA42 cables are identical.

The first thing that should happen when you plug in the cable is that Windows should detect a USB-RS232 serial bridge device and prompt you for drivers.

Hopefully the drivers will have been supplied with the cable. If not, then use Microsoft's UVCView utility to identify the Product ID and Vendor ID of the bridge chip inside the cable, and then search the Net for drivers.

http://www.users.on.net/~fzabkar/USB_IDs/UVCView.x86.exe

If your cable's bridge chip is not detected, then there is one wire which may need to be connected to the drive's fourth pin.

More info when you provide some feedback ...