From: Phil Turmel <philip@turmel.org>
To: Stefan Lamby <webmaster@peter-speer.de>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Raid 1 needs repair
Date: Thu, 4 Feb 2016 16:30:57 -0500 [thread overview]
Message-ID: <56B3C311.5060407@turmel.org> (raw)
In-Reply-To: <43098506.459602.1454607669214.JavaMail.open-xchange@app01.ox.hosteurope.de>
On 02/04/2016 12:41 PM, Stefan Lamby wrote:
>
>> You may also need "mdadm --zero-superblock /dev/sda1" before the add
>> command.
>>
>> But if it's currently active in the array, why do you need to fail it?
>
> So this is the right way?
>
> mdadm --manage /dev/md0 --remove /dev/sda1 # remove failed disk from array
> mdadm --zero-superblock /dev/sda1
> mdadm --manage /dev/md0 --add /dev/sda1 # add new disk to array (assumed same or
> greater space for partition)
Your mdstat and your lsdrv output disagree on the status of /dev/sdb1.
If mdstat is current, what belongs to what? Your --examine results
suggest sda1 and sdb1 go together, but mdstat shows sdc1 running with
sdb1 in another array and sda1 all alone. If sda1 is all alone in an
array you can't remove it.
Your device names are probably changing between boots (not unusual) and
it is confusing your report.
Please show lsdrv results after you add the proper utilities to the
environment you run lsdrv from. At least install lvm utilities and
mdadm utilities.
Phil
next prev parent reply other threads:[~2016-02-04 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 14:21 Raid 1 needs repair Stefan Lamby
2016-02-04 14:51 ` Phil Turmel
2016-02-04 16:03 ` Stefan Lamby
2016-02-04 16:45 ` Phil Turmel
2016-02-04 17:41 ` Stefan Lamby
2016-02-04 21:30 ` Phil Turmel [this message]
2016-02-05 10:02 ` Stefan Lamby
[not found] ` <1543635690.543147.1454691080103.JavaMail.open-xchange@app03.ox.hosteurope.de>
2016-02-05 16:54 ` [SOLVED] " Phil Turmel
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=56B3C311.5060407@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=webmaster@peter-speer.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 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.