Difference between revisions of "Talk:Problem with hard drive clicking"
Bob Proulx (Talk | contribs) |
|||
| Line 8: | Line 8: | ||
I have been very successful with using '''sync ; sleep 5; sync; hdparm -w /dev/hda''' to reset the hard drive and stop the ticking. Regardless of the large warning in the hdparm -w man page section I have not seen any data loss. I believe that the small onboard hard drive write cache coupled with having a mostly quiescent system at the time that the command is run probably meanst that I would never see any problem. In a quiescent system the sync;sleep;sync should allow all of the buffers to be written completely througy. But I could believe that if this was done while heavy write activity was occurring that it might create a situation where data in the hard drive write cache might be lost. Eventually the ticking will return and if I am in a quiet envirionment it will be annoying. When that happens I sync and reset the drive and the ticking stops. Before trying this solution rebooting and power cycling the hard drive was the only way to reset and that was very annoying. (Although hibernate, power off, power on, restore from hibernation, means I don't lose anything except about three minutes of my life.) | I have been very successful with using '''sync ; sleep 5; sync; hdparm -w /dev/hda''' to reset the hard drive and stop the ticking. Regardless of the large warning in the hdparm -w man page section I have not seen any data loss. I believe that the small onboard hard drive write cache coupled with having a mostly quiescent system at the time that the command is run probably meanst that I would never see any problem. In a quiescent system the sync;sleep;sync should allow all of the buffers to be written completely througy. But I could believe that if this was done while heavy write activity was occurring that it might create a situation where data in the hard drive write cache might be lost. Eventually the ticking will return and if I am in a quiet envirionment it will be annoying. When that happens I sync and reset the drive and the ticking stops. Before trying this solution rebooting and power cycling the hard drive was the only way to reset and that was very annoying. (Although hibernate, power off, power on, restore from hibernation, means I don't lose anything except about three minutes of my life.) | ||
| + | |||
| + | For me running '''smartctl -t long /dev/sda1''' in the background seems to be a cure for the clicking disease which DRIVES ME CRAZY!!! I have a X41 with a 40GB HD. Seems to work for click free ~41 minutes. All the other methods with hdparm did not help. I don't know whether this is good or not for the HD to run a constant test and it might damage the HD but I don't care. I'm actually surprised the HD is still ok, I can get into a rage because of the clicking and used to bang my fist on it quite a bit. | ||
Revision as of 05:03, 18 October 2008
yes it really works! (This comment is two years old. I can't tell to what it is referring. I suggest that this be comment may be removed now.)
I've had hdd clicking from day one when the hdd idles (t42 2378-jzm 40GB). I would suggest that this particular click is not a sign of impending doom. The drive has had heavy use for 18months with out any problems.
I have this clicking sound with a Fujitsu MHV 2060 BH in my Z61m, 3 months old (in March 2007) Firware version 0084002A.
I also believe that the clicking (or ticking as it really seems to be for me) while a very annoying condition is not an abnormal condition and does not indicate that anything bad is happening. I do not believe it indicates any type of hard drive failure. I have had a laptop disk drive in heavy use for almost two years while suffering through the ticking and have not yet experienced any hard drive failures.
I have been very successful with using sync ; sleep 5; sync; hdparm -w /dev/hda to reset the hard drive and stop the ticking. Regardless of the large warning in the hdparm -w man page section I have not seen any data loss. I believe that the small onboard hard drive write cache coupled with having a mostly quiescent system at the time that the command is run probably meanst that I would never see any problem. In a quiescent system the sync;sleep;sync should allow all of the buffers to be written completely througy. But I could believe that if this was done while heavy write activity was occurring that it might create a situation where data in the hard drive write cache might be lost. Eventually the ticking will return and if I am in a quiet envirionment it will be annoying. When that happens I sync and reset the drive and the ticking stops. Before trying this solution rebooting and power cycling the hard drive was the only way to reset and that was very annoying. (Although hibernate, power off, power on, restore from hibernation, means I don't lose anything except about three minutes of my life.)
For me running smartctl -t long /dev/sda1 in the background seems to be a cure for the clicking disease which DRIVES ME CRAZY!!! I have a X41 with a 40GB HD. Seems to work for click free ~41 minutes. All the other methods with hdparm did not help. I don't know whether this is good or not for the HD to run a constant test and it might damage the HD but I don't care. I'm actually surprised the HD is still ok, I can get into a rage because of the clicking and used to bang my fist on it quite a bit.
