03-11-2012 01:26 PM
As the title states, I have a couple of ST2000DM01 drives and the firmware is at CC9C. I went to the update page and see that there is a new version, CC9D, but as I try to update, it gives me the "can't update" message. Yes, I did disconnect the drives and used the DOS version to update with BIOS settings at all the different drive settings. None worked. I noticed on a couple of other threads (different drive thread) that you can force the drive to update the firmware, but I do not know what the name of the file/command line is for the file. Can anyone help with this and let me know what the command line should be? Thanks.
03-12-2012 12:05 AM
03-12-2012 09:00 AM - edited 03-12-2012 09:19 AM
Thank you for all that, it really helps. My drives are ST2000DM001-9YN164 with CC9C. So far I believe I have narrowed it down to these and between those is GRCC9D4H.LOD or GRCC9D6H.LOD (as you already stated):
CC9D4H.LOD;GR753C.CCD9.AY0AAL.CC9D.C39A ST2000DM001-9YN164;GR753C.CCD9.AY08AL.CC9C.C39?;GR CC9D4H.LOD;GR753C.CCD9.AY0AAL.CC9D.C39A ST2000DM001-9YN164;GR753D.CCD9.AY04AL.CC9C.D???;GR CC9D6H.LOD;GR753D.CCD9.AY0AAL.CC9D.D39A ST2000DM001-9YN164;GR753D.CCD9.AY08AL.CC9C.D39?;GR CC9D6H.LOD;GR753D.CCD9.AY0AAL.CC9D.D39A ST2000DM001-9YN164;GR753C.CCD9.AY04AL.CC9C.D???;GR CC9D6H.LOD;GR753D.CCD9.AY0AAL.CC9D.D39A ST2000DM001-9YN164;GR753C.CCD9.AY08AL.CC9C.D39?;GR CC9D6H.LOD;GR753D.CCD9.AY0AAL.CC9D.D39A
03-12-2012 09:15 AM - edited 03-12-2012 10:25 AM
Also, I looked at the serial numbers, I have one with a 1 as the second digit and the rest a re 2's. Guessing the 1 is a 4 head and the 2 is 6 heads? The variances of the serials numbers are:
1E - (only one of these)
Also, if the drive was 6 heads, what is the command? I am not sure what the sequencing would be. Kinda like this: FDL487A -m Anak -f GRCC9D6H.LOD -i ST2000DM001 -s -x -b -v -a 20 (The highlighed in red I know is wrong, but what should it be?) Am I close?
03-12-2012 01:42 PM
03-12-2012 02:02 PM
I will test them with that, but they are in a USB enclosure attached to my server pool, so I might run into a transfer limitation of the USB interface. The reading might not reflect true trasfer speeds.
03-12-2012 02:39 PM
03-12-2012 09:48 PM
No, I would not do a firmware update through a UBS enclosure. As for the DOS tests, I shut down my server, pulled the disk and attached it to a SATA cable from one of my spare computers. The DOS test does not write info to the drive, only in the RAM. The reason I am hesitant to do a data transfer test outside of the USB is because I don't want the computer to add any unnecessary info to the drive that might jeopardize the placement back into my server pool. I have multiple drives and removing them to test each one from the pool takes FOREVER. As for getting mad if the firmware goes awry, I would never do that. I know the risks and things happen when you tinker.
03-13-2012 09:08 AM - edited 03-13-2012 09:31 AM
Just to do a follow up, I had the serial numbers checked and was told, as you stated, the numbers no longer indicate the drive info. All the drives had 4 heads, so I would assume (if I decide to do it) the command would be?:
FDL497A -m Grenada -f GRCC9D4H.LOD -i ST2000DM001 -s -x -b -v -a 20
03-13-2012 04:49 PM