From: Stan Hoeppner <stan@hardwarefreak.com>
To: Eli Morris <ermorris@ucsc.edu>
Cc: linux-raid@vger.kernel.org
Subject: Re: 4 out of 16 drives show up as 'removed'
Date: Fri, 09 Dec 2011 13:38:13 -0600 [thread overview]
Message-ID: <4EE263A5.3010107@hardwarefreak.com> (raw)
In-Reply-To: <F0C8A2FE-8E5E-4683-BBF8-8E6B6A831635@ucsc.edu>
On 12/7/2011 2:42 PM, Eli Morris wrote:
> I thought maybe someone could help me out. I have a 16 disk software RAID that we use for backup. This is at least the second time this happened- all at once, four of the drives report as 'removed' when none of them actually were. These drives also disappeared from the 'lsscsi' list until I restarted the disk expansion chassis where they live.
>
> These are the dreaded Caviar Green drives.
Eli, you masochist. ;)
> 2) Any idea on how to stop this from happening again?
You already know the answer. You're simply ignoring/avoiding it. It
was given to you by a half dozen imminently qualified people over on the
XFS list when you had an entire chassis blow out many months ago, losing
many students' doctoral thesis data IIRC. I've since used that saga
many times as evidence against using "green" drives, esp the WD models,
for anything but casual desktop storage.
The only permanent fix is to replace the drives with models meant for
your use case, such as the WD RE4 or Seagate Constellation, to name two.
Unfortunately, right now, due to the flooding in Thailand, the price of
all drives across the board has doubled as a result of constricted
supply. Given you don't have funds in the budget to replace them
anyway, at any price, it seems you are simply screwed in this regard.
One thing I would suggest though, if you got the vendor tech's statement
in writing WRT the WD Green drives being compatible with their RAID
chassis, I'd lean hard on them to fix the issue, as it was their rec
that prompted your purchase, causing this problem in the first place, no?
--
Stan
next prev parent reply other threads:[~2011-12-09 19:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 20:42 4 out of 16 drives show up as 'removed' Eli Morris
2011-12-07 20:51 ` Mathias Burén
2011-12-07 20:57 ` NeilBrown
2011-12-07 22:00 ` Eli Morris
2011-12-07 22:16 ` NeilBrown
2011-12-07 23:42 ` Eli Morris
2011-12-08 19:17 ` Eli Morris
2011-12-08 19:51 ` NeilBrown
2011-12-08 20:39 ` Eli Morris
2011-12-08 20:59 ` NeilBrown
2011-12-08 21:42 ` Eli Morris
2011-12-08 22:50 ` NeilBrown
2011-12-08 23:03 ` Eli Morris
2011-12-09 3:20 ` NeilBrown
2011-12-09 6:58 ` Eli Morris
2011-12-09 15:31 ` John Stoffel
2011-12-09 16:40 ` Asdo
2011-12-09 19:38 ` Stan Hoeppner [this message]
2011-12-09 22:07 ` Eli Morris
2011-12-10 2:29 ` Stan Hoeppner
2011-12-10 4:57 ` Eli Morris
2011-12-11 1:15 ` Stan Hoeppner
2011-12-10 17:28 ` wilsonjonathan
2011-12-10 17:43 ` wilsonjonathan
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=4EE263A5.3010107@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=ermorris@ucsc.edu \
--cc=linux-raid@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox