From: Robert Hancock <hancockrwd@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: Linda Walsh <lkml@tlinx.org>,
linux-ide@vger.kernel.org, Jeff Garzik <jeff@garzik.org>
Subject: Re: Port Multiplier access with Sil 3124
Date: Wed, 11 Feb 2009 22:16:32 -0600 [thread overview]
Message-ID: <4993A2A0.7020606@gmail.com> (raw)
In-Reply-To: <49923356.6050405@kernel.org>
Tejun Heo wrote:
> Linda Walsh wrote:
>> I also had a triple Seagate drive failure within 2 months,
>> two of them within a week -- and I did lose *backups* of my primary
>> drives!
>
> My test disks go through a lot of unusual workloads which often
> include frequent emergency head unloads with immediately following
> spin up and Seagate has been the sturdiest for quite some time now.
> It's sad to hear that they're degressing. :-(
It seems like most of the problems have been firmware and not
mechanical, but a coworker did have a Seagate 7200.11 disk recently
start getting SMART errors, which doesn't seem like any of the usual
firmware symptoms that have been reported.
Went with a WD Caviar Black for a recent drive purchase instead..
hopefully Seagate will get their act together for the next models.
next prev parent reply other threads:[~2009-02-12 4:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-08 20:38 Port Multiplier access with Sil 3124 Linda Walsh
2009-02-09 9:26 ` Grant Grundler
2009-02-09 22:01 ` Linda Walsh
2009-02-09 14:35 ` Greg Freemyer
2009-02-09 20:09 ` Mark Lord
2009-02-09 22:22 ` Linda Walsh
2009-02-09 23:01 ` Greg Freemyer
2009-02-10 0:15 ` Jeff Garzik
2009-02-10 1:07 ` Linda Walsh
2009-02-10 3:48 ` Jeff Garzik
2009-02-11 2:09 ` Tejun Heo
2009-02-12 4:16 ` Robert Hancock [this message]
2009-02-10 3:25 ` Greg Freemyer
2009-02-11 2:12 ` 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=4993A2A0.7020606@gmail.com \
--to=hancockrwd@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=lkml@tlinx.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 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.