From: Phil Turmel <philip@turmel.org>
To: "Paramasivam, Meenakshisundaram" <mparamas@iupui.edu>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: mdadm RAID6 faulty drive
Date: Mon, 25 Mar 2013 13:43:50 -0400 [thread overview]
Message-ID: <51508CD6.50702@turmel.org> (raw)
In-Reply-To: <B2B36B3006DB4C47A56D6BA19443F5D12DE79EF4@IU-MSSG-MBX110.ads.iu.edu>
On 03/25/2013 12:02 PM, Paramasivam, Meenakshisundaram wrote:
>
> Hi,
>
> As a result of extended power outage, the FedoraCore 17 machine with
> mdadm RAID went down. Bringing it up, I noticed "faulty /dev/sdf" in
> mdadm -detail. However mdadm -E /dev/sdf shows "State : clean".
> Details are shown below. When I tried to add the drive to array,
> resync fails (I see lots of eSATA bus resets), and I get the same
> message in mdadm -detail.
>
> Questions:
> 1. How can a clean drive be reported faulty?
When the drive is kicked out for I/O errors its superblock is left as-is
(just as if you pulled its sata cable). The remaining devices'
superblocks are marked to show the failed drive, and *their*
superblocks' event count is bumped. The failed status of that device is
derived during assembly when its superblock is found to be stale.
> 2. Is there a easy way to mark drive (/dev/sdf) as "assume-clean" and
> add it?
No. The closest thing is to use a write-intent bitmap and "re-add"
devices that are disconnected.
That's not your problem.
> Please let me know if I should get an exact replacement drive at
> this stage, pull out faulty /dev/sdf, and add the new drive to array.
> Thanks.
You very likely need a new drive. You might want to try plugging that
drive into a different controller, or a different port on the same
controller, just to narrow the diagnosis.
You could also show us some of the kernel error messages, or show the
output of "smartctl -x /dev/sdf".
Phil
next prev parent reply other threads:[~2013-03-25 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 16:02 mdadm RAID6 faulty drive Paramasivam, Meenakshisundaram
2013-03-25 17:43 ` Phil Turmel [this message]
2013-03-26 20:05 ` Roy Sigurd Karlsbakk
2013-03-27 20:46 ` Paramasivam, Meenakshisundaram
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=51508CD6.50702@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mparamas@iupui.edu \
/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).