01-22-2009 09:26 AM - edited 01-22-2009 09:31 AM
The update here now worked for my ST31000340AS.
Burned the image to a CD, and booted from the CD (using my SATA connected DVD-burner).
Selected option C) for the ST31000340AS, and when it reported that the update was finished, I turned off and on the system (power cycled).
FredDerfson: How do I check the cache size?
Why does it report SATA/150? Should it not be SATA/300 ?!
01-22-2009 10:50 AM
The fellow with the unreported cache was using Everest and/or HDTune to get the info. I know nothing about these apps or CrystalDiskInfo.
My concern is that the particular bricking bug may be fixed, but something else may be broken. If upgrading a functional drive, take complete before & after snapshots of all the drive info and run before & after performance tests if you can.
01-22-2009 11:10 AM
Note: If you controller supports AHCI, its a good idea to disable it in BIOS and enumerate your drives in plain SATA mode before you flash.
Also, if your HDDs are on RAID, its a good idea to disable RAID and enumerate them as standalone SATA drives - before you flash the new firmware.
I have NVIDIA 780i & 790i systems, updated my 2xST3500320AS (they were on RAID-0) in a single go without issues.
I used the MooseDT-SD1A-2D-8-16-32MB.ISO - RAID is now enabled back, and everything looks good.
01-22-2009 11:42 AM - edited 01-22-2009 11:45 AM
Looks like it's done right after starting Vista? I recommend waiting a little while until SuperFetch is done caching programs and then run hdtune. It improves the quality of the results a lot. Also happend when i checked at first with Vista x64.
Whilst SuperFetch still active:
After waiting for a little while:
My burst rate is even lower but i'm sure it runs at SATA-II mode. Every tool i tried told me the same.
01-22-2009 10:16 PM - edited 01-22-2009 10:17 PM
Question : Does the update for the model ST31000340AS SD15 affects the DATA in the disk? I mean, can I update the firmware without losing the data in the disk?
Your data is intact. Plenty of people, including myself (on the same drive as yours with P/N 9BX158-303) have done the upgrade and found that to be true.
There's plenty saying that if your drive is not visible in BIOS the upgrade won't work, but I have my doubts.
Has anyone whose drive is not visible in BIOS tried the upgrade? Please report your success or failure, and confirm the rumour or shoot it down in flames.
01-22-2009 11:18 PM
The update will not work for drives already locked in the BUSY state.
Because the drive is locked in this state, there is no way for BIOS to recognize it, therefore, no Windows or DOS based program will be able to talk to it.
The BUSY state needs to be removed, as well as some other things need to be cleaned up in the System Area of the drive before the BIOS will recognize it. At that point, the upgrade would work.