[lavan]

kadolf, on Jan 18 2009, 03:56 PM, said:

My drive is bricked, but their serial number check thinks it's not affected.

My too
Seagate ST3500320AS, Firmware SD15, manufactured on March 22, 2008
Checker says it's not affected, but it's dead now!!!

[stormbow]

When I registered the drive it came up as so

Product: INTERNAL KIT 7200.9 FAMILY
Model: ST3500641AS-RK

The drive identifies itself as

Model Family: Seagate Barracuda 7200.11
Device Model: ST3500320AS
Serial Number: 9QM3D441
Firmware Version: SD15
User Capacity: 500,107,862,016 bytes

Seagate just says check your serial number online. The online checker "Your drive 9QM3D441 is NOT affected"
Doesn't give me a whole lot of confidence. I would like to know why the drive is okay if it says it has the affected firmware and why the serial number identifies as a 7200.9 series drive.

It is currently running fine but I have zero confidence in it.

[Leigh.Wanstead]

cdturri, on Jan 19 2009, 01:34 AM, said:

I think it's pretty clear that Seagate doesn't know the full extend of the problem or don't want to go public with it. The KB page says that the defective drives were manufactured in Dec 2008 but clearly there are lots of people who had their ST31500341AS failing as early as Oct 2008.

My hard drive S/N:9QJONXXX not effected. What to do? I got firmware:SD15. I purchased around 6 months ago. It was running fine now. I disconnected the drive around two days ago.

So I can not get the firmware from seagate???

This post has been edited by Leigh.Wanstead: 18 January 2009 - 12:31 PM

[Madcoder]

I just checked from the web page and I have a large server FULL of the faulty drives. The Seagate tool says they ARE affected by the problem. However, my drives are ES.2 (NS) drives on a SAS controller, so they were already flashed to AN05 a long time ago. I am now wondering if they are still impacted or if they are impacted only if I had the original SN05 loaded that they came with. Anyway, I will let everyone know what support says in this particular scenario.

[PrOdiGy1]

PrOdiGy1, on Jan 18 2009, 06:11 PM, said:

petoer, on Jan 18 2009, 04:09 PM, said:

guys try using capital letters when entering the serial # on seagates checker site.

this person is right!

mine was affected when i entered my number in so i was wondering why so many others were having problems. i just put it in again in lower case and it tells me my drive is not affected. make sure you enter the letters in caps on the seagate checker!

See this post if your serial number is coming up as not affected. also make sure there are no spaces when you enter into the field (this can happen if you are copying and pasting the number from somewhere) as that also messes up the search. pretty pants coding i have to admit!

[Madcoder]

One other thing to keep in mind is that they are obviously updating the situation as they learn more. For example, the KB article says it is only drives which were manufactured in December, but their serial number checker tool says my drives ARE affected, and they were manufactured long before December.

[Gradius2]

Madcoder, on Jan 18 2009, 03:39 PM, said:

One other thing to keep in mind is that they are obviously updating the situation as they learn more. For example, the KB article says it is only drives which were manufactured in December, but their serial number checker tool says my drives ARE affected, and they were manufactured long before December.

No this is FALSE !

Wasn't in December only, they really should meant UNTIL december are affected.

I have two drives from August and they died.

Btw the direct link is:
https://apps1.seagat...rms_af_srl_chk/

Gradius

This post has been edited by Gradius2: 18 January 2009 - 12:46 PM

[fatlip]

Hey all,

The fix was released on a website for those of you with the RS-232 connection. See Gradius' post. From reading it, this should work. I have taken the PCB board off my drive possible 50-60 times without incident, but be extremely careful when unscrewing and screwing it back on with the power connected!!!!

Thanks,
G

[Shuky]

arnd, on Jan 18 2009, 07:02 PM, said:

Gradius2, on Jan 18 2009, 06:34 PM, said:

Fixing 0 LBA error:

To correct 0 LBA error, you'll need to do a quick format in order to regenerate the partition, just with m0,2,2 and the rest can be left blank by putting only commas or filling out with zeros. At the end you need to use a "ValidKey" code, or 22. So we'll have to enter:

