From: "Peter Sangas" <pete@wnsdev.com>
To: 'Phil Turmel' <philip@turmel.org>,
'Reindl Harald' <h.reindl@thelounge.net>,
linux-raid@vger.kernel.org
Subject: RE: GRUB warning after replacing disk drive in RAID1
Date: Wed, 1 Mar 2017 15:51:12 -0800 [thread overview]
Message-ID: <008401d292e6$b6d743e0$2485cba0$@wnsdev.com> (raw)
In-Reply-To: <5136f32b-a0bb-dc16-cae9-59946ea21622@turmel.org>
>{ Convention on kernel.org is to reply-to-all, trim unneeded quoted material, and bottom post or interleave. Please do so. }
Yes. thank you.
>Grub1 needs its boot partitions to use v0.90 or v1.0 superblocks. Grub2 needs the md module in its core to boot from v1.1 or v1.2 superblocks.
>Anyways, because the content of a v1.2 array does not start at the beginning of the member devices, stupid grub doesn't connect sd[abc]1 with your /boot mount >and therefore delivers 'null'.
>And then doesn't know how to link the core together.
can't say I understand all that but does this mean the server can't boot from the replacement drive?
next prev parent reply other threads:[~2017-03-01 23:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 23:37 GRUB warning after replacing disk drive in RAID1 Peter Sangas
2017-02-28 9:23 ` Reindl Harald
2017-02-28 21:01 ` Peter Sangas
2017-02-28 22:34 ` Reindl Harald
2017-02-28 23:15 ` Peter Sangas
2017-03-01 0:12 ` Reindl Harald
2017-03-01 23:36 ` Peter Sangas
2017-03-02 9:54 ` Reindl Harald
2017-03-01 18:29 ` Phil Turmel
2017-03-01 22:13 ` Reindl Harald
2017-03-02 2:42 ` Phil Turmel
2017-03-02 13:15 ` Wols Lists
2017-03-01 23:51 ` Peter Sangas [this message]
2017-03-02 0:05 ` Phil Turmel
2017-03-02 23:00 ` Peter Sangas
2017-03-02 13:17 ` Wols Lists
2017-03-06 22:13 ` Peter Sangas
2017-03-07 12:54 ` Wols Lists
2017-03-07 13:00 ` Reindl Harald
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='008401d292e6$b6d743e0$2485cba0$@wnsdev.com' \
--to=pete@wnsdev.com \
--cc=h.reindl@thelounge.net \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.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 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.