fujitsu 160GB HD ticking noises in Vaio FE11S

[ndros]

Hi everybody,

lately I 've been occasionally hearing some strange ticking noises, most
likely coming from the Fujitsu MHV2160BT 4200 RPM 160GB SATA HD. The
noises occur at sparse intervals, and are short and relatively low,
still very clear and firm. Unfortunately, I have not been able to relate
them to a certain activity, could be that they occur at inactivity,
though the pattern is quite irregular to draw safe conclusions. For
sure, the notebook had not exhibited this noises from the beginning,
I would certainly have noticed.

Naturally I am preoccupied, I only have this notebook for 3 months and
really need it for my work :-( I have already addressed Sony through
their portal and am waiting for their reply. Still, if anyone has had
a similar experience, or has any clue as to what the problem might be
and how to troubleshoot it, I would be grateful!

 

[Rod Speed]

lately I 've been occasionally hearing some strange ticking noises, most
likely coming from the Fujitsu MHV2160BT 4200 RPM 160GB SATA HD.

Very likely the drive is dying and the noise you hear
is it recalibrating when it cant read the data reliably.

The noises occur at sparse intervals, and are short and relatively low,
still very clear and firm. Unfortunately, I have not been able to relate
them to a certain activity, could be that they occur at inactivity, though
the pattern is quite irregular to draw safe conclusions.

For sure, the notebook had not exhibited this noises
from the beginning, I would certainly have noticed.

Naturally I am preoccupied, I only have this notebook for 3 months and
really need it for my work :-( I have already addressed Sony through
their portal and am waiting for their reply. Still, if anyone has had
a similar experience, or has any clue as to what the problem might be
and how to troubleshoot it,

Post the SMART report on the drive here using Everest.
http://www.majorgeeks.com/download.php?det=4181

Its VITAL to backup whatever you'll slash your wrists
if you lose NOW, even if you have to run out and buy
an external drive or USB stick etc.

 

[ndros]

Post the SMART report on the drive here using Everest.
http://www.majorgeeks.com/download.php?det=4181

Its VITAL to backup whatever you'll slash your wrists
if you lose NOW, even if you have to run out and buy
an external drive or USB stick etc.

First of all, thank you very much for your reply Rod. I did exactly as
you advised, and am posting the SMART report on my drive:

--------[ SMART ]-------------------------------------------------------------------------------------------------------

[ FUJITSU MHV2160BT (NU06T6125ND6) ]

01 Raw Read Error Rate 46 100 100 141258 OK: Value is normal
02 Throughput Performance 30 100 100 54263808 OK: Value is normal
03 Spin Up Time 25 100 100 1 OK: Value is normal
04 Start/Stop Count 0 99 99 212 OK: Always passing
05 Reallocated Sector Count 24 100 100 0 OK: Value is normal
07 Seek Error Rate 47 100 100 17 OK: Value is normal
08 Seek Time Performance 19 100 100 0 OK: Value is normal
09 Power-On Time Count 0 99 99 2644975 OK: Always passing
0A Spin Retry Count 20 100 100 0 OK: Value is normal
0C Power Cycle Count 0 100 100 210 OK: Always passing
C0 Power-Off Retract Count 0 100 100 7 OK: Always passing
C1 Load/Unload Cycle Count 0 100 100 15302 OK: Always passing
C2 Temperature 0 100 100 18, 43 OK: Always passing
C3 Hardware ECC Recovered 0 100 100 2423 OK: Always passing
C4 Reallocation Event Count 0 100 100 445644800 OK: Always passing
C5 Current Pending Sector Count 0 100 100 0 OK: Always passing
C6 Off-Line Uncorrectable Sector Count 0 100 100 0 OK: Always passing
C7 Ultra ATA CRC Error Rate 0 200 200 0 OK: Always passing
C8 Write Error Rate 60 100 100 6664 OK: Value is normal
CB <vendor-specific> 0 100 100 28967454 OK: Always passing
F0 Head Flying Hours 0 200 200 0 OK: Always passing

The third column is Threshold, then Value, then Worst and then Data. I
get all OKs, although I don't quite understand the meaning of the four
columns I mentioned.

 

[Rod Speed]

First of all, thank you very much for your reply Rod. I did exactly
as you advised, and am posting the SMART report on my drive:

Urk, the drive is clearly dying, see embedded comments in the report.

--------[
SMART ]-------------------------------------------------------------------------------------------------------

[ FUJITSU MHV2160BT (NU06T6125ND6) ]

01 Raw Read Error Rate 46 100 100 141258 OK: Value is
normal
02 Throughput Performance 30 100 100 54263808 OK: Value is
normal
03 Spin Up Time 25 100 100 1 OK: Value is
normal
04 Start/Stop Count 0 99 99 212 OK: Always
passing
05 Reallocated Sector Count 24 100 100 0 OK: Value is
normal
07 Seek Error Rate 47 100 100 17 OK: Value is
normal
08 Seek Time Performance 19 100 100 0 OK: Value is
normal
09 Power-On Time Count 0 99 99 2644975 OK: Always
passing
0A Spin Retry Count 20 100 100 0 OK: Value is
normal
0C Power Cycle Count 0 100 100 210 OK: Always
passing
C0 Power-Off Retract Count 0 100 100 7 OK: Always
passing
C1 Load/Unload Cycle Count 0 100 100 15302 OK: Always
passing
C2 Temperature 0 100 100 18, 43 OK: Always
passing
C3 Hardware ECC Recovered 0 100 100 2423 OK: Always
passing
C4 Reallocation Event Count 0 100 100 445644800 OK: Always
passing

Thats a very high number and is the worst news.

C5 Current Pending Sector Count 0 100 100 0 OK: Always
passing
C6 Off-Line Uncorrectable Sector Count 0 100 100 0 OK: Always
passing
C7 Ultra ATA CRC Error Rate 0 200 200 0 OK: Always
passing
C8 Write Error Rate 60 100 100 6664 OK: Value is
normal

That isnt good either.

CB <vendor-specific> 0 100 100 28967454 OK: Always
passing

Likely that isnt good either.

F0 Head Flying Hours 0 200 200 0 OK: Always
passing

The third column is Threshold, then Value, then Worst and then Data.
I get all OKs,

Those dont mean much, usually too conservative.

although I don't quite understand the meaning of the four columns I mentioned.

The one that matters is Value. A value of 0 should be obvious.
The Reallocation Event Count is related to the drive checking
for reallocating a potentially bad sector to a spare.

Dont forget the immediate backup, the drive could die at any moment.

 

[Folkert Rienstra]

Urk, the drive is clearly dying,

Clearly huh.

see embedded comments in the report.

--------[ SMART ]-------------------------------------------------------------------------

[ FUJITSU MHV2160BT (NU06T6125ND6) ]

01 Raw Read Error Rate 46 100 100 141258 OK: Value is normal
02 Throughput Performance 30 100 100 54263808 OK: Value is normal
03 Spin Up Time 25 100 100 1 OK: Value is normal
04 Start/Stop Count 0 99 99 212 OK: Always passing
05 Reallocated Sector Count 24 100 100 0 OK: Value is normal
07 Seek Error Rate 47 100 100 17 OK: Value is normal
08 Seek Time Performance 19 100 100 0 OK: Value is normal
09 Power-On Time Count 0 99 99 2644975 OK: Always passing
0A Spin Retry Count 20 100 100 0 OK: Value is normal
0C Power Cycle Count 0 100 100 210 OK: Always passing
C0 Power-Off Retract Count 0 100 100 7 OK: Always passing
C1 Load/Unload Cycle Count 0 100 100 15302 OK: Always passing
C2 Temperature 0 100 100 18, 43 OK: Always passing
C3 Hardware ECC Recovered 0 100 100 2423 OK: Always passing
C4 Reallocation Event Count 0 100 100 445644800 OK: Always passing

Thats a very high number and is the worst news.

Nope.
That value is clearly not to be trusted when the normalized values 'worst' and 'value' are still at 100,
(have not degraded).

That isnt good either.

Likely that isnt good either.

Yet 'worst' and 'value' again still at 100.

Those dont mean much, usually too conservative.

although I don't quite understand the meaning of the four columns I mentioned.

'Threshold', 'Value' and 'Worst' are "Normalized values", 'Data' is the raw (actual) value.
The normalized values are like gages, full is good, empty is bad.

"The device performs conversion of the raw attribute values to transform them in-
to normalized values, which the host can then compare with the threshold values.
A threshold is the excursion limit for a normalized attribute value."

The one that matters is Value.

Not if the normalized values don't concur.

A value of 0 should be obvious.
The Reallocation Event Count is related to the drive checking
for reallocating a potentially bad sector to a spare.

Nope, that is 'pending'.

Dont forget the immediate backup, the drive could die at any moment.

LOL.

 

[Arno Wagner]

First of all, thank you very much for your reply Rod. I did exactly as
you advised, and am posting the SMART report on my drive:

--------[ SMART ]-------------------------------------------------------------------------------------------------------

[ FUJITSU MHV2160BT (NU06T6125ND6) ]

01 Raw Read Error Rate 46 100 100 141258 OK: Value is normal
02 Throughput Performance 30 100 100 54263808 OK: Value is normal
03 Spin Up Time 25 100 100 1 OK: Value is normal
04 Start/Stop Count 0 99 99 212 OK: Always passing
05 Reallocated Sector Count 24 100 100 0 OK: Value is normal
07 Seek Error Rate 47 100 100 17 OK: Value is normal
08 Seek Time Performance 19 100 100 0 OK: Value is normal
09 Power-On Time Count 0 99 99 2644975 OK: Always passing
0A Spin Retry Count 20 100 100 0 OK: Value is normal
0C Power Cycle Count 0 100 100 210 OK: Always passing
C0 Power-Off Retract Count 0 100 100 7 OK: Always passing
C1 Load/Unload Cycle Count 0 100 100 15302 OK: Always passing
C2 Temperature 0 100 100 18, 43 OK: Always passing
C3 Hardware ECC Recovered 0 100 100 2423 OK: Always passing
C4 Reallocation Event Count 0 100 100 445644800 OK: Always passing
C5 Current Pending Sector Count 0 100 100 0 OK: Always passing
C6 Off-Line Uncorrectable Sector Count 0 100 100 0 OK: Always passing
C7 Ultra ATA CRC Error Rate 0 200 200 0 OK: Always passing
C8 Write Error Rate 60 100 100 6664 OK: Value is normal
CB <vendor-specific> 0 100 100 28967454 OK: Always passing
F0 Head Flying Hours 0 200 200 0 OK: Always passing

The third column is Threshold, then Value, then Worst and then Data. I
get all OKs, although I don't quite understand the meaning of the four
columns I mentioned.

Looks perfectly fine. Maybe with the exception of the temperature
column. Not sure how to interpret this, but if is 43C while idle,
then you could have a drive that needs to do frequent thermal
recalibration when under load. However I would expect that to
show up in the seek error rate. It does not, so everything
may just be fine.

Can you have a lokk at the drive temperature with sandra?

Arno

 

[ndros]

Thank you both for your responses and the useful information you are
providing. I was wondering, isn't there another tool like Everest to maybe
crosscheck the figures, that you would advise me to use? I have installed
Linux as a second OS, so it could be Linux sowftware, as well. Also,
I performed disk defragmentation two days ago, and admittedly it took
quite some time (it's a 160GB disk). Could it account for the high
reallocation event count?

Nonetheless, I am backing up everything regularly, thanks for the tip,
anyway!

 

[ndros]

Can you have a lokk at the drive temperature with sandra?

Could you please point me to a link, as I googled around and am not sure
which sandra you mean. Thanks for your reply!

 

[Arno Wagner]

Could you please point me to a link, as I googled around and am not sure
which sandra you mean.

google "sisoft sandra" should find it.

Thanks for your reply!

You are welcome. You are entriely doing the right thing in
trying to find out whether your disk has a problem.

Arno

 

[Arno Wagner]

Thank you both for your responses and the useful information you are
providing. I was wondering, isn't there another tool like Everest to maybe
crosscheck the figures, that you would advise me to use? I have installed
Linux as a second OS, so it could be Linux sowftware, as well.

Aha! Even better. Use "smartctl -a /dev/<disk>" for the full smart status
or "smartctl -d ata -a /dev/<disk>" if it is an SATA disk. Requires
kernel >= 2/6/15 for SATA though. You can forget about sandra if you
post that, at least as far as I am concerned.

Use "hdparm /dev/hda" for just the temperature. Also requires kernel

= 2/6/15 for SATA disks.

Also,
I performed disk defragmentation two days ago, and admittedly it took
quite some time (it's a 160GB disk). Could it account for the high
reallocation event count?

It is unclear whether the value is high. For the raw value the vendor
is allowed to use what they want. For the ''coocked'' value
there are two conventions for ''perfect'': 100 and 255. Worse
is allways lower for coocked.

As for the observed raw value, it looks quite close to 2^32-1 (i.e. the
maximum unsigned long value). Maybe the vendor starts with the highest
possible number in a 32 bit unsigned int and counts down for each
event.

Nonetheless, I am backing up everything regularly, thanks for the tip,
anyway!

Very good.

Arno

 

[Arno Wagner]

Aha! Even better. Use "smartctl -a /dev/<disk>" for the full smart status
or "smartctl -d ata -a /dev/<disk>" if it is an SATA disk. Requires
kernel >= 2/6/15 for SATA though. You can forget about sandra if you
post that, at least as far as I am concerned.

Use "hdparm /dev/hda" for just the temperature. Also requires kernel

It is unclear whether the value is high. For the raw value the vendor
is allowed to use what they want. For the ''coocked'' value
there are two conventions for ''perfect'': 100 and 255. Worse
is allways lower for coocked.

As for the observed raw value, it looks quite close to 2^32-1 (i.e. the
maximum unsigned long value). Maybe the vendor starts with the highest
possible number in a 32 bit unsigned int and counts down for each
event.

Very good.

The kernels should of course be >= 2.6.15. My keyboard calibration
seems to be off this morning.

Arno

 

[ndros]

Based on your valuable tips, I did some reading on S.M.A.R.T. and
installed smartmontools. As far as I understand, my Fujitsu MHV2160BT
drive is not in the smartctl database, therefore the raw values could
be misleading, as you and Folkert suggested. I performed 3 shorts, one
long and one conveyance selftest, and the output, as shown by smartctl
-d ata -l selftest /dev/sda, did not indicate any errors:

---------------------------------------------------------------------------
=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours)
LBA_of_first_error
# 1 Extended offline Completed without error 00% 743 -
# 2 Conveyance offline Completed without error 00% 741 -
# 3 Short offline Completed without error 00% 741 -
# 4 Short offline Completed without error 00% 741 -
# 5 Short offline Completed without error 00% 740 -
---------------------------------------------------------------------------

Finally, I am attaching the output of smartctl -d ata -a /dev/sda, as you
advised me. Indeed the drive does get a bit hotter, escpecially during
the long selftest when it reached 49C, but I am not sure whether this is
bad news or not. Conclusively, the drive passes the S.M.A.R.T. health
test, no errors have been recorded in the Error Log, and all selftests
completed without problems. Is it safe to assume that the drive behaves
normally, despite the strange ticking noises?

Arno, thank you again for your extremely helpful feedback!

---------------------------------------------------------------------------
=== START OF INFORMATION SECTION ===
Device Model: FUJITSU MHV2160BT
Serial Number: NU06T6125ND6
Firmware Version: 00000013
User Capacity: 160,041,885,696 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 4a
Local Time is: Wed May 24 14:44:47 2006 EEST
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: (1200) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
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: ( 140) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.

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 0x000f 100 100 046 Pre-fail Always - 136070
2 Throughput_Performance 0x0005 100 100 030 Pre-fail Offline - 54263808
3 Spin_Up_Time 0x0003 100 100 025 Pre-fail Always - 1
4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 213
5 Reallocated_Sector_Ct 0x0033 100 100 024 Pre-fail Always - 8589934592000
7 Seek_Error_Rate 0x000f 100 100 047 Pre-fail Always - 2750
8 Seek_Time_Performance 0x0005 100 100 019 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 2664003
10 Spin_Retry_Count 0x0013 100 100 020 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 211
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 7
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 15422
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 38 (Lifetime Min/Max 18/47)
195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 3238
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 445644800
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x000f 100 100 060 Pre-fail Always - 4433
203 Run_Out_Cancel 0x0002 100 100 000 Old_age Always - 4827585905156
240 Head_Flying_Hours 0x003e 200 200 000 Old_age Always - 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]


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.
---------------------------------------------------------------------------

 

[Arno Wagner]

Based on your valuable tips, I did some reading on S.M.A.R.T. and
installed smartmontools. As far as I understand, my Fujitsu MHV2160BT
drive is not in the smartctl database, therefore the raw values could
be misleading, as you and Folkert suggested. I performed 3 shorts, one
long and one conveyance selftest, and the output, as shown by smartctl
-d ata -l selftest /dev/sda, did not indicate any errors:

---------------------------------------------------------------------------
=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours)
LBA_of_first_error
# 1 Extended offline Completed without error 00% 743 -
# 2 Conveyance offline Completed without error 00% 741 -
# 3 Short offline Completed without error 00% 741 -
# 4 Short offline Completed without error 00% 741 -
# 5 Short offline Completed without error 00% 740 -
---------------------------------------------------------------------------

Finally, I am attaching the output of smartctl -d ata -a /dev/sda, as you
advised me. Indeed the drive does get a bit hotter, escpecially during
the long selftest when it reached 49C, but I am not sure whether this is
bad news or not. Conclusively, the drive passes the S.M.A.R.T. health
test, no errors have been recorded in the Error Log, and all selftests
completed without problems. Is it safe to assume that the drive behaves
normally, despite the strange ticking noises?

With the self-tests successful, I can only say that this drive looks
perfectly healthy.

49C under load is a bit much, but still not dangerous. If your room
temperature can go up 5C or more compared to what it was during the
test, you should get some additional cooling for the disk, I would
say.

Arno, thank you again for your extremely helpful feedback!

You are welcome.

Arno

---------------------------------------------------------------------------
=== START OF INFORMATION SECTION ===
Device Model: FUJITSU MHV2160BT
Serial Number: NU06T6125ND6
Firmware Version: 00000013
User Capacity: 160,041,885,696 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 4a
Local Time is: Wed May 24 14:44:47 2006 EEST
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: (1200) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
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: ( 140) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.

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 0x000f 100 100 046 Pre-fail Always - 136070
2 Throughput_Performance 0x0005 100 100 030 Pre-fail Offline - 54263808
3 Spin_Up_Time 0x0003 100 100 025 Pre-fail Always - 1
4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 213
5 Reallocated_Sector_Ct 0x0033 100 100 024 Pre-fail Always - 8589934592000
7 Seek_Error_Rate 0x000f 100 100 047 Pre-fail Always - 2750
8 Seek_Time_Performance 0x0005 100 100 019 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 2664003
10 Spin_Retry_Count 0x0013 100 100 020 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 211
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 7
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 15422
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 38 (Lifetime Min/Max 18/47)
195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 3238
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 445644800
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x000f 100 100 060 Pre-fail Always - 4433
203 Run_Out_Cancel 0x0002 100 100 000 Old_age Always - 4827585905156
240 Head_Flying_Hours 0x003e 200 200 000 Old_age Always - 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]

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.
---------------------------------------------------------------------------

 

[BaniPani]

I have exactly the same ticking noises as ndros described. My Son
Vaio FE21S has built in the Fujitsu MHV2160BT 4200 RPM 160GB SATA H
as well. I ran SiSoft Sandra and Everest as mentioned above, but i
says there are no errors. The HD temperature is about 37°C / 98°F

SiSoft Sandra shows "warning 3103: acoustic management activated
Can decrease performance." (translated from German; the warnin
may vary in the English version of Sandra). Probably that causes thi
noise. How can I deactivate this option (if it is an option at all)

@ndros
Do you have any new information about this issue

 

[Rod Speed]

I have exactly the same ticking noises as ndros described. My Sony
Vaio FE21S has built in the Fujitsu MHV2160BT 4200 RPM 160GB SATA HD
as well. I ran SiSoft Sandra and Everest as mentioned above, but it
says there are no errors. The HD temperature is about 37°C / 98°F.

Post the full Everest SMART report here, just a set of OKs isnt enough.

SiSoft Sandra shows "warning 3103: acoustic management activated.
Can decrease performance." (translated from German; the warning may
vary in the English version of Sandra). Probably that causes this noise.

Nope. Its saying that its in quiet mode and that
that may see the drive not be as fast as it can be.

How can I deactivate this option

Hitachi's Drive Feature Tool will be able to do that.

