05-30-2012 12:20 PM
I'm using the boot iso - doesn't work - no AV installed on the boot ISO.
It probably only works on a very few models with specfic firmware already on board.
05-30-2012 02:28 PM
I'm on a 2TB ST2000DM001, Current FIRMWARE CC4C
Tried updating using both the .exe and ISO.. From the DOS program it says FAILED in big red letters. Upon scanning for any ATA interfaces, it can't find any. ???
I've played around in the BIOS changing ACHI to regular ATA, and then the program won't even run.
Bit of a lose end now. Tried quite a few things, but consistently getting the FAILED. It was getting late, so i had to abandon and will try again later this evening.
It is my secondary, so my next steps are to remove the SSD primary, then try again.. Or throw the ST2000DM001 into my older P5Q Pro / Q6600, and try again, with just that drive installed. My current setup is a 2600k on an Asus P8Z77 V-LX mobo. (if that helps Seagate diagnose?)
Anyway, still living with my worrying chrip & screech since i'm still on the CC4C firmware. Hopefully tonight, i'll have some better luck.
Getting the same FAILED message in BIg letters
Using an Asrock Z77 MB
Still on CC4C firmware on my 2TB barracuda...
05-30-2012 03:39 PM - edited 05-30-2012 03:42 PM
Try disabling your AV when flashing and only have one drive at a time connected for those with multiple drives to do.hth.
I take it that's advice for flashing under Windows?
I would just like to say that flashing anything under Windows is generally a bad idea - more risky than flashing from plain DOS.
That said, I do have a question - can this be used to update drives via USB? I expect not - if so, what happens? Are we expected to take the drive back under warranty for an upgrade? Will Seagate upgrade external drives' firmware for us for free?
Will I void my warranty if I crack open an external USB drive *only* to upgrade the firmware?
EDIT: This firmware might stop the chirping - does it also stop the momentary lag associated with the chirping?
Will we ever get told what the chirping\lag actually is\was?
05-30-2012 04:31 PM
Yeah within Windows and I agree DOS is the best way to do things.
Anyway I've had a little head scratch and I've some optional steps for you to try.
For those with an UEFi bios, turn off the UEFi
For everyone save your bios to file and then load set up defaults, when flashing is finished load the old bios config back in.
Now this isn't a cure it's an idea and up to you if you want to have a go, what I'm getting at is the FW utility may not have been modded for UEFi use, or you could have something like a password bios protection that shuts out anything ready to come in with it's writing pen in hand, or something as simple as the Lan driver could be stopping it, it's unlikely but to give you ideas I thought I'd post it up.
05-30-2012 06:45 PM
Following on from my post # 17, I removed all my drives except ST2000DM001, and still for love nor money would it recognize my drive. My mobo is an Asus P8Z77-V LX. on a 2600k. I tried as much as i could as in, different Sata ports, playing around with ACHI etc, using the exe and the ISO, none of which helped my drive be detected from within the DOS update pgm, even though everything is detected correctly in an OS using Seagate tools and even Windows.
Anyway, I managed to fix, by pulling the drive and placing it in my older P5Q Pro running on an older Q6600..
Boom found it right away, and off it went for the update.. It was nice to hear the screech for the last time in as it went for the update.
So I will say there are some compatibilty issues with certain SATA controllers that hopefully you won't get.
Good luck fellas.
05-31-2012 02:08 AM
Updated my st3000dm001 without problems, no more chirping. Good job seagate
Can you please tell us what was your old fw version? CC4C or CC9D ? Because i still have the same error for CC4C "partition limits error" .
05-31-2012 02:43 AM
Firmware update worked perfectly for me, the noise seems to be gone.
As far as the load cycle count is concerned (granted this is in no way scientific)
1 hour of running with the new settings for APM: Increased from E1 (225) to E5 (229)
1 hour of running with APM disabled: No change whatsoever