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 20:29:20 -0600 [thread overview]
Message-ID: <4EE2C400.2000100@hardwarefreak.com> (raw)
In-Reply-To: <381720EC-8DCA-4862-9C62-22954CC7AA60@ucsc.edu>
On 12/9/2011 4:07 PM, Eli Morris wrote:
> So, that's not so great. As you mention in your last paragraph, the reason why we had Caviar Green drives to begin with is that our RAID vendor recommended them to us specifically for use in the RAID where they failed. I spoke with him after they failed and he insists that these drives were not the problem and that they are used without problem in similar RAIDs. He seems like a good guy, but ultimately, I have no way of knowing what to think of that. He thinks the four drives 'failed' because of a backplane issue, but, since the unit is older and out of warranty, and thus costly, that isn't really worth investigating.
Sure it is, if your data has value. The style of backplanbe you have,
4x3 IIRC, is cheap. If one board is flaky, replace it. They normally
run only a couple hundred dollars, assuming your OEM still has some in
inventory.
If not, and you have $1500 squirreled away somewhere in the budget, grab
one of these and move the drives over:
http://www.newegg.com/Product/Product.aspx?Item=N82E16816133047
Sure, the Norco is definitely a low dollar 24 drive SAS/SATA JBOD unit.
But the Areca expander module is built around the LSI SAS 2x36 ASIC,
the gold standard SAS expander chip on the market.
Do you have any dollars in your yearly budget for hardware
maintenance/replacement?
--
Stan
next prev parent reply other threads:[~2011-12-10 2:29 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
2011-12-09 22:07 ` Eli Morris
2011-12-10 2:29 ` Stan Hoeppner [this message]
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=4EE2C400.2000100@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 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.