(if it is an option at all)?

Yes it is if Sandra has got its story right.

 

[Folkert Rienstra]

I have exactly the same ticking noises as ndros described. My Sony
Vaio FE21S has built in the Fujitsu MHV2160BT 4200 RPM 160GB SATA HD
as well. I ran SiSoft Sandra and Everest as mentioned above, but it
says there are no errors. The HD temperature is about 37°C / 98°F.

SiSoft Sandra shows "warning 3103: acoustic management activated.
Can decrease performance." (translated from German; the warning may
vary in the English version of Sandra). Probably that causes this noise.

Yup, that makes sense: an option that makes your harddrive slower at the
expense of more noise, who wouldn't want that. Obviously a must have.

 

[BaniPani]

The SMART test results for my Fujitsu MHV2160BT harddisk

ID Attribute Description Thresh. Value Worst
Data Statu
01 Raw Read Error Rate 46 100 100
70199 OK: Value is norma
02 Throughput Performance 30 100 100
53477376 OK: Value is norma
03 Spin Up Time 25 100 100 1
OK: Value is norma
04 Start/Stop Count 0 100 100 41
OK: Always passin
05 Reallocated Sector Count 24 100 100 0
OK: Value is norma
07 Seek Error Rate 47 100 100
2956 OK: Value is norma
08 Seek Time Performance 19 100 100 0
OK: Value is norma
09 Power-On Time Count 0 100 100
849535 OK: Always passin
0A Spin Retry Count 20 100 100 0
OK: Value is norma
0C Power Cycle Count 0 100 100 39
OK: Always passin
C0 Power-Off Retract Count 0 100 100 0
OK: Always passin
C1 Load/Unload Cycle Count 0 100 100
1866 OK: Always passin
C2 Temperature 0 100 100 21
36 OK: Always passin
C3 Hardware ECC Recovered 0 100 100
2355 OK: Always passin
C4 Reallocation Event Count 0 100 100
442368000 OK: Always passin
C5 Current Pending Sector Count 0 100 100 0
OK: Always passin
C6 Off-Line Uncorrectable Sector Count 0 100 100 0
OK: Always passin
C7 Ultra ATA CRC Error Rate 0 200 200 0
OK: Always passin
C8 Write Error Rate 60 100 100
32248 OK: Value is norma
CB <vendor-specific> 0 100 100
10421082 OK: Always passin
F0 Head Flying Hours 0 200 200 0
OK: Always passin

