Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Fan whirr and constant clicking from HD.


  • Please log in to reply
5 replies to this topic

#1 JohnSmithers1

JohnSmithers1

  • Members
  • 104 posts
  • OFFLINE
  •  
  • Local time:08:24 PM

Posted 29 March 2015 - 02:57 PM

Greetings.

 

I have came from the malware forum. In respect of http://www.bleepingcomputer.com/forums/t/569182/suspected-rootkit-malware;-lost-fresh-restore-point;-avg-returned-when-deleted/page-6#entry3666440

 

It was suggested that perhaps there may be a resolution to this challenge. It has been established that I am clear of malware.

 

However I constantly here a faint click of my hardrive, like it is searching for something all the time. Meanwhile my fan is contantly on. This is not normal.

 

Many thanks in advance.



BC AdBot (Login to Remove)

 


#2 Sintharius

Sintharius

    Bleepin' Sniper


  • Members
  • 5,639 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:The Netherlands
  • Local time:08:24 PM

Posted 29 March 2015 - 03:20 PM

Hello there,

Is the noise you hear similar to one of the noises described in here? (find the one that belongs to your HDD's manufacturer)

Regards,
Alex

#3 JohnSmithers1

JohnSmithers1
  • Topic Starter

  • Members
  • 104 posts
  • OFFLINE
  •  
  • Local time:08:24 PM

Posted 29 March 2015 - 05:43 PM

The closest is the last Toshoba one. Mine is a Hitachi.

 

Thanks for the swift reply.



#4 JohnC_21

JohnC_21

  • Members
  • 22,919 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:24 PM

Posted 29 March 2015 - 06:36 PM

Clicking usually indicates a failing drive. You can test the drive using the HGST drive fitness test here. It should work. Hitachi was purchased by WD and then called HGST. If the tool does not work then download Gsmartcontrol for Windows and do the short test. Look at the attributes tab for any red or pink rows. 



#5 JohnSmithers1

JohnSmithers1
  • Topic Starter

  • Members
  • 104 posts
  • OFFLINE
  •  
  • Local time:08:24 PM

Posted 30 March 2015 - 02:43 AM

I could not get HGST to work. Ssmartcontrol passed the HD but I attach the report for you.

 

smartctl 5.43 2012-06-30 r3573 [i686-w64-mingw32-win7(64)-sp1] (sf-5.43-1)
Copyright © 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     Hitachi HTS723225A7A364
Serial Number:    E38G4263D7YBRD
LU WWN Device Id: 5 000cca 6d4d1b462
Firmware Version: ECBOA60W
User Capacity:    250,059,350,016 bytes [250 GB]
Sector Size:      512 bytes logical/physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 6
Local Time is:    Mon Mar 30 08:40:36 2015 GMTDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)    Offline data collection activity
                    was never started.
                    Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)    The previous self-test routine completed
                    without error or no self-test has ever
                    been run.
Total time to complete Offline
data collection:         (   45) seconds.
Offline data collection
capabilities:              (0x5b) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    Offline surface scan supported.
                    Self-test supported.
                    No Conveyance Self-test supported.
                    Selective Self-test supported.
SMART capabilities:            (0x0003)    Saves SMART data before entering
                    power-saving mode.
                    Supports SMART auto save timer.
Error logging capability:        (0x01)    Error logging supported.
                    General Purpose Logging supported.
