From: Phil Turmel <philip@turmel.org>
To: Adam Goryachev <mailinglists@websitemanagers.com.au>,
Daniel Jones <dj@iowni.com>
Cc: Wols Lists <antlists@youngman.org.uk>, linux-raid@vger.kernel.org
Subject: Re: Requesting assistance recovering RAID-5 array
Date: Fri, 3 Apr 2020 16:14:46 -0400 [thread overview]
Message-ID: <d2db8ad1-9fb3-4d08-3fdd-2eb06a931859@turmel.org> (raw)
In-Reply-To: <3f771f84-1c0d-8617-faa7-22657d9de95e@websitemanagers.com.au>
On 4/3/20 4:13 PM, Adam Goryachev wrote:
>
> On 4/4/20 05:43, Phil Turmel wrote:
>>
>> On 4/3/20 2:42 PM, Daniel Jones wrote:
>>> After the "--create missing /dev/sdc1 /dev/sdd1 /dev/sde1" and the
>>> fsck, is "mdadm --manage /dev/md0 --add /dev/sdb" the correct syntax
>>> for attempting to add?
>>
>> You can leave out "--manage". But yes.
>
> I was mostly following this, but might have missed something here so
> this is just a suggestion to double check....
>
> If you are trying to use partitions instead of whole devices (to prevent
> this happening again in future), then shouldn't you use:
>
> mdadm --manage /dev/md0 --add /dev/sdb1
>
> ie, sdb1 not sdb....
Yes. Good catch.
prev parent reply other threads:[~2020-04-03 20:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 0:04 Requesting assistance recovering RAID-5 array Daniel Jones
2020-03-31 0:24 ` antlists
2020-03-31 0:51 ` Daniel Jones
2020-03-31 1:27 ` crowston.name
2020-03-31 1:50 ` Phil Turmel
2020-03-31 1:48 ` Phil Turmel
2020-03-31 2:09 ` Daniel Jones
2020-03-31 12:00 ` Phil Turmel
2020-03-31 13:36 ` Daniel Jones
2020-04-01 3:39 ` Daniel Jones
2020-04-01 4:45 ` Phil Turmel
2020-04-01 6:03 ` Daniel Jones
2020-04-01 12:15 ` Wols Lists
2020-04-01 12:55 ` Phil Turmel
2020-04-01 15:21 ` Daniel Jones
2020-04-01 15:38 ` Phil Turmel
2020-04-01 15:39 ` Phil Turmel
2020-04-01 18:07 ` Daniel Jones
2020-04-01 18:32 ` Phil Turmel
2020-04-03 18:29 ` Daniel Jones
2020-04-03 18:34 ` Phil Turmel
2020-04-03 18:42 ` Daniel Jones
2020-04-03 18:43 ` Phil Turmel
2020-04-03 20:13 ` Adam Goryachev
2020-04-03 20:14 ` Phil Turmel [this message]
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=d2db8ad1-9fb3-4d08-3fdd-2eb06a931859@turmel.org \
--to=philip@turmel.org \
--cc=antlists@youngman.org.uk \
--cc=dj@iowni.com \
--cc=linux-raid@vger.kernel.org \
--cc=mailinglists@websitemanagers.com.au \
/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