Jump to content


Photo

Seagate ST3400832AS firmware need, or "Why Seagate Sucks"


  • You cannot start a new topic
  • Please log in to reply
4 replies to this topic

#1 LazLong

LazLong

    Member

  • Member
  • 2 posts

Posted 13 June 2007 - 04:45 PM

I have six brand new, been sitting on the shelf for 1.5 years, Seagate ST400832AS drives with firmware 3.01. They refuse to be properly recognized by my SIL3112-based controller, nor my Oxford 924-based Firewire-SATA bridge. However, the same drive with firmware 3.02 works fine. Anyone have access to a firmware updater for this drive to something newer than 3.01?

As to why Seagate sucks, I called them asking for a firmware upgrade and was told there weren't any. I then rummaged through our stack of these drives and found one with a newer firmware, tested it and it worked, and got mad. I called Seagate with the evidence in hand, and was again told no firmware update available for 7200.8 drives as they are only actively supporting 7200.9 and .10's. Plus, their firmware repository gets updated (replaced) weekly.

Grrrrrrrrrrr!

#2 casey1132

casey1132

    Member

  • Member
  • 1 posts

Posted 30 August 2007 - 10:21 PM

I am looking to buy a ST400832AS with Firmware 3.01 and Site Code "AMK". Would you care to part with one? I'm located in Texas USA. Thanks!

#3 kboxvegas

kboxvegas

    Member

  • Member
  • 3 posts

Posted 06 September 2007 - 12:33 AM

I have six brand new, been sitting on the shelf for 1.5 years, Seagate ST400832AS drives with firmware 3.01. They refuse to be properly recognized by my SIL3112-based controller, nor my Oxford 924-based Firewire-SATA bridge. However, the same drive with firmware 3.02 works fine. Anyone have access to a firmware updater for this drive to something newer than 3.01?

As to why Seagate sucks, I called them asking for a firmware upgrade and was told there weren't any. I then rummaged through our stack of these drives and found one with a newer firmware, tested it and it worked, and got mad. I called Seagate with the evidence in hand, and was again told no firmware update available for 7200.8 drives as they are only actively supporting 7200.9 and .10's. Plus, their firmware repository gets updated (replaced) weekly.

Grrrrrrrrrrr!

If your willing to risk losing a drive try extracting the firmware then using Seagate's seatools you can load the firmware to one of the other drives to see if it works. If there is no hardware differences it should work fine.

#4 LazLong

LazLong

    Member

  • Member
  • 2 posts

Posted 07 May 2009 - 11:34 AM

I have six brand new, been sitting on the shelf for 1.5 years, Seagate ST400832AS drives with firmware 3.01. They refuse to be properly recognized by my SIL3112-based controller, nor my Oxford 924-based Firewire-SATA bridge. However, the same drive with firmware 3.02 works fine. Anyone have access to a firmware updater for this drive to something newer than 3.01?

As to why Seagate sucks, I called them asking for a firmware upgrade and was told there weren't any. I then rummaged through our stack of these drives and found one with a newer firmware, tested it and it worked, and got mad. I called Seagate with the evidence in hand, and was again told no firmware update available for 7200.8 drives as they are only actively supporting 7200.9 and .10's. Plus, their firmware repository gets updated (replaced) weekly.

Grrrrrrrrrrr!

If your willing to risk losing a drive try extracting the firmware then using Seagate's seatools you can load the firmware to one of the other drives to see if it works. If there is no hardware differences it should work fine.


How do you extract the firmware?

#5 6_6_6

6_6_6

    Member

  • Member
  • 590 posts

Posted 07 May 2009 - 05:17 PM

Wasn't 7200.8 released in 2004? And SIL3112 in 2002?

Let me understand this scenario straight...

You are running a 5-year-old drive on a 7-year-old controller... and you are experiencing problems. And Seagate sucks?

Drive manufacturers advise against a firmware upgrade for a very good reason. It is very easy to render a drive useless when a user is trying to flash firmware... and they dont want to deal with that. They would rather deal with the drives themselves in their own facilities.



0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users