From: Wols Lists <antlists@youngman.org.uk>
To: Paul Tonelli <paul@tonel.li>,
Andreas Klauer <Andreas.Klauer@metamorpher.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Recovery after accidental raid5 superblock rewrite
Date: Mon, 31 Jul 2017 21:35:33 +0100 [thread overview]
Message-ID: <597F9495.9060507@youngman.org.uk> (raw)
In-Reply-To: <e0c059b0-2d68-92bf-3eb9-e2827602061c@tonel.li>
On 31/07/17 20:57, Paul Tonelli wrote:
> but a reboot always brings me back to step 2), with the need to press
> ctrl-D at boot time.
>
> What am I missing? Am I using a bad version of the mdadm or kernel
> (mdadm:amd64 3.3.2-5+deb8u2, kernel 4.8.0-0.bpo.2-amd64) or am I doing
> it wrong in another way ?
Okay. Step 2. Does an "mdadm --assemble --scan" work instead? This will
tell us whether your raid array is fine, just that it's not being
properly assembled at boot. Actually, before you do that, try a "mdadm
/dev/md0 --stop".
If the stop then assemble scan works, it tells us that your boot
sequence is at fault, not the array.
Can you post the relevant section of grub.cfg? That might not be
assembling the arrays.
Cheers,
Wol
next prev parent reply other threads:[~2017-07-31 20:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 19:46 Recovery after accidental raid5 superblock rewrite Paul Tonelli
2017-06-03 21:20 ` Andreas Klauer
2017-06-03 22:33 ` Paul Tonelli
2017-06-03 23:29 ` Andreas Klauer
2017-06-04 22:58 ` Paul Tonelli
2017-06-05 9:24 ` Andreas Klauer
2017-06-05 23:24 ` Paul Tonelli
2017-06-05 23:56 ` Andreas Klauer
2017-06-10 20:04 ` Paul Tonelli
2017-06-10 20:41 ` Andreas Klauer
2017-07-31 19:57 ` Paul Tonelli
2017-07-31 20:35 ` Wols Lists [this message]
2017-08-01 14:01 ` 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=597F9495.9060507@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=Andreas.Klauer@metamorpher.de \
--cc=linux-raid@vger.kernel.org \
--cc=paul@tonel.li \
/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.