F3 T>m0,2,2,0,0,0,0,22 (enter)

Gradius,

a question: Will the quick format wipe out / erase the existing data?

Thanks, Arnd

No, just use Partition recovery or "A-FF Find and Mount"

and copy your data safely..
i just yesterday do some translation recalculate , on my 0 LBA ST3320613AS.

[Leigh.Wanstead]

May I ask if seagate checker says the hard disk not effected and if I follow the conclusion to continue using the hard disk and do have the hard drive broken later. Will any compenstation for this legal ground?

[Gradius2]

I created a new topic about the solution here:
http://www.msfn.org/...howtopic=128807

Please, no offtopic there.

Thanks,
Gradius

[Shuky]

Leigh.Wanstead, on Jan 18 2009, 08:00 PM, said:

May I ask if seagate checker says the hard disk not effected and if I follow the conclusion to continue using the hard disk and do have the hard drive broken later. Will any compenstation for this legal ground?

My ST3320613AS is also not affected, but 0 LBA is show ,and now repaired;)

[ViniciusFerrao]

Gladius2 method works? O.O

Amagod! \o/

[fatlip]

I have a drive on the way here now to see 100% if this works. It should be here within the hour.

G

ViniciusFerrao, on Jan 18 2009, 12:44 PM, said:

Gladius2 method works? O.O

Amagod! \o/

[tuning1]

fatlip, on Jan 18 2009, 01:47 PM, said:

I have a drive on the way here now to see 100% if this works. It should be here within the hour.

G

ViniciusFerrao, on Jan 18 2009, 12:44 PM, said:

Gladius2 method works? O.O

Amagod! \o/

Data lost or okay

[fatlip]

tuning1, on Jan 18 2009, 01:00 PM, said:

fatlip, on Jan 18 2009, 01:47 PM, said:

I have a drive on the way here now to see 100% if this works. It should be here within the hour.

G

ViniciusFerrao, on Jan 18 2009, 12:44 PM, said:

Gladius2 method works? O.O

Amagod! \o/

Data lost or okay

there should be no data loss. This is writing to the System Area of the hard drive.

[CJohnson1073]

Seagate claims to be offering a free data recovery service for bricked drives. Has anyone used this service yet? Was it successful? I am a little leary about sending the drive out and losing my data. The info can be found in the following article from computerworld.

http://www.computerworld.com/action/articl...ticleId=9126280

CJohnson1073

[fatlip]

This was just announced on Friday, so I doubt anyone has used the "free" option yet.

CJohnson1073, on Jan 18 2009, 01:17 PM, said:

Seagate claims to be offering a free data recovery service for bricked drives. Has anyone used this service yet? Was it successful? I am a little leary about sending the drive out and losing my data. The info can be found in the following article from computerworld.

http://www.computerworld.com/action/articl...ticleId=9126280

CJohnson1073

[gvsyn]

Excellent guys, just tried the recovery commands, rebooted, bam! OS straight up, no problems so, ones you've got the RS232 connection sorted, it's about 10mins to fix the disc.

Again MASSIVE thanks to fatlip for the RS232 setup, pichi for the BSY resetting and Gradius2 for digging up the LBA0 fix \o/

This post has been edited by gvsyn: 18 January 2009 - 03:56 PM

[verdilith]

I have a 500GB ST3500320AS drive, 7200.11, SD15 firmware.

Without any warning, it died two days ago. I could hear it working, but it wasn't even being detected in the BIOS. A lot of internet searching about this has led me here, so I could add my experience.

The first ST3500320AS drive I got was DOA. I had the replacement 6 months before it died on me on Friday. The company I got it from (I'm based in the UK) said they would send me a replacement. They said that they only considered "other options" when at least three drives had died. I feel like I am working with a time bomb.

When I read that Seagate had some kind of firmware fix for this, it eased the annoyance and frustration a bit, but trying to contact them to ask about the firmware patch was a nightmare.

I have got to the point where I am expecting a replacement HDD, but am leery about using it - in fact, I *want* it to die on me so I can get something completely different.