Seagate firmware issues

J

JohnnyQ

Senior Member
Joined
Sep 29, 2005
Messages
655
Reaction score
1
Location
CT Pampoenkraal
How many of you have reflashed these potential faulty drives, with the new firmware, and did you do it with your data still on?
Was it successful, and was your data still intact?
Did the drives remain stable after the flash?

I have a 750 and a 500, that have the problematic firmware version. Nothing has gone wrong yet, but both are full and it would be sad to loose the data on those drives.
 
I flashed a 500GB running Windows Server 2008 with Exchange 2007 and when it was complete and restarted all was 100%. Been fine ever since.
 
JohnnyQ said:
How many of you have reflashed these potential faulty drives, with the new firmware, and did you do it with your data still on?
Was it successful, and was your data still intact?
Did the drives remain stable after the flash?

I have a 750 and a 500, that have the problematic firmware version. Nothing has gone wrong yet, but both are full and it would be sad to loose the data on those drives.
Click to expand...

It should be save but I would still recommend making backups before doing anything dramatic on any drive. :D
 
I flashed 4 x 500gb in a raid array. I did not want to have issues and thankfully there were none.
 
I am Penguin said:
It should be save but I would still recommend making backups before doing anything dramatic on any drive. :D
Click to expand...

Just make sure you use the current firmware files from the seagate site. Be carefull of the older version which could still be in the circuit.
 
This topic has made me nervous, so I checked my HDD.

It says my model number is on the affected drives list, use the serial number check.

The serial number check said it is OK.

Think this is good enough?

My firmware version is SD22 - Seagate ST3320613AS.


BTW
How good is HDDScan? Should I run the surface tests and are there any dangers I should be aware of.
(I'm new to this level of PC play and don't want to accidentally wipe my disk.)
 
Last edited:
I flashed mine with data still on it and everything was just fine. The drive hadn't exhibited any problems before that though.

FYI mine is an ST350032whatever (500gb).
 
Just done my half full 1TB drive and no problem here either..got to be plugged to Sata or eSata as it won't do it via USB nor will that drivedetect program ID the drive whilst its on usb.
Also found a Memorex CD-RW would'nt work for the boot cd but a Verbatim CD-RW would.
No problems part from those anyway.

EDIT: HD tune (free)will ID your drive model no with USB if anyones stuck wondering with external drives and no eSata.
http://www.hdtune.com/
 
Last edited:
Just thought I'd add that I've just flashed my 1TB half full of media and, thankfully, it seems fine so far. (ed, died two days later)

Did anyone else notice that the firmware downloaded from the same link, the file MooseDT-SD1A-3D4D-16-32MB.ISO changed at some point? I downloaded it before but thought I'd wait a while before flashing to see how it goes for other people, then when I decided to finally flash I downloaded it again (actually two more times so I could run a hash check on the download since Seagate doesn't mention what it's hash should be) and that's when I noticed the file has changed, odd.

EDIT:

I thought I should update this as the drive has become basically useless.
 
Last edited:
I eventually decided to take the plunge, and flashed my 750G yesterday. Guess what, drive is f#@$g unreadable afterward(with 400G of data).:mad: The pc sees it, but it is marked as unreadable in disk management. The only option i had was to convert to basic disk and lose all data. Fortunately i backed up the data first.:)
 
Plasticmonkey said:
Enlighten me: What are potential problematic firmware versions?
Click to expand...


Barracuda 7200.11
ST31000340AS SD15, SD16, SD17, SD18, SD19 Affected.
ST3750330AS SD15, SD16, SD17, SD18, SD19 Affected.
ST3750630AS SD15, SD16, SD17, SD18, SD19 Affected.
ST3640330AS SD15, SD16, SD17, SD18, SD19 Affected.
ST3640530AS SD15, SD16, SD17, SD18, SD19 Affected.
ST3500320AS SD15, SD16, SD17, SD18, SD19 Affected.
ST3500620AS SD15, SD16, SD17, SD18, SD19 Affected.
ST3500820AS SD15, SD16, SD17, SD18, SD19 Affected.
ST31500341AS All NON CC or LC versions. Do NOT flash CC or LC Drives!!!
ST31000333AS All NON CC or LC versions. Do NOT flash CC or LC Drives!!!
ST3640323AS All NON CC or LC versions. Do NOT flash CC or LC Drives!!!
ST3640623AS All NON CC or LC versions. Do NOT flash CC or LC Drives!!!
ST3320613AS All NON CC or LC versions. Do NOT flash CC or LC Drives!!!
ST3320813AS All NON CC or LC versions. Do NOT flash CC or LC Drives!!!
ST3160813AS All NON CC or LC versions. Do NOT flash CC or LC Drives!!!

Barracuda ES.2 SATA
ST31000340NS All firmware versions earlier than SN06.
ST3750330NS All firmware versions earlier than SN06.
ST3500320NS All firmware versions earlier than SN06.
ST3250310NS All firmware versions earlier than SN06.

DiamondMax 22
STM31000340AS MX15 (or higher)
STM3750330AS MX15 (or higher)
STM3500320AS MX15 (or higher)
STM31000334AS All versions
STM3320614AS All versions
STM3160813AS All versions
 
JohnnyQ said:
I eventually decided to take the plunge, and flashed my 750G yesterday. Guess what, drive is f#@$g unreadable afterward(with 400G of data).:mad: The pc sees it, but it is marked as unreadable in disk management. The only option i had was to convert to basic disk and lose all data. Fortunately i backed up the data first.:)
Click to expand...

Don't do that. If you can see it in BIOS then you can flash it again. Make sure you have the right version of the firmware. There was a bad version that was released first and then the good version was released afterwards. Also make sure that you have the right version for the part number. You can always flash back to the version you had originally on the drive (it's written on the drive) and that will work.
 
Browser said:
Just thought I'd add that I've just flashed my 1TB half full of media and, thankfully, it seems fine so far.

Did anyone else notice that the firmware downloaded from the same link, the file MooseDT-SD1A-3D4D-16-32MB.ISO changed at some point? I downloaded it before but thought I'd wait a while before flashing to see how it goes for other people, then when I decided to finally flash I downloaded it again (actually two more times so I could run a hash check on the download since Seagate doesn't mention what it's hash should be) and that's when I noticed the file has changed, odd.
Click to expand...

Thats correct. The first release was buggy and the subsequent release resolved the problems.
 
Well I thought I would add that the drive I flashed is now basically dead, another Seagate drive fails, firmware renders Seagate useless.

It's failing Seatools tests and is incredibly slow and giving numerous problems with it's contents.

Off to buy a WD and hope that works out but they're looking good lately.
 
Flashed my 1.5TB Seagate (which had the problematic firmware) to SD1B with no problems at all, still working great and no more lock-ups :)
 
Hi,

Anybody know if this Seagate 500gig drive needs to be flashed.

Its a ST350084 1NSAR0 thats in a casing and i use it as an exteral drive.
When copying via usb using total copy at max speed it only goes up to 5mb p/s.
Haven't tried copying via the sata connector yet.

Oh, is this drive good or not. New range or not.

Thanks guys
:D
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X