Short self-test routine
recommended polling time:      (   2) minutes.
Extended self-test routine
recommended polling time:      (  65) minutes.
SCT capabilities:            (0x003d)    SCT Status supported.
                    SCT Error Recovery Control supported.
                    SCT Feature Control supported.
                    SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   062    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   040    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0007   229   229   033    Pre-fail  Always       -       1
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       1098
  5 Reallocated_Sector_Ct   0x0033   097   097   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   040    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0012   094   094   000    Old_age   Always       -       3050
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       1084
191 G-Sense_Error_Rate      0x000a   098   098   000    Old_age   Always       -       4
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       24051781
193 Load_Cycle_Count        0x0012   099   099   000    Old_age   Always       -       10916
194 Temperature_Celsius     0x0002   176   176   000    Old_age   Always       -       34 (Min/Max 2/63)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       45
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       237
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0
223 Load_Retry_Count        0x000a   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 30866 (device log contains only the most recent five errors)
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 30866 occurred at disk power-on lifetime: 3044 hours (126 days + 20 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 14 4b dc 1c 0c  Error: UNC at LBA = 0x0c1cdc4b = 203217995

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 20 48 3f dc 1c 40 00      02:41:22.964  READ FPDMA QUEUED
  60 40 40 3f 31 dc 40 00      02:41:22.964  READ FPDMA QUEUED
  61 01 38 17 a5 00 40 00      02:41:22.964  WRITE FPDMA QUEUED
  60 20 30 bf 63 23 40 00      02:41:22.964  READ FPDMA QUEUED
  60 20 28 9f 64 23 40 00      02:41:22.964  READ FPDMA QUEUED

Error 30865 occurred at disk power-on lifetime: 3044 hours (126 days + 20 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 14 4b dc 1c 0c  Error: UNC at LBA = 0x0c1cdc4b = 203217995

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 40 00 3f 31 dc 40 00      02:41:20.626  READ FPDMA QUEUED
  61 08 f8 df aa 60 40 00      02:41:20.624  WRITE FPDMA QUEUED
  61 10 f0 af aa 60 40 00      02:41:20.624  WRITE FPDMA QUEUED
  61 c8 e8 ef 4c 5c 40 00      02:41:20.616  WRITE FPDMA QUEUED
  61 00 e0 ef 4b 5c 40 00      02:41:20.616  WRITE FPDMA QUEUED

Error 30864 occurred at disk power-on lifetime: 3044 hours (126 days + 20 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 14 4b dc 1c 0c  Error: WP at LBA = 0x0c1cdc4b = 203217995

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 20 38 5f db 06 40 00      02:41:18.191  WRITE FPDMA QUEUED
  61 08 30 bf e1 5f 40 00      02:41:18.176  WRITE FPDMA QUEUED
  61 02 28 0f 6d db 40 00      02:41:18.162  WRITE FPDMA QUEUED
  61 20 20 3f 81 7a 40 00      02:41:18.161  WRITE FPDMA QUEUED
  61 08 18 6f e1 5f 40 00      02:41:18.142  WRITE FPDMA QUEUED

Error 30863 occurred at disk power-on lifetime: 3044 hours (126 days + 20 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 14 4b dc 1c 0c  Error: WP at LBA = 0x0c1cdc4b = 203217995

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 10 b0 f7 e1 0a 40 00      02:41:15.785  WRITE FPDMA QUEUED
  61 08 a0 e7 e1 0a 40 00      02:41:15.785  WRITE FPDMA QUEUED
  61 18 98 af e1 0a 40 00      02:41:15.785  WRITE FPDMA QUEUED
  61 10 90 97 e1 0a 40 00      02:41:15.785  WRITE FPDMA QUEUED
  61 08 80 77 e1 0a 40 00      02:41:15.783  WRITE FPDMA QUEUED

Error 30862 occurred at disk power-on lifetime: 3044 hours (126 days + 20 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 14 4b dc 1c 0c  Error: WP at LBA = 0x0c1cdc4b = 203217995

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 30 9f df 0a 40 00      02:41:13.388  WRITE FPDMA QUEUED
  61 10 28 87 df 0a 40 00      02:41:13.388  WRITE FPDMA QUEUED
  61 10 20 6f df 0a 40 00      02:41:13.387  WRITE FPDMA QUEUED
  61 08 18 57 df 0a 40 00      02:41:13.387  WRITE FPDMA QUEUED
  61 08 10 47 df 0a 40 00      02:41:13.381  WRITE FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      3050         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.



#6 JohnC_21

JohnC_21

  • Members
  • 22,919 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:24 PM

Posted 30 March 2015 - 08:04 AM

I believe the hard drive is failing and if you have any important data on it back it up immediately. Even though it passed you have some problems, especially due to the fact it is clicking. Is the clicking at constant intervals?

 

Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       237

 

Pending Sectors are Sectors that cannot be read but are awaiting reallocation. Increases in this without an increase in the Reallocated Sector Count is bad.

 

Current Pending Sector Count

Count of "unstable" sectors (waiting to be remapped, because of unrecoverable read errors). If an unstable sector is subsequently read successfully, the sector is remapped and this value is decreased. Read errors on a sector will not remap the sector immediately (since the correct value cannot be read and so the value to remap is not known, and also it might become readable later); instead, the drive firmware remembers that the sector needs to be remapped, and will remap it the next time it's written.[36] However some drives will not immediately remap such sectors when written; instead the drive will first attempt to write to the problem sector and if the write operation is successful then the sector will be marked good (in this case, the "Reallocation Event Count" (0xC4) will not be increased). This is a serious shortcoming, for if such a drive contains marginal sectors that consistently fail only after some time has passed following a successful write operation, then the drive will never remap these problem sectors.

 

 

ATA Error Count: 30866 (device log contains only the most recent five errors)

 

During the test you had 30866 errors and those were both Read and Write but the last five indicate mostly Write errors. Write errors being the worse of the two.

UNC means Uncorrectable but I yet to find what WP means, possibly Write Protect? I am not sure. Hopefully somebody else knows the answer.

 

If you do decide to keep the drive, I would not keep anything important on it. Before using it I would zero out the drive and reformat it.

 

Even though SMART says the test passed, SMART is not perfect. The test can pass and the drive still fail but after seeing your report I would err on the side of caution and replace the drive.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users