Hitachi HDT725032VLA360 clicking

[Mikhail-81]

Recently my hdd Hitachi was sounding as "click-click-click..." with short rarely peeps (I may send you a mp3- recording of this sound) and didn't determined by the OS at the same time, while I was leaving the PC turned on for a day, for example, to upload media content, or defragmentation.
shutdowning the PC and booting PC again solves the problem, but the problem was reappeared from booting to booting. I've check the hdd by program HD Tune Pro 5.00 - it shows "All is OK". Hitachi HDT725032VLA360 (320 GB). It was bought in 2007. But worked since 2010. operating time of 3300 hours use.

See the SMART:

HD Tune Pro: Hitachi HDT725032VLA360 Health

ID Current Worst ThresholdData Status
(01) Raw Read Error Rate 100 100 16 0 ok
(02) Throughput Performance 100 100 50 0 ok
(03) Spin Up Time 111 111 24 21758291 ok
(04) Start/Stop Count 100 100 0 1093 ok
(05) Reallocated Sector Count 100 100 5 0 ok
(07) Seek Error Rate 100 100 67 0 ok
(08) Seek Time Performance 100 100 20 0 ok
(09) Power On Hours Count 100 100 0 3397 ok
(0A) Spin Retry Count 100 100 60 0 ok
(0C) Power Cycle Count 100 100 0 668 ok
(C0) Unsafe Shutdown Count 100 100 0 1185 ok
(C1) Load Cycle Count 100 100 0 1185 ok
(C2) Temperature 171 171 0 524323 ok
(C4) Reallocated Event Count 100 100 0 0 ok
(C5) Current Pending Sector 100 100 0 0 ok
(C6) Offline Uncorrectable 100 100 0 0 ok
(C7) Ultra DMA CRC Error Count 200 253 0 0 ok

Then I set the Enabled (was Disabled as default) parameter "HDD S.M.A.R.T. Campability" in CMOS for both hdd-drives, connected to PC.
After that the hard drive Hitachi began to work normally and more quite for 6 months, but after that the problem has returned. I've removed bottom electric plate and cleaned it with an eraser. Have changed the SATA cables and connection ports - No results. I've plugged a new Seagate for backup to the same port - it operate normally. Should I check my troubleshutting Hitachy by MHDD? On what parameters I should pay attention in this case?
My motherboard - Gigabyte GA-P35C-DS3R rev 1.1. BIOS ver F2, I have n't updated its since 2007. Should I Update the BIOS of mb or Hdd's?

[Mikhail-81]

Could it be the cause of swollen capacitors power supply PC? But why the new Seagate works normally...

[dmarques]

With the tests you've made, it clear that the problem is related to the hard drive itself.
What's your goal now? Revive the drive or get your data?

[Mikhail-81]

Now the drive is operating normally. But I'm not sure from reappearance of this trouble.
So my goal - to find the cause of trouble and fix it.

[dmarques]

I think sooner or later the drive will die, so make a backup of it and replace it.

[Vulcan]

@Mikhail-81,

The story so far does not have enough exact detail IMHO - you seem to be saying that both the Seagate and Hitachi disks are currently working OK, but in the past, the Hitachi drive was sometimes clicking. It seems that you are not sure whether anything you did definitely stopped the Hitachi clicking, or whether it stopped for another reason which you're not able to find.

If that is a good summary of the situation, then an intermittent power-related problem (which did not happen when the Seagate drive was attached, perhaps because the problem was intermittent - i.e. this was just good luck?) still seems a possibility. Perhaps you have more details which you have not yet given, to help to confirm or disprove that possibility?

If you do not have a problem now, then it can be very difficult to find the cause of a previous problem which has not stopped happening. Don't expect us to find the cause for you, in that situation. To answer your earlier questions - no, don't change the BIOS or disk firmware, since neither will cause the intermittent symptoms that you describe, IMHO.

As dmarques said, perhaps the Hitachi drive is failing - so make regular backups and then you don't have to worry so much

[Mikhail-81]

