From: Phil Turmel <philip@turmel.org>
To: Eyal Lebedinsky <eyal@eyal.emu.id.au>,
list linux-raid <linux-raid@vger.kernel.org>
Cc: Wolfgang Denk <wd@denx.de>, Brad Campbell <lists2009@fnarfbargle.com>
Subject: Re: [sucess] upgrading LSI SAS9211-8i fw IR->IT
Date: Mon, 6 Nov 2017 16:48:16 -0500 [thread overview]
Message-ID: <0eba8116-169e-4ca6-262a-dfcc3c8ed5f9@turmel.org> (raw)
In-Reply-To: <5006e53f-5df1-df17-732f-73a5a7d3349e@eyal.emu.id.au>
On 11/06/2017 04:38 PM, Eyal Lebedinsky wrote:
> On 07/11/17 07:15, Wolfgang Denk wrote:
>> Dear Eyal,
>>
>> In message <c12a2a32-2321-1ed7-e1de-ce0e408552e1@eyal.emu.id.au>
>> you wrote:
>>>
>>> (I had many disk failures/replacements in the 4 years life of
>>> this array).
>>
>> Reading this makes me wonder if you checked your environment for
>> other influences. there must be some reason for an exceptional
>> high number of failures.
>>
>> I remeber we also had a nighmare of disk errors in the rack in the
>> 2nd floor of our building - which disappeared after moving the
>> rack into the basement. I can't prove it, but I blame it on
>> vibrations. We have a heavy traffic train line less than 50 meters
>> away, and disks (classic, magnetic ones) definitely do not like
>> vibrations - see [1]. Maybe you have other influences you did not
>> check for yet?
>
> Interesting Wolfgang,
>
> - This array is at home, a relatively quiet place. - I monitor the
> disks temperatures and it is OK. - The machine runs off a UPS which
> can be a source of bad power (if the PS does not filter it out). -
> The HBA may be somehow bothering the disks?
>
> The disks are under warranty until late next year so there is time to
> see if the disks do better with the LSI.
>
> BTW, two of the RMAs were for disks that arrived DOA (as RMAs). I do
> not have high regard for the WD blacks. The failures were spread
> across the last 4 years (so not infant mortality).
>
> If nothing else, this experience made me comfortable with software
> raid, and encouraged me to stick to my backup schedule.
That's a really bad failure rate. But they're WD Blacks, which if I
recall correctly, do not support scterc. Did you deal with your driver
timeouts? If not, those drives probably weren't really dead. Just not
raid-compatible out-of-the-box.
Phil
next prev parent reply other threads:[~2017-11-06 21:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 11:47 upgrading LSI SAS9211-8i fw IR->IT Eyal Lebedinsky
2017-10-24 12:14 ` Roman Mamedov
2017-10-24 13:04 ` Eyal Lebedinsky
2017-10-24 17:59 ` Roman Mamedov
2017-10-26 3:31 ` [sucess?] " Eyal Lebedinsky
2017-10-27 23:09 ` Eyal Lebedinsky
2017-10-29 15:02 ` Brad Campbell
2017-11-02 10:51 ` [sucess] " Eyal Lebedinsky
2017-11-03 0:54 ` Brad Campbell
2017-11-03 2:31 ` Eyal Lebedinsky
2017-11-03 3:03 ` Brad Campbell
2017-11-03 3:39 ` Eyal Lebedinsky
2017-11-06 20:15 ` Wolfgang Denk
2017-11-06 21:38 ` Eyal Lebedinsky
2017-11-06 21:48 ` Phil Turmel [this message]
2017-11-06 21:59 ` Eyal Lebedinsky
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=0eba8116-169e-4ca6-262a-dfcc3c8ed5f9@turmel.org \
--to=philip@turmel.org \
--cc=eyal@eyal.emu.id.au \
--cc=linux-raid@vger.kernel.org \
--cc=lists2009@fnarfbargle.com \
--cc=wd@denx.de \
/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