Hi,

I have the following drive attached to my SATA controller (extracted from FreeAgent Desk):



The device is working properly and the (short) self test passes.

Typing the serial number into the Seagate Download Finder directed me to the SD3B ISO (Barracuda11-ALL-BRSD3B.ISO). So I burnt the ISO and booted from it. I then double checked that the ST31000333AS was indeed included in the list of supported modules as reported by the bootable flash software. Alas, trying to "download firmware to supported models" resulted in a big red FAILED message.

I suspect some manual flashing procedure is required, similar to to the one described here, but that thread was for a different model so I'm a bit reluctant to try the exact same command. I've attached a screenshot of the files I have in the FreeDOS prompt.

Thanks!

From the configuration file ...



I take no responsibility for the outcome, but the following command line should apply the firmware update.

FDL497A -m BRINKS -f BRSD3B6H.LOD -i ST31000333AS -s -x -b -v -a 20

Note that the above configuration file screens out unsuitable candidates. You will now be forcing the update to go ahead.

_________________
A backup a day keeps DR away.

Hi fzabkar,

Thanks for the quick response!
I'm not familiar with the format of the configuration file but I gather it's something like this:



So if I'm reading this correctly, my current drive should have been matched by one of these:


Now I know for sure that my device model (ST31000333AS) and firmware (SD35) match. What I'm concerned about are the other parts, namely BR120B, BP070A / BP0P0A, and B09E/ B0A3 / B0A8. What do they mean? How can I tell what my hard drive's corresponding values are so that a more educated decision could be made on whether to upgrade the firmware or not?

I'm also confused as to how the download finder would direct me to an "officially" incompatible firmware when provided with something as specific as a serial number..

Thanks again

The only way I know to see the package version is to issue a Ctrl-L via the serial terminal interface. As for what the components mean, I think they refer to the versions of certain firmware modules. I believe the last one pertains to the servo code.

_________________
A backup a day keeps DR away.

Well connecting via a serial terminal is a bit too hardcode for me at this point I theorize that my drive's exact spec doesn't match the configuration file because they didn't expect people to pry open external enclosures (FreeAgent Desk in my case) and pull out the drives from there... makes sense?

Last question then - I fully realize you're not responsible for the outcome - but from your experience, would you recommend I attempt the forced update? At MSFN they claim that not performing this specific upgrade (from SD35 to at least SD1A) is a bricking waiting to happen. SeaTools recommends the update too, BTW.

Thanks again!

The flash-m.bat file tests for the following errors:

Disk drive already has this firmware version.
Error: Specific model not found. %model% expected.
Model matched but firmware version is not compatible.
No disk drive detected. Drive not found. Drive not ready.

I don't know why your error message is not one of these.

I don't wish to recommend anything, but going by my experience at Seagate's old forum, I don't recall anyone reporting a problem after upgrading SD3x firmware to SD3x.

_________________
A backup a day keeps DR away.

Forgive me, I didn't realize the error was reported only after pressing 'c' to return to the original OS.
I'm getting the last error you mentioned:

Does this change anything?

Try temporarily reconfiguring the SATA controller in BIOS for legacy or IDE mode.

_________________
A backup a day keeps DR away.

Looks like I don't have that option in the BIOS
http://dlcdnet.asus.com/pub/ASUS/mb/LGA ... B_only.pdf

The closest thing I could find was this, but I assume that's not it?

I see only AHCI or RAID. :-(

The only thing I could suggest is to try a different motherboard.

_________________
A backup a day keeps DR away.

So, to sum up - our current theory is that it's not a configuration mismatch issue, rather the fact that the flasher can't even see the drive?
To test that assumption, I could try the command-line you gave me to forcefully update the firmware, which we expect will fail for the same reason - correct?

BTW I was able to update a Samsung SpinPoint F3 firmware from FreeDOS, if that's relevant (http://knowledge.seagate.com/articles/e ... Q/223631en).

Yes, you could try the command line.

If you examine flash-m.bat, you will see that the command that scans for available HDDs is seaenuma. However, the command that executes the update is fdl497a.exe. I suspect that the former is able to communicate with your SATA controller whereas the latter cannot.

_________________
A backup a day keeps DR away.

Actually, it looks like neither one can communicate with the drive
The command-line failed as we expected, but even seaenuma reported "no controllers".

Well, mystery solved. Thanks a lot for all your help!!
I actually posted specifically in this forum because I saw you were active here.. what can I say, I'm a fan

Now, to find some unsuspecting soul with legacy IDE support in their board...

Well, I connected the hard drive to my sister's ancient motherboard which doesn't even have AHCI and sure enough, the upgrade proceeded without hickup!
Yet another satisfied fzabkar customer

I think my next project would be to update my other FreeAgent Desk drive (this time ST31000528ASm which updates to CC49).
Will post here how I fare.