A big thanks in advance for trying to help me. I think it got rapidl
worse from yesterday to today

When the "click" occurs and something is loading from th
harddisk the load procedure stops for milliseconds until th
"click" is over

 

[Rod Speed]

The SMART test results for my Fujitsu MHV2160BT harddisk:

ID Attribute Description Thresh. Value Worst
Data Status
01 Raw Read Error Rate 46 100 100
70199 OK: Value is normal
02 Throughput Performance 30 100 100
53477376 OK: Value is normal
03 Spin Up Time 25 100 100 1
OK: Value is normal
04 Start/Stop Count 0 100 100 41
OK: Always passing
05 Reallocated Sector Count 24 100 100 0
OK: Value is normal
07 Seek Error Rate 47 100 100
2956 OK: Value is normal

I dont like this one.

08 Seek Time Performance 19 100 100 0
OK: Value is normal
09 Power-On Time Count 0 100 100
849535 OK: Always passing
0A Spin Retry Count 20 100 100 0
OK: Value is normal
0C Power Cycle Count 0 100 100 39
OK: Always passing
C0 Power-Off Retract Count 0 100 100 0
OK: Always passing
C1 Load/Unload Cycle Count 0 100 100
1866 OK: Always passing
C2 Temperature 0 100 100 21,
36 OK: Always passing
C3 Hardware ECC Recovered 0 100 100
2355 OK: Always passing
C4 Reallocation Event Count 0 100 100
442368000 OK: Always passing

