donnerzusel

Hi everybody, sorry, I've been busy the last days. Congrats, Gradius2! I found the update on the Seagate website, burned it at slowest speed possible, booted the PC and attached the drive after the POST. The Firmware SD1A-Disc boots up, and if I let it try to detect the drive, the computer hangs and messages like "invalid opcode" appear on the screen, so it seems that I'm not able to flash my drive with the new firmware. When I try to flash, I unplug every drive (because the BIOS hangs after recognizing the faulty ST31000340AS - is this the BSY-error?) and restart the computer to re-plug the ST31000 just after the POST. Strange thing: The AD14-Update-Boot-CD (which was recommended by a Seagate employee) does recognize the drive and is able to flash it again with AD14, which is not what I want. So I'm waiting again on Seagate to fix the fixed firmware. ;-) Thanks for reading. Greets, donnerzusel

Hi folks, I just registered because I have one of those Seagate Drives. xx:5QJ1****:ST31000340AS:9BX158-303:AD14:09127:WUXISG:2008-10-15:2008-01-18:OEM:donnerzusel:Germany:Failed AFTER Firmware Upgrade recommended by Seagate:Linux 2.6.28:Enermax PRO82+ 425W Strange thing: I had a chat yesterday with one of those Seagate guys. At that time, I had Firmware SD15 running and the drive was running fine. He affirmed that my drive (see above) is affected by the firmware issue. He gave me a link to a firmware update and a certificate number to access that page. I asked him if it is safe to "upgrade" the firmware from version SD15 to AD14 because I've read some posts of bricked hard drives. He assured me that the upgrade is necessary and safe to do. So I created the bootable CD, powered down the computer, disconnected everything except a CD drive and the Seagate HDD and started the upgrade. Everything went fine, I powered down the computer as requested, waited for some minutes and powered it on again. Well, and with the new firmware the BIOS reports an error while trying to access the Seagate HDD. I tried this hard disk in several other machines, it doesn't work anymore. Edit: Strangely, the BIOS still reports the full capacity of the drive, but refuses to boot if the drive is connected and reports "HARD DISK ERROR". If I put the power cable into the drive just after the POST, the computer boots happily from my first HDD (the faulty Seagate drive is just for data). The Seagate drive is unaccessible from Windows (it contains only ext3-partitions, but it is not shown in the Hardware tabs or the Drive Management) as well as from Linux. Linux is able to see and identify the drive and capacity, it reports the new firmware version (AD14) but hangs if I try to access the sectors on it. If I boot from the Seagate Firmware-Upgrade CD (using the same trick as above: replug the power after POST), the Flash-Tool recognizes the Hard Drive and is able to flash the AD14 firmware again. But it is unaccessible as well. So maybe I'm doing something wrong here or Seagate has some issues with the "new" firmware. Oh, and the online tool at the Seagate page where you put in the Serial number, tells me that my drive is affected. Of course, I backed up the data before flashing, so I don't suffer from data loss. /Edit Long story short: -ST31000340AS with Firmware SD15 (working) -Seagate support acknowledged that the drive is affected -Seagate support suggests firmware upgrade to AD14 -upgraded firmware, drive bricked. Thank you, Seagate.