Hitachi Harddisks Thread (5K3000, 7K3000, 7K2000)

[BattlestormTitan]

Hi Guys, are there any updated firmware’s for the 7k4000 drives? At least I think they are classed as 7k4000’s
I’ve got a batch of Hitachi HDS724040ALE640 (4tb) listed as running MJAOA3B0, so I’m assuming firmware 3B0 back from 2012 which have been running fine, I’ve had a few failures which have been replaced the same model drive running MJAOA580 and they are dropping from a big raid10 like fly’s.
Does the 800 or A10 firmware that’s been talked about exist for this drive?
The Raid controllers are dell Perc H710P’s and H810P’s the drives them selfs don’t report any issue with HGST’s tools, but HHDScan reports 300+ 500ms hits when scanning the drive, which is what I’m guessing is causing the drop. Some if the older posts talk about the 800 fixing this issue on the 7k3000’s thus my hope for a firmware for the 7k4000 4tb

 

[Rich.T.]

FYI:

I've just updated the firmware for my Hitachi HDS724040ALE640, FwRev=MJAOA250 to MJAOA580.

I needed to do this in order for the drive to support standby mode.

To accomplish this I found that I had to install Windows Vista x86 on an old PC, plug the Hitachi HDS724040ALE640 into the first SATA connector on the motherboard, with the OS booting from the second for the drive to me recognised. I then ran the supplied HiTest software and ran the firmware update, using the supplied file "MJ0NB580.BD".

Success! It now shows up as: Model=HGST HDS724040ALE640, FwRev=MJAOA580 and will spin down correctly, as needed.

 

[kryptex]

Rich.T., would you share the firmware with us ? Talk is cheap

 

[Rich.T.]

Sorry for the delay.
You're right: Talk is cheap.
By the way: The drive in question does not seem to enter standby after the set period.
It's behaviour doesn't seem to have changed, despite the upgrade. Could this be caused by something more fundamental than the drive's firmware? Does anybody know; or has anyone had a similar experience with these Hitachi/HGST drives?

Thanks,
Rich.

 

[HellDiverUK]

I have a pair of Jan 2014 HDN724040ALE640 which run MJAOA5E0 - I bought these as Deskstar NAS drives, but I'm assuming they're just a 7K4000 with different firmware. These drives don't seem to do any idle states as far as I can tell. They have just under 2400 hours on them, and have about 720 load cycle count, which seems to be the same as the power cycle count according to SMART.

 

[kryptex]

Sorry for the delay.
You're right: Talk is cheap.
By the way: The drive in question does not seem to enter standby after the set period.
It's behaviour doesn't seem to have changed, despite the upgrade. Could this be caused by something more fundamental than the drive's firmware? Does anybody know; or has anyone had a similar experience with these Hitachi/HGST drives?

Thanks,
Rich.

Thanks a lot ! I've just noticed that the embedded, new HiTest 2.47S finally supports Windows 7 32bit/64bit. This was not the case with any previous firmwares for Hitachi, since all of them required Windows XP 32bit specifically in order to run.

Regarding the standby mode of Hitachi HDDs, I've found Hitachi Feature Tool (FTool) to be able to modify the APM (Advanced Power Management) of the drive. Here is the 2.16 M2 ISO, it supports SATA 6.0 Gb/s. You have to burn it to a CD/DVD and boot from it:
MEGA

