
Solving the problem with the Seagate Barracuda 7200.11, ES.2 and DiamondMax 22
Seagate today posted a firmware that fixes recent problems with its 7200.11, ES.2, and DiamondMax 22 series of hard drives.
Update: at the moment, no one was able to flash, the flasher says that the hard drive is of the wrong model: “Error: Specific model not found”. We are waiting for updates on the Seigate website.
Update2:
Update3: Some hard drives were flashed successfully, but many people have a situation like this one:
Update4: “500GB disks (ST3500320AS, STM3500320AS) cannot be flashed on SD1A yet - disks are being killed. 640-1000GB drives should work normally, but it’s better to wait for the fix. Files firmware have been removed from the official server to determine the reasons "(p) doomer (the Data of Recovery Expert, author HDDScan)
Update5: Hyde by known firmware.
Update6: The problem with the firmware has been resolved, all of the above laid out firmwares are checked and operational.
- ST3500320AS, ST3500620AS, ST3500820AS, ST3640330AS, ST3640530AS, ST3750330AS, ST3750630AS, ST31000340AS with firmware AD14, SD15, SD16, SD17, SD18, SD19. The new firmware version SD1A can be downloaded from here or by direct links:
ST3500320AS, ST3500620AS, ST3500820AS - Download ;
ST3750330AS, ST3750630AS, ST31000340AS - Download ;
ST3640330AS, ST3640530AS - later. - STM3500320AS, STM3750330AS, STM31000340AS, STM31000333AS with firmware MX15 and later. Download the new firmware version MX1A here or by direct links:
STM3500320AS: MooseDT-MX1A-2D-DMax22.ISO
STM3750330AS: MooseDT-MX1A-3D4D-DMax22.ISO
STM31000340AS: MooseDT-MX1A-3D4D-DMax22.ISO - ST31500341AS, ST31000333AS, ST3640323AS, ST3640623AS, ST3320613AS, ST3320813AS, ST3160813AS also vulnerable should upgrade to SD1B or SD1C :
ST31500341AS: Brinks-4D8H-SD1B.ISO
ST31000333AS: Brinks-3D6H-SD1B.ISO
ST3640323AS, ST3640623AS: Brinks-2D4H-SD1B .ISO
ST3320613AS, ST3320813AS: Brinks-1D2H-SD2B
.ISO ST3160813AS: Brinks-1D1H-SD2B.ISO - STM31000334AS, STM3320614AS, STM3160813AS - firmware MX1B :
STM31000334AS: Brinks-3D6H-MX1B.ISO
STM3640323AS: Brinks-2D4H-MX1B.ISO
STM3320614AS: Brinks-1D2H-MX1B.ISO
STM3160813AS: Brinks-1D1H-MX1B.ISO - ST3250310NS, ST3500320NS, ST3750330NS, ST31000340NS - recommended firmware version SN06 or SN16 depending on the party.
Update: at the moment, no one was able to flash, the flasher says that the hard drive is of the wrong model: “Error: Specific model not found”. We are waiting for updates on the Seigate website.
Update2:
Suspicions began to appear back in December last year, when Seagate 7200.11 series drives with the same symptoms began to arrive more and more often at service centers - when the computer is turned on, the hard drive is not detected at all or detected, but with a capacity of 0 GB. At the same time, both electronics and disk mechanics are perfectly operational. As it turned out, the problem lies in the so-called translator table, which is responsible for converting the real physical addressing of the disk to logical - due to an error in the firmware of the disks, this table may be destroyed, which will lead to the symptoms described above. At the same time, all user data on the disk remains intact, but is no longer available for the computer.
Update3: Some hard drives were flashed successfully, but many people have a situation like this one:
I have requested. ST3500320AS, SD15, 3 pieces in a row. The flasher did not swear, poured a new firmware SD1A into each drive, reported successful execution, asked to turn off and on the computer. Now, although these disks start, they are defined as IDE Hard Disk seconds after 30 freezes on each port, the BIOS seems to even show the ST3500320AS type, but the raid controller does not see them at all. The pieces of iron are shorter.
Update4: “500GB disks (ST3500320AS, STM3500320AS) cannot be flashed on SD1A yet - disks are being killed. 640-1000GB drives should work normally, but it’s better to wait for the fix. Files firmware have been removed from the official server to determine the reasons "(p) doomer (the Data of Recovery Expert, author HDDScan)
Update5: Hyde by known firmware.
Update6: The problem with the firmware has been resolved, all of the above laid out firmwares are checked and operational.