All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Fjellstrom <tfjellstrom@strangesoft.net>
To: Tejun Heo <htejun@gmail.com>
Cc: Robert Hancock <hancockrwd@gmail.com>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: failed command FLUSH CACHE EXT
Date: Thu, 3 Jun 2010 02:41:10 -0600	[thread overview]
Message-ID: <201006030241.11102.tfjellstrom@strangesoft.net> (raw)
In-Reply-To: <4C07666A.7000705@gmail.com>

On June 3, 2010, Tejun Heo wrote:
> Hello,
> 
> On 06/03/2010 01:42 AM, Thomas Fjellstrom wrote:
> > I seem to have rather bad luck with hard drives. Every time I buy more
> > than two, I tend to get one or two failures out of the batch. 25-50%
> > failure rate almost. Horrible. I at least average 1 dead hard drive a
> > year since I got my first computer.
> 
> Hmmm... that sounds really high.  Out of how many?  Hard drives do
> fail sometimes but not that easily even if you put it under relatively
> heavy use 24/7.  Maybe there is a common cause - say, instable power,
> vibration, impact or whatever?  Or maybe the universe just doesn't
> like you?  :-)
> 
> Thanks.

I think its a combination of factors. But mainly, early on I was cheap. UBER 
cheap, nor did I know that a power supply is probably the /most/ important 
component in a machine. If it helps I've also had many motherboards, tons of 
ram, and some misc other parts fail over the years as well, but I've 
probably gone through more hard drives than anything else.

Let me see if I can count all of them... 

1x6G   - failed
1x40G  - failed
4x80G  - 2 failed (PSU kill)
2x160G - 1 failed (used drives anyhow, don't really count)
4x320G - 2 failed (DOA, well after a week each)
4x640G - 1-2 failed (can't really remember the circumstances with these...)
6x1T   - 1 failed (DOA)
4x2T   - 2 failed (1 DOA, 1 after a year)

So about half.

I mostly blame my cheapness when I was younger. Bad PSU's can cause a lot of 
problems. I've since stopped buying and using cheap power supplies. And it 
has so far made a difference in death count. If I skip the DOA drives, only 
one 1TB, 1 2TB and 1 640 failed. Thats far better than a 50% mortality rate.

That list may not be entirely accurate, it spans over 10 years of hd use. I 
can barely remember what I did the day before, let alone the details of 
things that happened 10 years ago.

-- 
Thomas Fjellstrom
tfjellstrom@strangesoft.net

      reply	other threads:[~2010-06-03  8:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-30  2:46 via 8237 sata errors Thomas Fjellstrom
2010-05-30 18:40 ` Robert Hancock
2010-05-30 18:57   ` Thomas Fjellstrom
2010-05-30 19:33     ` Thomas Fjellstrom
2010-05-30 19:40       ` Robert Hancock
2010-05-30 19:48         ` Thomas Fjellstrom
2010-05-31  1:19           ` Thomas Fjellstrom
2010-06-02 21:10             ` failed command FLUSH CACHE EXT (was: Re: via 8237 sata errors) Thomas Fjellstrom
2010-06-02 23:05               ` Robert Hancock
2010-06-02 23:42                 ` Thomas Fjellstrom
2010-06-03  8:23                   ` failed command FLUSH CACHE EXT Tejun Heo
2010-06-03  8:41                     ` Thomas Fjellstrom [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=201006030241.11102.tfjellstrom@strangesoft.net \
    --to=tfjellstrom@strangesoft.net \
    --cc=hancockrwd@gmail.com \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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.