[icefloe01]

cdturri, on Jan 18 2009, 05:42 PM, said:

I presume this is because the tool was complete rubbish and a lot of people reported that they bricked drives were shown as "not affected".

Affected drives were being reported as NOT affected because people were not putting in all capital letters. Seagate probably took the tool offline to rewrite it so it would not matter if the letters were capital or not. I'll bet it will be back up before too long. It was just a careless programming error I'd bet.

[quattro150]

Excellent!!! I'll try it once I get home from work today....
*keeping fingers crossed*

pichi, on Jan 19 2009, 11:11 AM, said:

I hadn't BSY problem, only 0 GB problem.
I have followed these steps:

G-List Erase:
---------------
Ctrl+z
F3 T>i4,1,22
F3 T>
(Power off and power on)

Translator regeneration:
----------------------------
Ctrl+z
F3 T>m0,2,2,0,0,0,0,22
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 00, Max Certify Rewr
ite Retries = 0000
User Partition Format Successful - Elapsed Time 0 mins 00 secs
F3 T>/2
F3 2>Z
Spin Down Complete
Elapsed Time 0.147 msecs
F3 2>
(Power off)

I have connected the hdd to SATA port and after reboot:
ALL ARE OK
THE HDD WORKS

Thanks you, thanks Gradius2, fatlip and all the people that have collaborated.

[killerB]

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

$eagate release new firmware "SD1A" for ST3500320AS, ST3640330AS, ST3750330AS, ST31000340AS. (SD15, SD16, SD17, SD18, SD19, AD14 Firmware)

Quote

!!WARNING!!
The software and information in this article could be data destructive and/or render your hard drive inoperable if not followed carefully. It is always recommended to keep a backup of critical data.

Please verify your drive model number, serial number, and firmware revision using the Drive Detectsoftware.

If your drive has one of the following firmware revisions: SD15, SD16, SD17, SD18, SD19, or AD14, click here to download the SD1A update.

Please see How do I use a bootable ISO image downloaded from your site? for assistance burning a CD using an ISO image.

If your drive matches one of the models listed in this article and does not match any of these versions of firmware, your drive is not affected.
If you are still unsure if this applies to your drive, please submit an email to disksupport@seagate.com. Please enter the model number, serial number, and firmware revision into the subject line of the email.

I'm curious... Ready but size is 0GB. => Update firmware to SD1A => will Harddisk repair?

This post has been edited by killerB: 19 January 2009 - 12:51 AM

[Jackie78]

icefloe01, on Jan 19 2009, 04:30 AM, said:

cdturri, on Jan 18 2009, 05:42 PM, said:

I presume this is because the tool was complete rubbish and a lot of people reported that they bricked drives were shown as "not affected".

Affected drives were being reported as NOT affected because people were not putting in all capital letters. Seagate probably took the tool offline to rewrite it so it would not matter if the letters were capital or not. I'll bet it will be back up before too long. It was just a careless programming error I'd bet.

This is definitely not true. I have entered several serial numbers from the failed-drives Thread in Caps into the Seagate tool, most of them were reported as being not affected. So the tool was definitely not covering all drives. Besides, there was no plausibility check, if you entered any string that the tool could not identify, it always reportet "Not affected" too, which lead to even more confusion.

I really hope that Seagate have indeed found out what is causing all the trouble, and provide a solution soon. Their information policy up to now really is a catastrophy I think

[ciobi]

Jackie78, on Jan 19 2009, 02:50 AM, said:

icefloe01, on Jan 19 2009, 04:30 AM, said:

cdturri, on Jan 18 2009, 05:42 PM, said:

I presume this is because the tool was complete rubbish and a lot of people reported that they bricked drives were shown as "not affected".

Affected drives were being reported as NOT affected because people were not putting in all capital letters. Seagate probably took the tool offline to rewrite it so it would not matter if the letters were capital or not. I'll bet it will be back up before too long. It was just a careless programming error I'd bet.

This is definitely not true. I have entered several serial numbers from the failed-drives Thread in Caps into the Seagate tool, most of them were reported as being not affected. So the tool was definitely not covering all drives. Besides, there was no plausibility check, if you entered any string that the tool could not identify, it always reportet "Not affected" too, which lead to even more confusion.

I really hope that Seagate have indeed found out what is causing all the trouble, and provide a solution soon. Their information policy up to now really is a catastrophy I think