Or this one either.

C5 Current Pending Sector Count 0 100 100 0
OK: Always passing
C6 Off-Line Uncorrectable Sector Count 0 100 100 0
OK: Always passing
C7 Ultra ATA CRC Error Rate 0 200 200 0
OK: Always passing
C8 Write Error Rate 60 100 100
32248 OK: Value is normal

Or this one either.

CB <vendor-specific> 0 100 100
10421082 OK: Always passing
F0 Head Flying Hours 0 200 200 0
OK: Always passing

While some have claimed that just because you see those 100 values
on those questionable lines, that doesnt explain why the drive is clicking.
I expect its because the drive is being much too conservative about
those 100 values and the drive does have a problem.

A big thanks in advance for trying to help me.
I think it got rapidly worse from yesterday to today.

When the "click" occurs and something is loading from the
harddisk the load procedure stops for milliseconds until the
"click" is over.

Yeah, thats the drive recalibrating and eventually getting
the data off the platters. Thats the reason for the delay.

I'd personally replace the drive and I'd bet that those
dubious values are then fine with the replacement drive.

 

[BaniPani]

While some have claimed that just because you see those 100 value

on those questionable lines, that doesnt explain why the drive i clicking
I expect its because the drive is being much too conservative abou
those 100 values and the drive does have a problem

