From: Roman Mamedov <rm@romanrm.net>
To: Eyal Lebedinsky <eyal@eyal.emu.id.au>
Cc: list linux-raid <linux-raid@vger.kernel.org>
Subject: Re: possible HighPoint RocketRAID 2720SGL failure
Date: Thu, 21 Sep 2017 17:20:19 +0500 [thread overview]
Message-ID: <20170921172019.2067e49b@natsu> (raw)
In-Reply-To: <73afd1f8-176a-07e9-1024-57692dc96904@eyal.emu.id.au>
On Thu, 21 Sep 2017 21:12:36 +1000
Eyal Lebedinsky <eyal@eyal.emu.id.au> wrote:
> It looks like the controller failed as all 7 disks disappeared together and did not respond
> to any i/o or even smart.
>
> After power off/on things look OK. The raid6 did a very short recovery, then the ext4 fs did
> a quick recovery. fsck found no problems.
>
> I later started a raid 'check' but it failed in less that an hour (out of 10) in the same way.
> A day later I tried again and it failed within 15 minutes.
>
> So far it looks like nothing was lost but I am uncomfortable with this situation.
> No surprise here...
>
> The controller did not log any errors.
>
> Does this look familiar to anyone?
The controller is based on the Marvell 9485 chip and Marvell SATA/RAID
controllers seem to have a bad reputation for reliability:
https://www.jethrocarr.com/2013/11/24/adventures-in-io-hell/
https://www.youtube.com/watch?v=010urq9wY3A
I have also faced some CRC errors or disk drop-outs/reconnects on 9123 cards,
and in one case all disks (or possibly the controller itself) disappear from
the system until reboot on a 88SX7042 based controller.
--
With respect,
Roman
next prev parent reply other threads:[~2017-09-21 12:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 11:12 possible HighPoint RocketRAID 2720SGL failure Eyal Lebedinsky
2017-09-21 12:20 ` Roman Mamedov [this message]
2017-09-22 1:08 ` Roger Heflin
2017-09-22 8:27 ` Eyal Lebedinsky
2017-09-22 13:20 ` Phil Turmel
2017-09-22 22:52 ` Eyal Lebedinsky
2017-09-23 9:29 ` Eyal Lebedinsky
2017-09-23 14:49 ` Phil Turmel
2017-09-23 16:53 ` Wols Lists
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=20170921172019.2067e49b@natsu \
--to=rm@romanrm.net \
--cc=eyal@eyal.emu.id.au \
--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;
as well as URLs for NNTP newsgroup(s).