Can't upgrade firmware of ST2000DM001-1CH164 about openseachest

[AlexDaciuk]

Ok, after using the cfs file, it upgraded to CC29

I downloaded latest SeaChest_Firmware from the repo you linked and used the CFS file, this is the output

root:firmware/ # ./SeaChest_Firmware_282_12130_64 -d /dev/sda --fwdlConfig GPCC2949.CFS                                                                                                                                                                                       [17:25:40]
==========================================================================================
 SeaChest_Firmware - Seagate drive utilities - NVMe Enabled
 Copyright (c) 2014-2020 Seagate Technology LLC and/or its Affiliates, All Rights Reserved
 SeaChest_Firmware Version: 2.8.2-1_21_30 X86_64
 Build Date: Apr 13 2020
 Today: Tue Apr 21 17:26:15 2020
==========================================================================================

/dev/sda - ST2000DM001-1CH164 - Z340EMCF - ATA
Downloading file GBP3TBCC29.LOD
Error reading contents of firmware file!
.....................................................
Firmware Download successful!
Firmware Download time (s): 6.39
Average time/segment (ms): 120.56
Activate Time          (s): 6.33
New firmware version is CC29
Successfully validated firmware after download!

and --scan tell me that the firmware is at CC29, so, the upgrade was successful

root:firmware/ # ./SeaChest_Firmware_282_12130_64 --scan                                                                                                                                                                                                                      [17:26:21]
==========================================================================================
 SeaChest_Firmware - Seagate drive utilities - NVMe Enabled
 Copyright (c) 2014-2020 Seagate Technology LLC and/or its Affiliates, All Rights Reserved
 SeaChest_Firmware Version: 2.8.2-1_21_30 X86_64
 Build Date: Apr 13 2020
 Today: Tue Apr 21 17:26:30 2020
==========================================================================================
Vendor   Handle       Model Number            Serial Number          FwRev     
ATA      /dev/sda     ST2000DM001-1CH164      Z340EMCF               CC29  

So, thanks for the cfs suggestion, that worked out, still can't understand why it used the 3TB firmware on my 2TB unit

[vonericsen]

Hi @AlexDaciuk,
Thank you for the logs.
What is the drive attached to (Motherboard, SATA controller, SAS controller, etc)? If it is the motherboard SATA ports, can you tell me if it is in AHCI or RAID mode?

[AlexDaciuk]

Hi,

It is attached to the integrated SATA ports of the motherboard and it is in AHCI mode

lspci | grep SATA returns

SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)

[rudock1]

Hi @AlexDaciuk

Matching firmware to a given product can sometimes be tricky due to various designs and configurations that Seagate ships. While your SHA matches what we found for the "2TB" file, it seems that is not the correct firmware file for your drive. Due to the age of the drive family I could not find an expert to ask.

Our closed source version, SeaChest_Firmware, has an additional feature and can utilize the .cfs configuration file that is included with the SATA firmware ZIP package. Hopefully, it will take care of matching the correct file to the drive. Place cfs and lod files in the same configuration as seen in the package (generally cfs and all lod files in the same directory). We have binary versions here in the GitHub Seagate ToolBin: https://github.com/Seagate/ToolBin/tree/master/SeaChest/Firmware

If you prefer to continue using the open source version you have, then sending the 3TB lod file (MD5:A709F515AE74C7F28FC3A7C536EFFF10) may work.

One last note for customers upgrading their firmware: modern Seagate drives do a lot to protect themselves from flashing incorrect firmware (reference year of 2012 or so). Older products may not have the same level of protection. The SATA firmware update packages from Seagate.com that use cfs files will make sure that only appropriate firmware is downloaded to a given drive to prevent any bad firmware flashes that might occur.

Always backup your data before using firmware in case something awful did go wrong during the upgrade process.

[AlexDaciuk]

Ok, that make sense a little but the thing is that the firmware package I donwloaded is the one suggested by Seagate own searcher (https://apps1.seagate.com/downloads/request.html) when I put the serial number of the HDD, so, it's Seagate own web page returning a non matching firmware?

Weirdly enough, there is a github wiki about upgrading it with hdparm directly that uses the exactly same HDD

The model and serial number I use it's the one provided by hdparm -I /dev/sda

root:Firmware_Seagate/ # hdparm -I /dev/sda                                                                                                                           

/dev/sda:

ATA device, with non-removable media
        Model Number:        ST2000DM001-1CH164                      
        Serial Number:         Z340EMCF
        Firmware Revision:  CC27    
        Transport:                Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
        Used: unknown (minor revision code 0x001f) 
        Supported: 9 8 7 6 5 
        Likely used: 9

The file that I downloaded has the name Barracuda-GrenadaBP-CC29-CC49.zip , I really don't know what GrenadaBP stands for, its sha256 sum is 8873c0a96e8c850ae6bf4970bad1ce146d679450e362a8046baec447dad6a749 , just for reference

The output from SeaChest it's the same that the one from OpenSeaChest when trying to upgrade the firmware, gonna try using the cfs file to see if it changes anything

I should email seagate to see if they can provide the correct firmware?

Cheers
Alex