From: Adam Goryachev <mailinglists@websitemanagers.com.au>
To: Nicolas Tellier <telliern@gmail.com>, Phil Turmel <philip@turmel.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Failed Raid 5 due to OS mbr written on one of the array drives
Date: Wed, 4 Nov 2015 02:45:53 +1100 [thread overview]
Message-ID: <5638D6B1.4010509@websitemanagers.com.au> (raw)
In-Reply-To: <CAArDwD9SDbH-Xdi6hRciLcYkWzY+Kv3JtgtWCyvELffJ=gv+0w@mail.gmail.com>
On 04/11/15 01:21, Nicolas Tellier wrote:
> Hi Phil, and thanks for taking the time to reply to me.
>
> I'm not sure I understood you advice correctly.
> When you say leave off /dev/sdd, do you mean I should recreate a 3
> disks array like this :
> mdadm --create --verbose --assume-clean /dev/md0 --level=5
> --metadata=1.2 --chunk=128 --data-offset=262144 --raid-devices=3
> /dev/sda1 /dev/sdb1 /dev/sdc1
No, but lucky you checked
> Or a 4 disks array with no mention of /dev/sdd, like this (my instinct
> tell me that wouldn't work) :
> mdadm --create --verbose --assume-clean /dev/md0 --level=5
> --metadata=1.2 --chunk=128 --data-offset=262144 --raid-devices=4
> /dev/sda1 /dev/sdb1 /dev/sdc1
No, but lucky you checked
> Or, as I was thinking originally, to put /dev/sdd as missing, like so :
> mdadm --create --verbose --assume-clean /dev/md0 --level=5
> --metadata=1.2 --chunk=128 --data-offset=262144 --raid-devices=4
> /dev/sda1 /dev/sdb1 /dev/sdc1 missing /dev/sdd
No, but lucky you checked
What he means (I'm pretty sure) is that you should run the command:
mdadm --create --verbose --assume-clean /dev/md0 --level=5
--metadata=1.2 --chunk=128 --data-offset=262144 --raid-devices=4
/dev/sda1 /dev/sdb1 /dev/sdc1 missing /dev/sdd
but delete "/dev/sdd" from that, because you are using the wrong syntax.
Specifically, run this command:
mdadm --create --verbose --assume-clean /dev/md0 --level=5
--metadata=1.2 --chunk=128 --data-offset=262144 --raid-devices=4
/dev/sda1 /dev/sdb1 /dev/sdc1 missing
The word missing replaces a device name, because the device doesn't
exist. It doesn't say that the next device name is missing.
> I'm tempted to subscribe to the mailing list, but I'm afraid of the
> volume of e-mail I'm going to get. I originally tried to search
> through the archives, but couldn't find anything relevant to my case.
> I'm looking right now at the "timeout mismatch" results.
The list isn't that busy, I would guess around 10 per day. You can
always unsubscribe after you solve your problem, but staying subscribed
will let you learn a lot about common issues, especially the drive
timeout mismatch issues.
Regards,
Adam
[SNIP]
--
Adam Goryachev
Website Managers
www.websitemanagers.com.au
next prev parent reply other threads:[~2015-11-03 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 17:02 Failed Raid 5 due to OS mbr written on one of the array drives Nicolas Tellier
2015-11-02 18:19 ` Phil Turmel
2015-11-03 14:21 ` Nicolas Tellier
2015-11-03 15:45 ` Adam Goryachev [this message]
2015-11-03 15:47 ` 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=5638D6B1.4010509@websitemanagers.com.au \
--to=mailinglists@websitemanagers.com.au \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.org \
--cc=telliern@gmail.com \
/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.