02-17-2009 09:53 AM
Maybe a better reasponse would be to create threads with links to other threads about specific issues, because this throw-it-all-together approach looks like you are just trying to make the problem seem so wide spread.
On the other hand, they could actually ADDRESS the issue and fix all these bolloxed up drives. I know, what a crazy thought.
02-17-2009 12:10 PM - edited 02-17-2009 12:11 PM
I am still trying to perform the firmware upgrade on my STE3500320AS, and the CD with the ISO image returns the error appearing in this screen pic.
Yes, I have read the posts regarding "Invalid opcode" and they generally recommend to either enable or disable AHCI in system BIOS (yes, both are recommended in different posts). Unfortunately, they provide no help on HOW to do this! I have searched my motherboard BIOS settings in vain for any such setting. The mobo manual doesn't even MENTION AHCI (I searched the PDF). So now I am at a dead end -- I cannot get the FreeDOS-based firmware update to work (and I have TWICE downloaded the ISO image and created CDs using the latest version of ISO Recorder. Can anyone help?
Has anyone made any progress on this? I am hooking the Seagate drive up to an XP computer with an nvidia2 chipset that does not appear to offer AHCI as an option. The SATA controller is a SiI 3112A that operates only in non-AHCI (IDE) mode.
02-17-2009 12:39 PM
Has anyone made any progress on this? I am hooking the Seagate drive up to an XP computer with an nvidia2 chipset that does not appear to offer AHCI as an option. The SATA controller is a SiI 3112A that operates only in non-AHCI (IDE) mode.Message Edited by howardrg on 02-17-2009 12:11 PM
I don't know if I ultimately had to do this, but I once had a pair of drives that were having issues and Seagate sent me a new firmware to flash for them. These drives were running with an old Asus A7N8X-E Deluxe MB and they didn't want to flash on that system for some reason (I didn't try too hard though). I ended up flashing them using a different motherboard and they flashed without issue. I still have those drives in use today and haven't had any issues since.
02-17-2009 01:01 PM
02-17-2009 01:05 PM
Since we're not allowed to use different threads I'll post this here as well.
As someone else found these images for SD1A are different. The moderators suggested that there was no proof of a difference.
We'll here it is !!
MD5 (MooseDT-SD1A-3D4D-16-32MB.ISO) = c89bfea8b87701ceb8e9c8ab686ca756
MD5 (MooseDT-SD1A-3D4D-16-32MB_newer.ISO) = 400c9cdfb6c78944a483fcc692a8cd57
Could be random difference caused by packaging etc.?? Read on...
I extracted the files from within the ISO, the bootsector within that, and then the zip file inside that.
$ diff -r --brief MooseDT-SD1A-3D4D-16-32MB*
Files MooseDT-SD1A-3D4D-16-32MB/boot/flash.bat and MooseDT-SD1A-3D4D-16-32MB_newer/boot/flash.bat differ
Files MooseDT-SD1A-3D4D-16-32MB/boot/SD1A3D4D.LOD and MooseDT-SD1A-3D4D-16-32MB_newer/boot/SD1A3D4D.LOD differ
Details of the flash.bat change !!, Including the new line "REM (January 29, 2009)" which kind of proves a difference !!!
Changes were too big to be allowed in this post, so here there are. Left column is the original SD1, right column is the new one:
I'll have a look at the differences in the LOD files later.
02-17-2009 01:07 PM
Since you seem to want to bury all questions into one thread, can you respond to this question here?
[From original thread here]
I can confirm yunsile's findings. I downloaded MooseDT-SD1A-2D-8-16-32MB.ISO for the ST3500320AS drives on 1/21/2009. The hashes are as follows:
I just downloaded this ISO again from the official download page and here are the new hashes:
Looks like this file was updated on 2/9/2009:
User-Agent: Sam Spade 1.14
HTTP/1.1 200 OK
Last-Modified: Mon, 09 Feb 2009 23:01:32 GMT
Date: Tue, 17 Feb 2009 20:18:38 GMT
Seagate - can you clarify what was changed? Silent changes (unannounced changes without updates to the version number) make me nervous because it then becomes impossible to know which firmware is on a drive by examining the version number...which is the whole point of the version number.
02-17-2009 01:32 PM
I have two ST3500320AS drives, made in China, both in the first half of 2008.
The serial checker in january said that they were not affected, but people were reporting bricked drives with the serial checker saying not affected.
I have upgraded to SD1A but now I am getting occasional Event ID 55 errors:
"The file system structure on disk is corrupt and unusable. Please run the chkdsk utility on the volume"
What are other peoples experiences with SD1A and corruption? I never had a problem on SD15.