From: Robert Hancock <hancockrwd@gmail.com>
To: Gavin Cameron <gavin@gavsworld.net>
Cc: Tejun Heo <tj@kernel.org>, linux-ide@vger.kernel.org
Subject: Re: Frequent Head Unload Problem
Date: Fri, 17 Apr 2009 19:24:47 -0600 [thread overview]
Message-ID: <49E92BDF.7060507@gmail.com> (raw)
In-Reply-To: <49E8C14D.7020907@gavsworld.net>
Gavin Cameron wrote:
>> Can you try doing smartctl -a on both drives before and after you hear
>> the noise and see if it seems to match up with any of the counters
>> changing?
>
> Here's the build up:
> sudo smartctl -a /dev/sda > sda_start
> sudo smartctl -a /dev/sdb > sdb_start
> ... a few mins while noises go on ...
> sudo smartctl -a /dev/sda > sda_end
> sudo smartctl -a /dev/sdb > sdb_end
>
> Here are the results:
> diff sda_start sda_end
> 13c13
> < Local Time is: Fri Apr 17 16:03:40 2009 BST
> ---
> > Local Time is: Fri Apr 17 16:17:20 2009 BST
> 66c66
> < 194 Temperature_Celsius 0x0002 253 253 000 Old_age
> Always - 17 (Lifetime Min/Max 9/38)
> ---
> > 194 Temperature_Celsius 0x0002 240 240 000 Old_age
> Always - 25 (Lifetime Min/Max 9/38)
> 88a89
> >
>
> So nothing there apart from the temperature. However:
> diff sdb_start sdb_end
> 13c13
> < Local Time is: Fri Apr 17 16:03:42 2009 BST
> ---
> > Local Time is: Fri Apr 17 16:17:26 2009 BST
> 57,59c57,59
> < 7 Seek_Error_Rate 0x000a 199 199 000 Old_age
> Always - 80
> < 8 Seek_Time_Performance 0x0027 246 238 187 Pre-fail
> Always - 39281
> < 9 Power_On_Minutes 0x0032 229 229 000 Old_age
> Always - 710h+53m
> ---
> > 7 Seek_Error_Rate 0x000a 199 198 000 Old_age
> Always - 43
> > 8 Seek_Time_Performance 0x0027 246 238 187 Pre-fail
> Always - 45449
> > 9 Power_On_Minutes 0x0032 229 229 000 Old_age
> Always - 711h+07m
> 65,66c65,66
> < 194 Temperature_Celsius 0x0032 037 253 000 Old_age
> Always - 17
> < 195 Hardware_ECC_Recovered 0x000a 253 251 000 Old_age
> Always - 36907
> ---
> > 194 Temperature_Celsius 0x0032 037 253 000 Old_age
> Always - 24
> > 195 Hardware_ECC_Recovered 0x000a 253 251 000 Old_age
> Always - 31779
> 70c70
> < 199 UDMA_CRC_Error_Count 0x0008 084 001 000 Old_age
> Offline - 768
> ---
> > 199 UDMA_CRC_Error_Count 0x0008 100 001 000 Old_age
> Offline - 768
> 72c72
> < 201 Soft_Read_Error_Rate 0x000a 253 252 000 Old_age
> Always - 0
> ---
> > 201 Soft_Read_Error_Rate 0x000a 253 252 000 Old_age
> Always - 2
> 100a101
> >
>
> Looks to me like this drive could well be on its way out! None of the
> counters (Start_Stop_Count for example) were changing, but lots of CRC
> and error counts are.
>
> What do you think? Just a knackered drive and nothing to do with libata
> at all?
Yeah, it's possible that what you're hearing isn't a head unload at all,
but some kind of abnormal recalibration noise, etc.
next prev parent reply other threads:[~2009-04-18 1:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 16:52 Frequent Head Unload Problem Gavin Cameron
2009-04-15 1:27 ` Robert Hancock
2009-04-15 22:58 ` Gavin Cameron
2009-04-16 0:01 ` Robert Hancock
2009-04-17 17:50 ` Gavin Cameron
2009-04-18 1:24 ` Robert Hancock [this message]
2009-04-23 22:00 ` Gavin Cameron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49E92BDF.7060507@gmail.com \
--to=hancockrwd@gmail.com \
--cc=gavin@gavsworld.net \
--cc=linux-ide@vger.kernel.org \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).