Barracuda XT, Barracuda, Barracuda Green, DiamondMax and other desktop SATA and IDE drives

[I_P_M]

Hi,

I am the owner of a ST3500320NS 500 GB Barracuda ES.2 which I have used as a system drive for about the last 12-18 months.

Last night when resume a hibernated vista session i got a BOSD and since the HDD has not been accessible. I am unable to see the device in BIOS and have checked on several machines.

There is no damage to the disk, it powers and spins well. there are no knocks clunks or other sounds that would indicate internal malfunctions.

I have done some research online and a large number of forum posts suggest the disk may be locked in BSY state and offer various suggestions to fix it.

I have also tired a Seagate firmware update, booted from the .iso and selected my disk model but the process hangs, seemingly unable to detect the HDD.

Can you please offer some suggestions on ways that i will be able to retreive the data stored on this disk? as typicial I got sloppy with backups.

Thanks

[I_P_M]

P/N - 9CA154-303

FW - SN05

[fzabkar]

See this thread:
http://forums.seagate.com/t5/ATA-and-Serial-ATA-drives/Updated-firmware-on-a-bricked-hard-disk-but-n...

[I_P_M]

Hi, thanks for your reply.

Does the 'Seagate 7200.11 BSY bug' also apply to the ES.2 as well then?

The thread you kindly linked states a ST3500320AS drive, however mine is ST3500320NS, will those solutions work?

Forgive my ingorance.

Thanks

[fzabkar]

The technical bulletin alluded to in that thread identifies an urgent field update that applies to the following models.
V Topic: Drive Hang after Power Cycle
Date: 1/16/09
Products: Barracuda 7200.11, Barracuda ES.2 (SATA), DiamondMax 22, FreeAgent Desk, Maxtor OneTouch 4, SV35.3, SV35.4

I know (from discussions at HDD Guru data recovery forums) that the 7200.11 DIY fix also applies to Maxtor DiamondMax 22, and I know it also works on the 7200.12 series (to address other issues).

I can't recall the same fix being attempted on ES.2 drives, but I'm willing to bet that it will work with these models as well. In fact the firmware image files for the ES.2 and 7200.11 drives contain references to TetonST and Moose (or Brinks). This confirms that they are members of the same family (Moose), and that they use the same terminal commands(TetonST).

If you see a "F3 T>" prompt, then you should be good to go.

BTW, you may this thread useful:

Unlocking terminal of Seagate ES.2 in BSY/LED:000000CC state:
http://www.msfn.org/board/topic/129551-unlocking-terminal-of-seagate-es2-in-bsyled000000cc-state/

[I_P_M]

Thanks again, I'll give it a try this weekend (or when the cable arrives) and get back to you..

Have a great weekend