If that is a good summary of the situation, then an intermittent power-related problem (which did not happen when the Seagate drive was attached, perhaps because the problem was intermittent - i.e. this was just good luck?) still seems a possibility. Perhaps you have more details which you have not yet given, to help to confirm or disprove that possibility?

No - When I've first heard the clicking, I bought a Seagate, and make a backup, since I have it as a reserve drive.

[Mikhail-81]

I think sooner or later the drive will die, so make a backup of it and replace it.

But why the SMART is OK?

[Vulcan]

If that is a good summary of the situation, then an intermittent power-related problem (which did not happen when the Seagate drive was attached, perhaps because the problem was intermittent - i.e. this was just good luck?) still seems a possibility. Perhaps you have more details which you have not yet given, to help to confirm or disprove that possibility?

No - When I've first heard the clicking, I bought a Seagate, and make a backup, since I have it as a reserve drive.

Unfortunately that is still not detailed enough for me to understand exactly what happened and when - i.e. the full sequence of events (problems observed, tests performed, results of those tests, changes to the configuration etc). Without that clear understanding, then diagnosis will be too slow, inefficient and prone to errors. Personally I still do not see where an intermittent power-related problem has been eliminated as a possibility...

But why the SMART is OK?

SMART does not, and never can, predict/show all problems. For example, if a drive cannot even start up successfully, then it also cannot update the SMART attributes (they are stored on the platters). Therefore you can never look at SMART data and say "the drive is definitely OK" - that is logical fallacy. All you can say is that the SMART data shows no obvious signs of a problem - which does not mean that the drive is definitely OK! This is a common misunderstanding. I hope that explanation helps you to better understand the limitations of the SMART attribute data.

[Mikhail-81]

Vulcan, What data do you need? I afraid of test's that it may be caused damage of the drive

[Vulcan]

I afraid of test's that it may be caused damage of the drive

Unfortunately I don't understand what you mean.

If you mean that you are afraid of damage that past tests may have caused to the drive - it is too late to worry about the past.

If you mean that you are afraid of damage that future tests may cause to the drive - I did not ask for any new tests to be run.

What data do you need?

I don't think I can be clearer than what I said in my previous posting, so it seems that we have a communication problem, as we are not understanding each other. Therefore I will stop here - perhaps someone else will understand you better than I am.

[Mikhail-81]

[/quote]
Unfortunately that is still not detailed enough for me to understand exactly what happened and when - i.e. the full sequence of events (problems observed, tests performed, results of those tests, changes to the configuration etc). Without that clear understanding, then diagnosis will be too slow, inefficient and prone to errors. [/quote]

So I understood you need more information about my problem - can you write which one?

[labtech]

Unfortunately that is still not detailed enough for me to understand exactly what happened and when - i.e. the full sequence of events (problems observed, tests performed, results of those tests, changes to the configuration etc). Without that clear understanding, then diagnosis will be too slow, inefficient and prone to errors. [/quote]

So I understood you need more information about my problem - can you write which one?[/quote]

We do not know which one per se. We are just looking for clues from info that you may have accidentally omitted to mention/thought of/remember, etc.

For me, if you want to figure out if there is truly a problem with the drive, then some benchmark testing should be completed on at least one other machine (I would aim for two machines), as in a known fault free system, so that should there be any issues noticed, then they would have to be related to the HDD.

[Mikhail-81]

I've done tests by HD Tune Pro in my same computer. See results

Attachments

[labtech]

Though I do not understand Russian, based on the graphs and numbers, I do not see anything concerning with the drive.

I do suggest, as mentioned before, that you run the same test on a different machine as well, and potentially with another benchmark testing tool just to confirm consistency.

If you will follow the suggestion and everything indicates consistency with the drive's operation, then I would conclude that the random problem is with something else. Not sure what, because if anything such as the power supply unit would have become problematic, then the problem would have been apparent consistently and likely gotten worse. Pretty much the same with the capacitors I would expect.

Hope this helped.

Best wishes