From: "Mathias Burén" <mathias.buren@gmail.com>
To: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: RAID6 check found different events, how should I proceed?
Date: Sat, 6 Aug 2011 17:02:48 +0100 [thread overview]
Message-ID: <CADNH=7FBkx5HgWKiEzL_sNZvbjjTMbS23wOYXyrmPETCRbVwOw@mail.gmail.com> (raw)
In-Reply-To: <CADNH=7Eiqx0wCFypxqy-DSKWmr62L83MpP+V8XzjMEWJ3NE0yw@mail.gmail.com>
On 6 August 2011 14:23, Mathias Burén <mathias.buren@gmail.com> wrote:
> My RAID6 is currently degraded with one HDD (panic mail on the list),
> and my weekly cron job kicked in doing the RAID6 check action. This is
> the result:
>
> DEV EVENTS REALL PEND UNCORR CRC RAW ZONE END
> sdb1 6239487 0 0 0 2 0 0
> sdc1 6239487 0 0 0 0 0 0
> sdd1 6239487 0 0 0 0 0 0
> sde1 6239487 0 0 0 0 0 0
> sdf1 6239490 0 0 0 0 49 6
> sdg1 6239491 0 0 0 0 0 0
> sdh1 (missing, on RMA trip)
>
(snip)
> * Should I run a repair?
> * Chould I run a check again, to see if the event count changes?
> * Is it likely I've 2 more bad harddrives that will die soon?
> * Is it wise to run another smartctl -t long on all devices?
>
> Thanks,
> Mathias
>
A followup;
I ran smartctl -t long on all devices, and they all passed, SMART is
fine. The number of events is also the same for all HDDs now:
DEV EVENTS REALL PEND UNCORR CRC RAW ZONE END
sdb1 6244415 0 0 0 2 0 0
sdc1 6244415 0 0 0 0 0 0
sdd1 6244415 0 0 0 0 0 0
sde1 6244415 0 0 0 0 0 0
sdf1 6244415 0 0 0 0 49 6
sdg1 6244415 0 0 0 0 0 0
sdh1
This is without me running repair or anything like that.
Mathias
next prev parent reply other threads:[~2011-08-06 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 13:23 RAID6 check found different events, how should I proceed? Mathias Burén
2011-08-06 16:02 ` Mathias Burén [this message]
[not found] ` <CALvtuFTKBRtco1VFw9xv6x3qsLx+rdJg2wL8E9+1g3LQf=Xkuw@mail.gmail.com>
2011-08-06 17:09 ` Cal Leeming [Simplicity Media Ltd]
2011-08-08 22:57 ` NeilBrown
2011-08-06 17:54 ` Alexander Kühn
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='CADNH=7FBkx5HgWKiEzL_sNZvbjjTMbS23wOYXyrmPETCRbVwOw@mail.gmail.com' \
--to=mathias.buren@gmail.com \
--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).