All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Andrew Paprocki <andrew@ishiboo.com>
Cc: Jim Paris <jim@jtan.com>, linux-ide@vger.kernel.org
Subject: Re: 2.6.24 sata_sil Sil3114 drive clicking / restarting?
Date: Sat, 02 Feb 2008 14:17:13 +0900	[thread overview]
Message-ID: <47A3FCD9.80908@gmail.com> (raw)
In-Reply-To: <76366b180801271121kf3119d7w89bca2f0315a4ca9@mail.gmail.com>

Andrew Paprocki wrote:
> Both drives already had PM disabled, visible in hdparm -i:
> "AdvancedPM=yes: disabled (255) WriteCache=enabled"
> 
> Looking at the smart reporting, it is showing both drives have a
> FAILING_NOW condition for Seek_Error_Rate. I don't know what to
> believe, because it seems like whatever drives I attach to this system
> are chewed up and start showing Seek_Error_Rate failure conditions.
> 
> /dev/sda:
>  7 Seek_Error_Rate         0x000b   046   046   067    Pre-fail
> Always   FAILING_NOW 393853
> /dev/sdb:
>  7 Seek_Error_Rate         0x000b   044   044   067    Pre-fail
> Always   FAILING_NOW 2556544
> 
> I swapped in 2 more drives of the same model, and one exhibits the
> same Seek_Error_Rate FAILING_NOW condition. I now have 4 out of 5 of
> this same model drive which are failing. They appear to be from the
> same batch, so I'm not ruling out some kind of manufacturing defect,
> but this definitely seems strange. I guess I'm just fishing to see if
> there is anything on the system that could have damaged the drives.

Can you connect the drive to a separate different SPU and see whether
the problem persists?

-- 
tejun

      reply	other threads:[~2008-02-02  5:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-27 18:19 2.6.24 sata_sil Sil3114 drive clicking / restarting? Andrew Paprocki
2008-01-27 18:33 ` Jim Paris
2008-01-27 19:21   ` Andrew Paprocki
2008-02-02  5:17     ` Tejun Heo [this message]

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=47A3FCD9.80908@gmail.com \
    --to=htejun@gmail.com \
    --cc=andrew@ishiboo.com \
    --cc=jim@jtan.com \
    --cc=linux-ide@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.