From: "Peter Sangas" <pete@wnsdev.com>
To: 'Wols Lists' <antlists@youngman.org.uk>, linux-raid@vger.kernel.org
Subject: RE: Read data from disk that was part of RAID1 array
Date: Mon, 20 Mar 2017 10:37:36 -0700 [thread overview]
Message-ID: <006a01d2a1a0$ac148170$043d8450$@wnsdev.com> (raw)
In-Reply-To: <58CE5AF8.5070907@youngman.org.uk>
> From: Wols Lists [mailto:antlists@youngman.org.uk]
> NEVER NEVER NEVER use --create !!!
>
>
> Use something like --assemble --force, which will set up a working array
if it can.
OK, I tried this command but received an error:
mdadm --assemble --force /dev/md10 /dev/sdc
"Cannot assemble mbr metadata in /dev/sdc, no superblock"
What command do you suggest...?
> If that had been an old array, with a different offset or superblock or
the like...
by "old" do you mean an array created using a different superblock format
other than 1.2?
Thanks,
Pete
next prev parent reply other threads:[~2017-03-20 17:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 22:18 Read data from disk that was part of RAID1 array Peter Sangas
2017-03-16 22:31 ` Reindl Harald
2017-03-17 23:17 ` Peter Sangas
2017-03-19 10:18 ` Wols Lists
2017-03-20 17:37 ` Peter Sangas [this message]
2017-03-20 19:33 ` Wols Lists
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='006a01d2a1a0$ac148170$043d8450$@wnsdev.com' \
--to=pete@wnsdev.com \
--cc=antlists@youngman.org.uk \
--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