Barracuda XT, Barracuda, Barracuda Green, DiamondMax and other desktop SATA and IDE drives

[zstef]

Let's join the club.

Same situation here.

Drive verification error after a FW upgrade.

Both ST3500320AS HDD-s currently dead!

The theory with RAID BIOS being too smart and checking the FW version seems probable, but how to solve that?

[alx_chm]

Finally, I was able to update four ST3750330AS drives with the new tool. Just to be on the safe side, before flashing, I switched the SATA controller from AHCI to IDE mode. My linux RAID10 array works fine (no problem with disk identifiers and UUIDs).

The only strange thing is that after the update, one of the drives I got as a replacement for a failed one (and that had never been used before) reports Reallocated_Sector_Ct of 4.

[KLA1973]

---

Turribeach wrote:

---

KLA1973 wrote:

---

CapSarcastic wrote:

---

KLA1973 wrote:
i can confirm they uploaded a version that WILL flash the SD1A on my two ST3500320AS drives, but after it successfully completed my ICH9R controller will no longer detect the drives in RAID mode, only in standard IDE. Considering I have a RAID array, this is a problem as you might imagine. Anyone know how to revert back to SD15 until a compatible version is released?

---

Are the drives detected in AHCI mode? Is it possible that updating the drives has broken the array, but the drives are still good?

Otherwise you're going to have to report it via the ticket system, which does actually seem to be working again and getting responses in a day or so.

---

It detects in IDE and AHCI mode, but it's not a normal broken array error. It hangs for a minute at the ICH9R screen and says "drive not validated." Normally, for a broken array it will let you enter the raid bios setup, but it can't get to that point.

---

Maybe the RAID controller is being too smart and doesn't like the drive to have changed the FW? Could you test in another PC to see if you can at least see the drive to use in a RAID? (you don't have to wipe it, just check that the ICHR9R can see the drive). If it works you might have to delete your old RAID volume and start over with a new volume...

---

I switched the drives to the other SATA controller present on my motherboard - a Gigabyte branded Jmicron in standard SATA mode. It detects the drive but Seatools fails immediately with a "drive not responding to command" error. It's probably not the Intel BIOS causing the problem, it's the drive itself. 

[Rodrigo G�mez]

---

alx_chm wrote:

Finally, I was able to update four ST3750330AS drives with the new tool. Just to be on the safe side, before flashing, I switched the SATA controller from AHCI to IDE mode. My linux RAID10 array works fine (no problem with disk identifiers and UUIDs).

The only strange thing is that after the update, one of the drives I got as a replacement for a failed one (and that had never been used before) reports Reallocated_Sector_Ct of 4.

---

Do you use a hardware RAID controller??

[miller25]

Add TWO more to the list of casualties as well for the new updater. ST3500320AS [9BX154-303] Thailand  (Original Firmeware SD15 on both). 

Getting message from BIOS -  "Primary Master Hard Disk Error"

Firmware CD sees drives with new version  SD1A.

More drives to fix, will be waiting for the next update. 

[CapSarcastic]

The 500GB image is most likely bricking drives because it's a corrupt image.

[alx_chm]

---

Rodrigo G�mez wrote:

Do you use a hardware RAID controller?? 

---

No, although my motherboard (MSI DKA790GX) has one, I found that linux RAID works faster and without the glitches.

[Ant]

---

CapSarcastic wrote:
The 500GB image is most likely bricking drives because it's a corrupt image.

---

WAIT! Isn't that only for STM3500320AS/DiamondMax 22 only? What about ST3500320AS/Seagate Barracuda 7200.11? http://img147.imageshack.us/img147/1961/updatedfor303fb9.gif for a screen capture for the firmware I want to use.

Message Edited by Ant on 01-19-2009 04:49 PM

[KLA1973]

---

CapSarcastic wrote:
The 500GB image is most likely bricking drives because it's a corrupt image.

---

That link is for the Maxtor version. The version I installed is the correct one for Seagate and the correct size (1.57 MB)

[zstef]

---

CapSarcastic wrote:
The 500GB image is most likely bricking drives because it's a corrupt image.

---

No, the image was fine, the FW is not.