Seagate ST2000DM001-9YN164 Firmware Update

[Asque]

I have received a Seagate Hard Disk of Model ST2000DM001-9YN164 with firmware version HP16. The firmware version code seems odd for the Seagate drive; there may be a custom firmware loaded onto the drive.

I have attached a SpeedFan 4.48 beta 6 window image capture showing the drive Model and firmware code.

The disk seems to work but sometimes make clunking noises that are alarming. I thought that this problem could be resolved with a firmware update and proceeded to download the ISO distribution of the CC4H firmware update at: http://knowledge.seagate.com/articles/e ... Q/223651en

After invoking the firmware update DOS software, the hard disk model is successfully matched, but the update is aborted after a failure to match firmware. I believe the tool was expecting CC46, CC47, CC49, CC4C, or CC4G.

Is there more information regarding the HP16 firmware?

Should all that should be necessary to alter to successfully flash the drive is add the ST2000DM001-9YN164 drive with the HP16 to the flash tools model list?

Attachments

SppedFan 4.48 beta 6 window image capture for Seagate ST2000DM001-9YN164, firmware HP16

Seagate_ST2000DM001-9YN164_HP16.gif (15.27 KiB) Viewed 89329 times

[egavastm]

I got one of these hard disks with the HP16 firmware in a HP computer and it has the same issue. I have requested newer firmware from HP and hopefully they can provide it.

My guess is the HP16 firmware is a custom version of CC46 with all the same issues.

[poehere]

You can not update the FW with what you are trying. This is correct the HP16 is special FW from HP computers. You will have to contact HP for a FW for this drive. If HP has a FW update they should have a program for you to use to update the FW on this drive. Otherwise you will not be able to do this one with what you are using now. The HP FW Update is not for the program you are using. This only applies to normal Seagate drives and not ones a manufacture has done like the drive you have for the HP computer it came in.

[egavastm]

I contacted HP and they wanted me to RMA my computer. I have no clue if they will post an update.

I got a 2nd ST2000DM001 drive and a serial TTL cable hoping to learn if forcing a firmware update is worth the risk. As you can see below the two drives I have are not comparable.

ST2000DM001-9YN164 HP16 Firmware
--------------------------------
Grenada Luxor 2.1 RAP22 - GR Hda DH, DETCR, 4K Zest
Product FamilyId: 58, MemberId: 04
HDA SN: Z1Exxxxx, RPM: 7199, Wedges: 188, Heads: 4, OrigHeads: A, Lbas: 00001D273EAC, PreampType: CB 16
PCBA SN: 0000xxxxxxxx, Controller: LUXORL_2_1( 202)(FF-FF-FF-FF), Channel: ITERATIVE, PowerAsic: MCKINLEY DESKTOP LITE Rev 15, BufferBytes: 4000000
Package Version: GR753C.HPD1.BK06B8.HP16 , Package P/N: 100707026, Package Global ID: 00188399,
Package Build Date: 04/26/2012, Package Build Time: 10:25:04, Package CFW Version: GR75.HPD1.00446199.00188399,
Package SFW1 Version: C3A7, Package SFW2 Version: ----, Package SFW3 Version: ----, Package SFW4 Version: ----
Controller FW Rev: 04261025, CustomerRel: HP16, Changelist: 00446199, ProdType: GR75.HPD1, Date: 04/26/2012, Time: 102504, UserId: 00188399
Servo FW Rev: C3A7
RAP FW Implementation Key: 16, Format Rev: 0002, Contents Rev: 61 02 00 00
Features:
- Quadradic Equation AFH enabled
- VBAR with adjustable zone boundaries enabled
- Volume Based Sparing enabled
- IOEDC enabled
- IOECC enabled
- DERP Read Retries enabled v. 3.8.00.0000000000001FF7
- LTTC-UDR2 disabled

