Well, i've 2 x 250GB and 1 x 500GB in my PC. All seagates, no problem. 1 250GB is an old model, no problem for that.

The newer 250GB is maybe 8 months or so, it has some problems after 2 or 3 months, but later discover it's the SATA cable giving problem and after changing the SATA cable, it works fine.

The last 500GB is the model in the thread title, i think about 2 months or so. So far no problem....but i'll start making schedule backup of my data to the other HDD tonight...

Made a NERO backup last night of my data in the 500GB drive to another Seagate 250GB HDD. Will set to schedule to run it twice weekly.

I still love my SEAGATE. ....Just give it enough love and it'll run fine....ha-ha..

This post has been edited by Matrix: Jan 15 2009, 10:50 AM

Just checked my HDD using SeagateTools....confirm it's the SD15 500GB drive....

Gonna schedule to run backup every 3 days tonight..

nOOOO!!!! I've just bought a 640GB WD HDD today for my BT machine...

btw, how to update the firmware for the seagate 500GB HDD?? The link provided up there has the batch file and all, but i've three drives in my PC....how does it know which to flash? Furthermore, is is safe to do? I'm afraid if i do it, it kills it immediately even faster than let it die naturally ..

Dang...mines is affected...i tried to create a case but failed to login...maybe non-working hours?

I've called Seagate Malaysia just now.

Just give them the serial number and they checked for you. The operator confirmed my HDD is affected and will be e-mailing me the update instructions.

Let's see how fast they can respond now....


Please call 1-800-80-2335. Just wait for a few minutes for the representative to pick up your call.

But i think everyone in LYP will start calling this number already so it might take longer now...

This post has been edited by Matrix: Jan 19 2009, 10:08 AM

Woo Hoo...Seagate reply me and responded already. They will send u a link and a certification validation. I've downloaded the file already...all in < 20 min after i called them....no need to e-mail to them...CALL IS MOST EFFECTIVE!

Here's the screenshot:


1) The certification link screen:


2) After u key in the certificate no(which is included in the e-mail they sent to you), the download screen.




I'll update tonight and see what happens...but must run backup before flashing!!

I still love Seagate.

No, mine is AD14. The reason i don't wanna post is because there could be different firmware for different batches. Don't simply pandai-pandai and flash everything to latest urself lar. I dun wanna post my firmware here and later screw up everyone's hard disks, then blame SeaGate.

Just give em a call, forgot the e-mail to the support posted up there. What's so difficult? Just spend 5 minutes on the line and kaw-tim already. Tell them ur serial no and they'll give u the correct firmware. Don't be lazy!

This post has been edited by Matrix: Jan 19 2009, 10:22 AM

Maybe, but perhaps it also didn't have the problematic code in SD15?? Who knows. We are not Seagate.

btw, here's some info from Seagate's forum...some user advice not to use NewEgg SD1A download (which i actually downloaded already).
http://forums.seagate.com/stx/board/messag...message.id=4240

---

Added on January 19, 2009, 11:03 amI said just give 'em a call (As in 'Membuat Pangillan Talipon'). So hard to pick up a phone and press some numbers meh??

Anyway, i'll pester their support to check on the SD1A.

This post has been edited by Matrix: Jan 19 2009, 11:03 AM

Yes, read somewhere that the fix isn't ready yet. So, even the SD1A isn't going to solve the problem anyway. Just wait for official release-lar. I backup my data everyday.

---

Added on January 19, 2009, 11:25 amJust found something:

http://ata.wiki.kernel.org/index.php/Known...Q_is_being_used

Is it because it caused by AHCI and NCQ? Those user who have a failed Seagate 500GB/1TB here....are you running in IDE mode or AHCI/RAID???

Please update!!

I am currently running in IDE mode.

This post has been edited by Matrix: Jan 19 2009, 11:25 AM

The firmware can't unbricked a bricked HDD. It is suppose to prevent the problem. What i would like to know is there and AD14 users who has a bricked HDD as well?