What do the values mean at all

Yeah, thats the drive recalibrating and eventually gettin
the data off the platters. Thats the reason for the delay

I'd personally replace the drive and I'd bet that thos
dubious values are then fine with the replacement drive

Is my harddisk destroying itself so continuous usage will lead to it
death

What I noticed in the past hours while some harddisk tests
If the harddisk is under full load it does not click and it does no
interrupt the load procedure to click/calibrate. But if it is idle i
begins to click again

 

[Rod Speed]

What do the values mean at all?

The 100 values are supposed to mean how well the
drive is doing compared with a drive that isnt dying.

The Value entry is supposed to be mostly the count
of that particular type of activity with the exception
of some of the specials like the temperature etc.

Is my harddisk destroying itself so continuous usage will lead to its death?

Yes, very likely.

What I noticed in the past hours while some harddisk tests:
If the harddisk is under full load it does not click and it does not
interrupt the load procedure to click/calibrate. But if it is idle it
begins to click again.

Thats certainly unusual. Its usually the other way around.

See what a full selftest with smartctl shows.

Thats a bit trickier to use, I do it from a knoppix bootable CD
but you do need to be able to use linux from the command
line and to be able to save the report to include it in a
newsgroup post. Not trivial if you havent used linux before.

There is a version for Win, but it isnt as capable.
http://smartmontools.sourceforge.net/