CRITICAL: Seagate Hard Drive failures (see if your hard drive is affected)

[AMD_infinium05]

---

Seagate also added to check our drive trough Seatools... I ran it with my system, Seatools didnt find anything... not a single problem.....

[Bordzz]

what should be our basis before updating firmware?

okay, don't fix if ain't broken...

so what are the things (symptoms) that should be taken in mind to get a GO GO firmware update?

I got ST3500320AS, SD15 - i dont see any problem so far.

mao pud ako pangutana bro. pareha pud tag hdd. naglibog ko kng angay ba e update or dli...

[Visual C#]

I apologize if I didn't make myself clear...

The firmware is known to be broken, as seen with the thousands of people who were affected, with similar hard drive models as ours. So it has to be fixed; you have to update it if it shows in the site that your hard drive is affected. If we wait for the symptoms to show (drive not showing in BIOS), well, updating the firmware is going to be useless...

Unless you're willing to try this out:

The Solution for Seagate 7200.11 HDDs - MSFN Forums

[fists099]

tnks,,its so useful

[AMD_infinium05]

how long would the process would take?... i already downloaded the update ISO and burned it on a cd...

what are the things you kept in mind during the update?....

HAD JUST UPDATED from SD15 to SD1A, worked great.... the actual flashing takes less than a minute

ST3500320AS
SN: 5QM36G51
Site code: WUXISG

[Bordzz]

unsa nay update ani?

[AMD_infinium05]

the latest downloadable SD1A is fine.

[AndyRazer]

Seagate Techie Speaks Out, Explains Firmware Debacle
Earlier this week, reports emerged of a simple firmware update going wrong for Seagate, rendering some batches of the company's Barracuda 7200.11 hard-drives useless. The flaw in the said firmware update (version SD1A) locked the drive's microcode, preventing the system BIOS from even detecting the drive, in case the user wanted to restore a drive damaged from the update. SD1A was released to fix stuttering problems caused as a result of a bad implementation of the drives' SATA micro-controllers, the earliest diagnosis of the problem the drives were facing. An employee of Seagate working in its engineering, attempted to explain the SD1A firmware debale, from the perspective of someone who doesn't work with the company's public-relations.

The SD1A firmware, according to the employee, wasn't given out as a singular release, but rather in several revisions to individual customers on a support-customer level, rather than an all-out public download. That was to address customers quicly, when the issue first surfaced as a flaw with the firmware. The problem actually existed where errors during drive operation was written to the drive's firmware to build on a log. When that log reached 320 entries, it would cause errors during initialization of the drive, when it is powered on, when the drive's firmware micro-code is read by the system BIOS. Errors in that process would cause the drive not to be detected / improperly initialized by the system. In a Tom's Hardware report, the employee explains that normally, a customer would go through the usual process of contacting tech-support for the preventative update and “this firmware had to go through five different checks to make sure it applies to the specific conditions to qualify sending to a customer, before now. 5 chances for us to go 'your drive needs the other (or none) firmware update'.” However, management, in order to quell the possibility of liability for drive failures, pushed a general public release of the firmware. “Suddenly, it's down to one check, and even that was more designed for a contingency just in case the wrong firmware was sent out.” The SD1A firmware mostly affected 500 GB versions of the Barracuda 7200.11 series, after it was released last week. Seagate pulled back the SD1A firmware after the issue of the firmware damaging hard-drives became chronic. The company later released a newer firmware update that can be found here.

Taken from a techPowerUp! article:
techPowerUp! News :: Seagate Techie Speaks Out, Explains Firmware Debacle

[isyot_daut]

kumusta na inyo mga hdisk sa mga nag update?

[AndyRazer]

Still OK (fingers crossed). Hopefully my drive won't break down. It's got all my data.