So any 500gb users has updated the firmware successfully already?

yeah..yeah please tell more. You are the first guy who successfully updated the firmware and see improvement!

1) What is ur HD model?

2) What is ur previous firmware version?

3) What is the firmware you updated?

Please share!!!!

---

Added on January 20, 2009, 9:03 amSure or not???

An update update has been released as of Jan 19, 2008 3:15PM CST

That was 1 year ago?? or the updater still stuck in the 2008 twilight zone???

---

Added on January 20, 2009, 9:13 amJust to share and update u guys, yesterday i called them and they give me a certificate to download the AD14 firmware. Then i reply them and ask them to confirm the new version (SD1A) and today they reply me with a link (same as the one above posted by poster here) which points to the SD1A....

Wah...lau...if i ask them again for new version again, maybe they give me another version?????

====================

Seagete Support:

Dear Xxxxx,

As per our conversation, Sending you the link to download the firmware upgrade for your drive with Model no.ST3500320AS

http://seagate.custkb.com/seagate/crm/self...sp?DocId=207931

Kindly click on the model no.of your drive. and follow the process.

Also attached is the file below on how to upgrade the firmware upgrade.

For any further assistance kindly feel free to Contact Us.

Best Regards,
Aditi Singh,
Customer Service & Support,
Seagate Technology.







--------------- Original Message ---------------
From: xxxxx
Sent: 1/19/2009 11:07 AM
To: sfdc.apacsupport@seagate.com
Subject: RE: Firmware upgrade [ ref:00D0hhzl.50035uo8V:ref ]

Dear Aditi,

Thanks for your prompt reply. But from what I understand this AD14 is an old version of the firmware that fixes the SD14 problem of not recognizing the full cache. I understand there is a latest firmware called SD1A which is available.

Can you please confirm if the latest SD1A can be downloaded?

Thank you.

Regards,
xxxx


-----Original Message-----
From: Seagate Technical Support [mailto:sfdc.apacsupport@seagate.com]
Sent: Monday, January 19, 2009 9:42 AM
To: xxxxx
Subject: Firmware upgrade [ ref:00D0hhzl.50035uo8V:ref ]

Dear xxxx,

Below you will find the instructions for redeeming the certificate number for Firmware upgrade for your internal drive

1. Go to the Certificate Validation URL on Seagate's website at: http://support.seagate.com/support/certificate.html

2. Enter the certificate number in the field provided on the website and click SUBMIT,

Your certificate number for your download is: <deleted>

(This code consists of 12 characters so please verify that you are using all characters listed.)

For any further assistance kindly feel free to Contact Us.

Best Regards,
Aditi Singh,
Customer Service & Support,
Seagate Technology.


ref:00D0hhzl.50035uo8V:ref





This post has been edited by Matrix: Jan 20 2009, 09:13 AM

Thank you. You da man!

I'm not sure what is my part no though, must open up and see i suppose, can't see from the SEATOOLS.

I'll update tonight and feedback.

Cakera Keras Cap Ayam. Made in Chow Kit.

Well, my one doesn't have any clack sound AFAIK...i've got 3 HDD inside...maybe too many other noise?? I thought some sound is normal?? Maybe i try to put my ears to the PC and listen for the sound tonight.

Wah-lau...better not update anything now until they test their thing thoroughly. At least mine is still working at the moment, it might get KOed immediately if i update with a not-so-tested firmware released in a hurry.

Not downtime. I think the SD1A got problem, so to prevent furhter damage, they take it offline b4 more Seagate users nuke their HDD.

This sympton actually to my 250GB with AAC firmware. Switch port and all that. But after i changed the SATA cable, it is now ok and doesn't have such problem anymore.

No guarantee. It could die the next time u plug it back in.

My advise...don't do anything or flash anything until there's further notice of new firmware and sees what happens...

It'll be ironic if we are trying to avoid a brick, but in the quest to prevent the brick, we actually bricked it.

Stay cool....