ST2000DM001-1CH164 CC26 Firmware
--------------------------------
GrenadaBP LuxorPlus2 4K, GPF1 MC with new serpent DFW
Product FamilyId: 58, MemberId: 04
HDA SN: Z1Fxxxxx, RPM: 7199, Wedges: 188, Heads: 5, OrigHeads: A, Lbas: 00001D273EAC, PreampType: CC 16
Bits/Symbol: C, Symbols/UserSector: BEB, Symbols/SystemSector: 1A5
PCBA SN: 0000xxxxxxxx, Controller: LUXORLPLUS_2_0( 203)(FF-FF-FF-F, Channel: STX_DUNRAVEN, PowerAsic: Unknown Rev 00, BufferBytes: 4000000
Package Version: GPG17C.CCD2.CB0487.CC26 , Package P/N: 100720588, Package Global ID: 00410638,
Package Build Date: 12/13/2012, Package Build Time: 13:56:37, Package CFW Version: GPG1.CCD2.00515436.00410638,
Package SFW1 Version: C7EA, Package SFW2 Version: ----, Package SFW3 Version: ----, Package SFW4 Version: ----
Controller FW Rev: 12131356, CustomerRel: CC26, Changelist: 00515436, ProdType: GPG1.CCD2, Date: 12/13/2012, Time: 135637, UserId: 00410638
Servo FW Rev: D7EA
TCG IV Version: n/a
Package BPN: 18
RAP FW Implementation Key: 16, Format Rev: 0004, Contents Rev: 71 01 07 00
QNR Container: 1
Features:
- Quadradic Equation AFH enabled
- VBAR with adjustable zone boundaries enabled
- Volume Based Sparing enabled
- IOEDC enabled
- IOECC enabled
- DERP Read Retries enabled v. 4.7.01.0000000000000017
- LTTC-UDR2 enabled
- SuperParity disabled
- Humidity Sensor disabled
- Background Reli Activity Critical Event Logging disabled

[poehere]

Do as HP says on this one. You can not do this like I explained before. HP16 is special FW for their drives. Send it in and get it fixed from factory if you want it fixed. The more you screw around with this one then you loose your chance to get it fixed from them. Good luck I can not tell you more on this one. You can not do what you want.

[egavastm]

I was able to flash my HP16 drive to CC4H and here is how I did it.

Boot from the CC4H SeaFlash for DOS CD.

Press Esc at the README.TXT, press Z to exit the selection menu and then press enter at the "Turn off the power now."

You should have a dos prompt now. The following command will flash your HDD. Make sure you only have one HDD connected.

FDL497A -m Grenada -f GRCC4Hxx.LOD -i ST2000DM001 -s -x -b -v -a 20

Once you see "Success" power your computer off.

Note: The GRCC4Hxx.LOD must be replaced by the correct firmware for your drive based on the number of heads it has. If the third letter of the serial number is E it should have 4 heads (GRCC4H4H.LOD). I checked the number of heads with a serial TTL cable.

Lastly don't blame me if this bricks your drive. I haven't fully tested my drive but it is currently 31% done rebuilding my RAID 1 array (I now have a matched firmware and number of platters).

[Col]

well done!

[Asque]

Thanks for your solution egavastm.

I have not yet tried the flash.

[int0x13]

I was able to flash my HP16 drive to CC4H and here is how I did it.

Boot from the CC4H SeaFlash for DOS CD.

Press Esc at the README.TXT, press Z to exit the selection menu and then press enter at the "Turn off the power now."

You should have a dos prompt now. The following command will flash your HDD. Make sure you only have one HDD connected.

FDL497A -m Grenada -f GRCC4Hxx.LOD -i ST2000DM001 -s -x -b -v -a 20

Once you see "Success" power your computer off.

Note: The GRCC4Hxx.LOD must be replaced by the correct firmware for your drive based on the number of heads it has. If the third letter of the serial number is E it should have 4 heads (GRCC4H4H.LOD). I checked the number of heads with a serial TTL cable.

Lastly don't blame me if this bricks your drive. I haven't fully tested my drive but it is currently 31% done rebuilding my RAID 1 array (I now have a matched firmware and number of platters).

I had a seagate 3TB CC4H firmware that was not reliable at all, so i'm not sure that updating to CC4H was a good solution.
Since then did you have any issue with that drive?

[fzabkar]

Mixing OEM firmware with retail firmware is very dangerous, even when things appear to be matched. In fact it is not always safe to mix retail versions, either. For example, Seagate warns that applying 7200.11 SDxx firmware to a drive with CCxx firmware will render it inoperable.

The OP's example shows a ST2000DM001-9YN164 OEM drive and a ST2000DM001-1CH164 retail drive. The model number suffixes denote two completely different architectures, as is confirmed by the terminal log. You must not apply 9YN164 firmware to a 1CH164 drive or vice versa.

Seagate's update packages include a configuration file. This file determines whether the user's drive is a suitable candidate for the update, and then applies the appropriate firmware image to the drive.

Here are the configuration files for the CC4C, CC4D, CC4H and CC9D updates:

http://www.users.on.net/~fzabkar/HDD/GRCC4CD9.TXT
http://www.users.on.net/~fzabkar/HDD/GR-CC4H.TXT

The files would suggest that CC9D firmware must not be applied to CC4x drives and vice versa.

Here is a Dell update that appears counterintuitive:

http://www.users.on.net/~fzabkar/dell_fw_cfg.txt

Notice that 0003SDM1 firmware is updated to 0004SDM1, and 0002SDM1 is updated to 0005SDM1.

However, the configuration file applies 0004SDM1 firmware to D003SDM1 and 0001DEM1 drives, so in this case mixing OEM and retail firmware appears OK.

Here is another case where one can go wrong:

http://www.users.on.net/~fzabkar/HDD/SN06BCFG.TXT

ST31000340NS MS01BB.SDN1.SN0421.SN04.b0fa SN06b.lod
ST31000340NS MS01BB.SDN1.SN0424.SN04.b0fa SN06b.lod
ST31000340NS MS03BB.SDN1.AJ0309.CN04.B0FE SN06b.lod
ST31000340NS MS03BB.SDN1.AL0P00.SN05.B101 SN06b.lod
ST31000340NS MS03BB.SDN1.AU0200.AN05.B101 SN06b.lod

http://www.users.on.net/~fzabkar/HDD/SN16BCFG.TXT

ST31000340NS MS010B.SDN2.SN04N7.SN04.B0FA SN16b.lod
ST31000340NS MS01B0.SDN2.N36100.SN03.B0FA SN16b.lod
ST31000340NS MS031B.SDN2.AU0100.SN15.B101 SN16b.lod
ST3750330NS MS010B.SDN2.SN04N7.SN04.B0FA SN16b.lod
ST3750330NS MS01B0.SDN2.N36100.SN03.B0FA SN16b.lod
ST3750330NS MS031B.SDN2.AU0100.SN15.B101 SN16b.lod

For example, notice that SN04 firmware upgrades to SN06 in the first case, but upgrades to SN16 in the second case. The difference is in the drive's part number.

Here is yet another possible pitfall:

http://www.users.on.net/~fzabkar/HDD/PH-CC46.TXT

ST316031?AS;PH0G2?.CCD3.AA????.CC3?.C2??;PHCC461H.LOD;PH0G2C.CCD4.GZ019Y.CC46.C26C
ST316031?AS;PH0G2?.CCD3.AA????.CC3?.D2??;PHCC462H.LOD;PH0G2D.CCD4.GZ019Y.CC46.D26C

Notice that the ST316031?AS drives come in 1-head and 2-head versions, each requiring a different LOD file (PHCC461H.LOD versus PHCC462H.LOD).

However, the same configuration file would suggest that one can mix certain OEM (HPxx) and retail firmware in this particular case:

ST316031?AS;PH0G2?.HPD1.BZ????.HP1?.C2??;PHCC461H.LOD;PH0G2C.CCD4.GZ019Y.CC46.C26C
ST316031?AS;PH0G2?.HPD1.BZ????.HP1?.D2??;PHCC462H.LOD;PH0G2D.CCD4.GZ019Y.CC46.D26C
ST316031?AS;PH0G2?.HPD2.DS????.HP2?.C2??;PHCC461H.LOD;PH0G2C.CCD4.GZ019Y.CC46.C26C
ST316031?AS;PH0G2?.HPD2.DS????.HP2?.D2??;PHCC462H.LOD;PH0G2D.CCD4.GZ019Y.CC46.D26C
ST316031?AS;PH0G2?.HPD4.AA????.HP0?.C2??;PHCC461H.LOD;PH0G2C.CCD4.GZ019Y.CC46.C26C
ST316031?AS;PH0G2?.HPD4.AA????.HP0?.D2??;PHCC462H.LOD;PH0G2D.CCD4.GZ019Y.CC46.D26C

I have examined some firmware update packages and found that they generally replace the entire ROM on the PCB (older models), or the ROM's code modules (F3 architecture). Some updates also replace one or more of the SA overlay modules (in a reserved area on the platters). When firmware is updated, one must be certain that the new modules are compatible with the existing ones, otherwise the drive will be rendered inoperable.

Analysis of Seagate F3 Firmware Update and Seagate LOD firmware image file:
http://www.alexsoft.org/viewtopic.php?f=59&t=816

ZOC scripts - Seagate LOD files parsing:
http://www.alexsoft.org/viewtopic.php?f ... 815&p=3162

Tip: Locating ROM and SA resources in firmware updates:
http://www.alexsoft.org/viewtopic.php?f=59&t=705

BTW, don't be surprised if the latest Barracuda update doesn't work. The configuration file has a bug that points the updater to a non-existent LOD file. I reported this bug to Seagate more than 2.5 years ago, and supplied a workaround in their forum (rename the files at the DOS prompt). However, their old forum was flushed down the toilet on April Fool's Day of this year, and the bug was still present some two years afterwards, according to feedback at Tom's Hardware.

[egavastm]

The two drives I have running CC4H are still working. Only one of them had the HP16 firmware. The other was a refurbished unit I got off of eBay and was upgraded to CC4H at the factory.

CrystalDisk does show some issues with the drive I upgraded to CC4H from HP16. I'm not sure if this is related to the forced firmware upgrade.

Attachments

[fzabkar]

As I suspected, your OEM and retail firmware are incompatible. It may be that normal operation of the drive is OK, but clearly the HP16 SMART module is incompatible with CC4H.

For example, notice that the numbers for the HP16 Command Timeout attribute (BC) actually belong to the following High Fly Writes attribute (BD), and the numbers for the High Fly Writes attribute belong to the Airflow Temperature attribute. That's because the additional B4 attribute has shifted everything down by one.

Similarly, the Load/Unload Cycle Count is actually the Temperature attribute, the Uncorrectable Sector Count is actually Head Flying Hours, and UDMA CRC Error Count is actually Total Host Writes.

[fzabkar]

This hybrid screenshot suggests that the drive is correctly updating its SMART parameters internally, but is incorrectly reporting them to the host.

[farles]

fzabkar,

I'm trying to update the firmware on my ST2000DM001-9YN164 running CC9C.

I noticed you mentioned above that there is a bug in the CC9D update utility. Can you tell me how to rename the file to get this to work? I've been searching everywhere to try to resolve the problem, but no luck so far.

Thanks!

[fzabkar]

@farles, can you post a link to your update? Otherwise, if it's not available via a direct download, could you upload it here?

[farles]

This should be the correct link:

https://apps1.seagate.com/downloads/certificate.html?action=performDownload&key=1114783357844

[fzabkar]

If you unpack the ISO with 7Zip, you will find a flash-m.bat file in LOD.ZIP.

The command that performs the update is ...

Code:

fdl497a.exe -s -x -b -v -a 20 -h GR-CC9D.CFS

The configuration file, GR-CC9D.CFS, contains an update matrix that screens suitable candidates and matches them against one of three LOD firmware image files.

GRCC9D2H.LOD
GRCC9D4H.LOD
GRCC9D6H.LOD

I'm assuming the filename reflects the Grenada family, CC9D firmware, and models with 2/4/6 heads.

After decoding the CFS file, we can see the following update matrix:

Code:

020410
#GRENADA RE-FRESH CODE SBS 570 TAB - MC DISABLED

# 1 DISK 2 HEAD CONFIGURATIONS
ST1000DM003-9YN162;GR753B.CCD9.AY04AL.CC9C.B???;1TBCC9D.LOD;GR753B.CCD9.AY0AAL.CC9D.B39A
ST1000DM003-9YN162;GR753B.CCD9.AY08AL.CC9C.B39?;1TBCC9D.LOD;GR753B.CCD9.AY0AAL.CC9D.B39A

# 2 DISK 4 HEAD CONFIGURATIONS
ST2000DM001-9YN164;GR753C.CCD9.AY04AL.CC9C.C???;2TBCC9D.LOD;GR753C.CCD9.AY0AAL.CC9D.C39A
ST2000DM001-9YN164;GR753C.CCD9.AY08AL.CC9C.C39?;2TBCC9D.LOD;GR753C.CCD9.AY0AAL.CC9D.C39A

# 3 DISK CONFIGURATIONS, 2TB CAN BE 5 OR 6 HEAD CONFIGURATIONS
ST2000DM001-9YN164;GR753D.CCD9.AY04AL.CC9C.D???;3TBCC9D.LOD;GR753D.CCD9.AY0AAL.CC9D.D39A
ST2000DM001-9YN164;GR753D.CCD9.AY08AL.CC9C.D39?;3TBCC9D.LOD;GR753D.CCD9.AY0AAL.CC9D.D39A

ST2000DM001-9YN164;GR753C.CCD9.AY04AL.CC9C.D???;3TBCC9D.LOD;GR753D.CCD9.AY0AAL.CC9D.D39A
ST2000DM001-9YN164;GR753C.CCD9.AY08AL.CC9C.D39?;3TBCC9D.LOD;GR753D.CCD9.AY0AAL.CC9D.D39A

ST2500DM001-9YN16L;GR753D.CCD9.AY04AL.CC9C.D???;3TBCC9D.LOD;GR753D.CCD9.AY0AAL.CC9D.D39A
ST2500DM001-9YN16L;GR753D.CCD9.AY08AL.CC9C.D39?;3TBCC9D.LOD;GR753D.CCD9.AY0AAL.CC9D.D39A

ST3000DM001-9YN166;GR753D.CCD9.AY04AL.CC9C.D???;3TBCC9D.LOD;GR753D.CCD9.AY0AAL.CC9D.D39A
ST3000DM001-9YN166;GR753D.CCD9.AY08AL.CC9C.D39?;3TBCC9D.LOD;GR753D.CCD9.AY0AAL.CC9D.D39A

The format of each line is ...

model number ; existing firmware package version ; firmware image file ; updated firmware package version

Notice that the 2-head drives are expecting a file named 1TBCC9D.LOD, 4-head drives require 2TBCC9D.LOD, and 5/6-head drives, either 2TB or 3TB, require 3TBCC9D.LOD. Since these files do not exist, the firmware update will ALWAYS fail.

The solution is to abort the update with a Ctrl-Break or Ctrl-C. This will return you to the FreeDOS prompt. Then rename the files as follows ...

Code:

ren GRCC9D2H.LOD 1TBCC9D.LOD
ren GRCC9D4H.LOD 2TBCC9D.LOD
ren GRCC9D6H.LOD 3TBCC9D.LOD

... and execute the following command:

Code:

fdl497a.exe -s -x -b -v -a 20 -h GR-CC9D.CFS

Note that the "3TB" in 3TBCC9D.LOD doesn't always reflect a 3TB model.

I reported this bug, and the solution, to Seagate about 3 years ago. Is it possibe that not one single Seagate customer has been able to update their drive in the past 3 years?

WARNING: I'm assuming that Seagate has not goofed by incorrectly naming the GRCC9DxH.LOD files. For example, the above procedure would be disastrous if the 2H LOD file was actually intended for 4H drives.

[farles]

Last night while I as waiting for my post to be approved I found another post you had with the config file decryption. I was able to use that to find the above info.

Thanks to your work I was able to install the 4 head firmware and all is working well! I was hoping this firmware removed the "chirping" problem associated with these drives, but no luck. I've decided to disable APM as that stops the sound.

Thank you again for all your help!

[Damion888]

fzabkar, genius, sheer genius! I just got four of those drives in a salvage operation and I couldn't get the firmware updated. You came along my internet winding road and saved the day...back in January...even two years before that!
=-=-=-=-=-=-=-=-=
If you unpack the ISO with 7Zip, you will find a flash-m.bat file in LOD.ZIP.

The command that performs the update is ...

Code:
fdl497a.exe -s -x -b -v -a 20 -h GR-CC9D.CFS

The configuration file, GR-CC9D.CFS, contains an update matrix that screens suitable candidates and matches them against one of three LOD firmware image files.

GRCC9D2H.LOD
GRCC9D4H.LOD
GRCC9D6H.LOD

I'm assuming the filename reflects the Grenada family, CC9D firmware, and models with 2/4/6 heads.

Cheers! Thanks and cheers again!

[longlife]

fzabkar sir,

Can u please decode the ST31500341AS upgarde ISO file to force the bios upgrade. The file in question is Brinks-4D8H-CC1H.iso. Could not attach is as there is some restriction. But the same can be downloaded from http://blog.salty.uk.com/post/Seagate-H ... grade.aspx