linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Small <tim@buttersideup.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: "smartmontools-support@lists.sourceforge.net"
	<smartmontools-support@lists.sourceforge.net>,
	linux-ide@vger.kernel.org
Subject: Re: [smartmontools-support] SATA drive reset/disable events on ICH7 ata_piix when polling SMART info
Date: Fri, 05 Feb 2010 14:31:36 +0000	[thread overview]
Message-ID: <4B6C2BC8.7000609@buttersideup.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1002050911500.7774@p34.internal.lan>

Justin Piszcz wrote:
> I have seen people report similar problems with the following drives:
>
> 1 - Velociraptors (me/others) (don't work at all in raid correctly)
> http://forums.storagereview.com/index.php/topic/27303-velociraptor-premature-failure-rate-bad-drives-premature-to-market/ 
>
> 2 - Green Drives (search this list, there are similar problems) in Linux.
>
> I have Caviar Black and WD RE3, they work OK in Linux.

OK, but:

1. Unlike the link you sent, there's nothing suspicious in any of the 
SMART attributes on any of the four drives - no bad sectors or other 
errors i.e. the following raw values are all zero on the WD drive which 
I've been stressing:

Raw_Read_Error_Rate
Reallocated_Sector_Ct
Seek_Error_Rate
Spin_Retry_Count
Calibration_Retry_Count
Reallocated_Event_Count
Current_Pending_Sector
Offline_Uncorrectable
UDMA_CRC_Error_Count
Multi_Zone_Error_Rate

... as well as empty SMART errors logs.


2. A few failures were seen with the Seagate drives as well (see last 
bits of the email), similarly with no apparent bad SMART attributes.


Thanks,

Tim.

  reply	other threads:[~2010-02-05 14:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05 14:07 SATA drive reset/disable events on ICH7 ata_piix when polling SMART info Tim Small
2010-02-05 14:17 ` [smartmontools-support] " Justin Piszcz
2010-02-05 14:31   ` Tim Small [this message]
2010-02-05 14:48     ` Justin Piszcz
2010-02-05 21:47     ` Mark Lord
2010-02-06  3:39       ` Tejun Heo
2010-02-06 15:26         ` Tim Small
2010-02-06 17:30           ` Mark Lord
2010-02-06 22:22             ` Tim Small
2010-02-07  4:51               ` Mark Lord
2010-02-08  2:40                 ` Tejun Heo
2010-02-08 13:03                 ` Tim Small
2010-02-08  2:49             ` Tejun Heo

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=4B6C2BC8.7000609@buttersideup.com \
    --to=tim@buttersideup.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=smartmontools-support@lists.sourceforge.net \
    /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).