Well, now they recommend everybody with SD15, SD16, SD17, SD18, SD19, or AD14 to upgrade to SD1A, so there's no point in having a S/N check tool. I think they all may exhibit the problem; it's just that the drives made in Thailand with SD15 during some period of time are significantly more likely than the others to run into this issue. Is the SD15 firmware for drives made in Thailand different from the SD15 for those made in China? I kind of doubt it, and I think the reason drives made in Thailand failed a lot more than those made in China because of slight mechanical differences in the parts used. IIRC, there are several bricked drives that were made in China. If that is true, all drives will fail under the "right" circumstances, so it makes sense to change the firmware for all of them. I guess they first wanted to limit the scope of the issue by using the S/N check tool, but then changed their minds (either gave up or perhaps it's better for PR.)

[cdturri]

Check this post: http://forums.seagate.com/stx/board/messag...e.id=5287#M5287

Basically everyone is trying to apply the FW to the 1 TB drives and it's failing. How dumb are these guys? They can't even check that the FW works before releasing it? Seagate sucks!!!

[rozak]

Well, the firmware from Seagate does not load. I can successfully scan the drive, but the loading procedure aborts with exception error. Go figure...

I have tried everything: 3 PCs, AHCI/IDE Compatible/IDE Enhanced mode, with the drive being the only SATA/IDE device, but still the same.

Model: ST31000340AS
P/N: 9BX158-303
Firmware: SD15
Date code: 09086

According to the serial number check tool this drive IS affected.

I have opened a case with Seagatea and I am waiting for the outcome (I hope the drive does not fail until then).

[gestalt]

rozak, on Jan 19 2009, 04:51 AM, said:

Well, the firmware from Seagate does not load. I can successfully scan the drive, but the loading procedure aborts with exception error. Go figure...

I have tried everything: 3 PCs, AHCI/IDE Compatible/IDE Enhanced mode, with the drive being the only SATA/IDE device, but still the same.

Model: ST31000340AS
P/N: 9BX158-303
Firmware: SD15
Date code: 09086

According to the serial number check tool this drive IS affected.

I have opened a case with Seagatea and I am waiting for the outcome (I hope the drive does not fail until then).

I just read in a german forum that HDDs with P/Ns ending in -303 do not work with this iso, only endings of -300

No luck for me as well, I have ST3500320AS, Firmware: SD15, online check says my drive is affected, but the booting from the update cd ends with "FreeDOS" on the screen with a blinking cursor.

[cdturri]

It sounds like you have some FreeDOS issues. Try booting with the same CD in another PC or a laptop. If it doesn't work try burning the CD a lower speeds. If it works then your PC might not be able to boot with FreeDOS. Try changing some BIOS setting, like disabling all periphetrals etc.

[gestalt]

cdturri, on Jan 19 2009, 06:26 AM, said:

It sounds like you have some FreeDOS issues. Try booting with the same CD in another PC or a laptop. If it doesn't work try burning the CD a lower speeds. If it works then your PC might not be able to boot with FreeDOS. Try changing some BIOS setting, like disabling all periphetrals etc.

Thx,
trying now...

[Flyover]

gestalt, on Jan 19 2009, 06:17 AM, said:

I just read in a german forum that HDDs with P/Ns ending in -303 do not work with this iso, only endings of -300

No luck for me as well, I have ST3500320AS, Firmware: SD15, online check says my drive is affected, but the booting from the update cd ends with "FreeDOS" on the screen with a blinking cursor.

This happened to me when I had my ICH9R controller set to RAID mode. If you have that controller, change it to IDE or AHCI in the BIOS and it should work. Of course, the actual patch probably won't.

This post has been edited by Flyover: 19 January 2009 - 05:47 AM

[gestalt]

Thanks for the advice,

I got it to boot by reburning the .iso (**** Nero )

As you predicted it still didn't work. I got the "Error: Specific model not found. ST3500320AS expected"-thing.

While I was at it, I pulled out the drive to find I have P/N -303 (as expected).

[benjamin08]

hello,

several people here in France reports that the firmware update cannot be applied...
The program stops after selection of "download firmware". The system reports "Segfault" ?

[cdturri]

Good you got it "working", well more like booting, not working really. I wish I could have the Engineer that coded that FW in front of me, I will tell him a few things about QA and customer service! Hundreds of users have tried already and they are just wasting our time, it seriously looks like a joke, a very bad joke.

[quattro150]

It worked, it worked!!!
Picked up where I left off last time after fixing the BSY problem... only needed 2 more commands after that. Clear G-List, then Format Partition, and I was good to go...

Now backing up all my files to the new WD I just bought... taking forever...
Let's see if any of the files got damaged by this whole episode, I hope not...

Now what am I gonna do with this brick?

Thank you EVERYBODY for making this fix public...!!! woo hooo....

[DerSnoezie]

quattro150, on Jan 19 2009, 01:18 PM, said:

Now what am I gonna do with this brick?

- Save it. Maybe it'll make a good story for your grandchildren
- Trash it to get rid of your frustration with seagate
- Use it as guinea pig drive in other experiments

This post has been edited by DerSnoezie: 19 January 2009 - 06:24 AM

[gestalt]

It looks like seagate is preparing updates for seven more drivemodels:

http://seagate.custkb.com/seagate/crm/self...&NewLang=en

however I can't find any word on different variations of P/Ns.

[cunyat]

Hi all,
does it work the .iso? I've downloaded it and it seems to have only seagate checkdrive and i don't see anyting that could bot the system to fw the drive....

thanks all

[cdturri]

It's in a hidden part, but if you try booting with it you will get the FW update program loaded automatically. Give it a try and you will see. Don't expect the FW update to work though as no one has been able to update their drives so far.

[cunyat]

cdturri, on Jan 19 2009, 07:33 AM, said:

It's in a hidden part, but if you try booting with it you will get the FW update program loaded automatically. Give it a try and you will see. Don't expect the FW update to work though as no one has been able to update their drives so far.

ok will give a try cause if not I can't sell any hd from the shop :/

another question, has anybody info about the free recovery from seagate? about how to do it?

thx!

This post has been edited by cunyat: 19 January 2009 - 06:40 AM