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: Thu, 2 Mar 2017 15:00:40 -0800 [thread overview]
Message-ID: <008d01d293a8$d24b1350$76e139f0$@wnsdev.com> (raw)
In-Reply-To: <ce5ec33c-c38b-de76-1976-bea9e7caba68@turmel.org>
> Correct. But it shouldn't be able to boot from the others either, with grub1.
> Something has changed in your grub install since you set up the original drives. Only
> grub2 would be able to boot from your v1.2 md0.
>
> { Sorry. I don't know how to fix grub2's md module. }
>
Just to so I'm crystal clear : the server needs to have grub2 installed so doesn't this confirm grub2 is installed.
grub-install -V
grub-install (GRUB) 2.02~beta2-36ubuntu3.2
and since I'm running Ubuntu 16.04.1 LTS
from https://help.ubuntu.com/community/Grub2
"GRUB 2 is the default boot loader and manager for Ubuntu since version 9.10"
"GRUB 2 is version 1.98 or later"
What Am I missing?
next prev parent reply other threads:[~2017-03-02 23:00 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
2017-03-02 0:05 ` Phil Turmel
2017-03-02 23:00 ` Peter Sangas [this message]
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='008d01d293a8$d24b1350$76e139f0$@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).