By lowering the APM value, you put the HDD in a deeper power saving mode. APM is usually turned off (or set to 254-255) on Hitachi HDDs from the factory (meaning that the drive is always spinning and doesn't park the heads -- no power savings).
With FTool I was able to set APM=128, a moderate power saving, on Hitachi 7K2000 and 7K3000, which parks the heads after a few minutes of inactivity. APM=128 doesn't spin down the HDD.

However, I haven't tried lower APM values, below 128, which, should put the drive in standby (spin down) after a few minutes. I say give it a try and experiment a little.
*Note: there are also other versions of this FTool out there (2.17 and modded variants of it), in case 2.16 M2 isn't compatible with the newer 7K4000 series. Drop me a line in case you need a modded version, I'll see what I can do.

Hope this helps !

 

[Rich.T.]

Thanks a lot ! I've just noticed that the embedded, new HiTest 2.47S finally supports Windows 7 32bit/64bit. This was not the case with any previous firmwares for Hitachi, since all of them required Windows XP 32bit specifically in order to run.

No problem, it's a pleasure. Thank you for the FTool link.
Oh yeah, sorry; I noticed that HiTest worked on my Win7-64 machine, but it seemed a bit glitchy and unstable to me, plus it didn't properly identify any of my storage controllers or any attached disks, so I used another machine, as I mentioned earlier.

Regarding the standby mode of Hitachi HDDs, I've found Hitachi Feature Tool (FTool) to be able to modify the APM (Advanced Power Management) of the drive. Here is the 2.16 M2 ISO, it supports SATA 6.0 Gb/s. You have to burn it to a CD/DVD and boot from it:
MEGA

https://mega.co.nz/#!Z91VTBrb!Nn9KkLNjIB40ZWsPvbJ9jr880FQ8CdIv4zDvQamYFBE

Thanks. I created a MSDOS USB boot disk with Rufus, chucked ftool.exe and ftool.hf on there, booted from it and ran ftool, but unfortunately the only feature that worked was the ability to enable/disable SMART, everything else came up as unsupported.

By lowering the APM value, you put the HDD in a deeper power saving mode. APM is usually turned off (or set to 254-255) on Hitachi HDDs from the factory (meaning that the drive is always spinning and doesn't park the heads -- no power savings).
With FTool I was able to set APM=128, a moderate power saving, on Hitachi 7K2000 and 7K3000, which parks the heads after a few minutes of inactivity. APM=128 doesn't spin down the HDD.

However, I haven't tried lower APM values, below 128, which, should put the drive in standby (spin down) after a few minutes. I say give it a try and experiment a little.

Yeah, I've got the other six HGST 7K4000s set to APM=127 on my fileserver VM via a /etc/hdparm.conf file. eg:

/dev/disk/by-id/ata-HGST_HDS724040ALE640_PK13********** {
apm = 127
keep_features_over_reset = on
spindown_time = 242
}
...etc.

*Note: there are also other versions of this FTool out there (2.17 and modded variants of it), in case 2.16 M2 isn't compatible with the newer 7K4000 series. Drop me a line in case you need a modded version, I'll see what I can do.

Hope this helps ![/SIZE]

It looks like I may be in need of further assistance after all. I don't hold out all that much hope though, as I don't see why the Linux hdparm command shouldn't be as effective as HGST's DOS tool, but I'll try everything I can to tame this stubborn drive. If you could link me to 2.17 I'd very much appreciate it and also; what do the modifications you mentioned entail?

Thanks again for your kind help.
Rich.

 

[tueddelkopp]

Hello,
i am searching for the newest Firmware for my 5k3000 (P/N: 0F12460) drive because i have problems with it. The above Links for this are dead. Can someone please reupload the firmware anywhere? Thanks

 

[kryptex]

Firmware A10 for Hitachi 5K3000 3TB (0F12460), with HiTest 2.47S flasher for WinXP 32bit or Win7 32bit/64bit:
MEGA
Please report back, how did it go ?

 

[tueddelkopp]

Thank you very much. I got that drive updated on an old WindowsXP machine. My problem with that drive was that there are a few offline uncorrectable and pending sectors that doesnt got reallocated on writing the disk with zeros. I will now test that with the new firmware and will report back.

 

[kryptex]

What was your previous firmware ? The one I've posted is A10. Sometimes when you have pending sectors a solution is to random-fill the drive, not zero-fill it. What I normally do is this: read (scan) the whole drive, then random-fill it, then again read (scan). Truth is, for a 3TB HDD it takes like 24h...
If you still can't repair those pending sectors, then I suggest to use HDDScan or HD Tune and find out which LBAs are the ones that can't be read. Then, do several read-write cycles with HDDScan on a 5 GB interval encompassing that/those bad LBAs.

 

[Iam2310]

Links for "Hitachi Deskstar 5K3000 HDS5C3020ALA632" firmware 800 and A10 broken. Can anyone upload again? Thank you.

 

[kryptex]

Links for "Hitachi Deskstar 5K3000 HDS5C3020ALA632" firmware 800 and A10 broken. Can anyone upload again? Thank you.

Here you go:
MEGA

 

[Dk3]

I think STH should have a repository to store all these drivers and firmware especially after HP changes into new policy. And this only serves to members only.

 

[kroem]

So, I'm soory about this, but the thread is so long and hard to follow if you do NOT have these drives - but is the 7K3000 a good drive? Would be running in a zfs nas.

 

[TubaMT]

Firmware A10 for Hitachi 5K3000 3TB (0F12460), with HiTest 2.47S flasher for WinXP 32bit or Win7 32bit/64bit:
MEGA
Please report back, how did it go ?

Hi @kryptex ! Thank you so much for the firmware for these drives! I also have a few Hitachi 5K3000 HDS5C3030ALA630 (P/N: 0F12460) from the ebay deal posted in the great deals section of the forum. It has firmware 580 on it.

Is the A10 firmware the latest? I've been trying to search through this thread and it seems like it is. I just wanted to make sure I didn't brick my drives.

Do you know what the benefits of this firmware are over the 580 firmware? Thank you!

 

[Dmitry Balashov]

Hello
Please give firmware Hitachi HDS723020bla642 (0F12115). all links is broken. thanks.

 

[britinpdx]

I'm also looking for firmware for the 2TB 7k3000 (0F12115).

looks like I have a mixture of A180, A5C0 and A800, so I presume A800 is the latest ?

 

[kryptex]

Firmware A10 for Hitachi 7K3000 2TB HDS723020BLA642 (0F12115):
DOS version: MEGA
Windows version (HiTest 2.47S flasher for WinXP 32bit or Win7 32bit/64bit): MEGA
Please report back, how did it go ?

 

[britinpdx]

Please report back, how did it go ?

Thanks for the super quick response !

I used the DOS FW flash method and had no issues in upgrading from 180, 5C0 and 800 to A10.

Now, I do have several additional drives (all at FW rev 800) in a current RAID6 array on an LSI controller, and have no issues that I'm aware of.
If I understand correctly, the FW upgrade is supposed to leave all data intact ... so if I power down the array and pull the drives one at a time to upgrade FW in another machine then I should have no issues with Array corruption ?

Or should I just let sleeping dogs lie ....