From: "Peter Sangas" <pete@wnsdev.com>
To: 'Wols Lists' <antlists@youngman.org.uk>,
'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: Mon, 6 Mar 2017 14:13:58 -0800 [thread overview]
Message-ID: <008401d296c6$f5ee1e80$e1ca5b80$@wnsdev.com> (raw)
In-Reply-To: <58B81B80.6020708@youngman.org.uk>
> On March 02, 2017 5:18 AM, Wols Lists wrote :
> Look at the raid wiki
>
> https://raid.wiki.kernel.org/index.php/Converting_an_existing_system
>
> it mentions grub.
Wol, I'm trying to understand what you and others are suggesting is causing this grub warning.
according to the raid.wiki you referenced the last line of grub.cnf should look like this to support booting from RAID:
initrd /boot/initramfs-genkernel-x86_64-4.4.6-gentoo
In addition, the wiki says " you will need to configure your distro to use an initramfs.
here are the last few lines of my grub.cnf:
echo 'Loading Linux 4.4.0-36-generic ...'
linux /vmlinuz-4.4.0-36-generic root=UUID=cddffa50-9713-4205-aab6-86745735958b ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /initrd.img-4.4.0-36-generic
should I be concerned my grub.cnf uses initrd.img and not initramfs? My grub.cnf was last modified 11/2016 and I've rebooted successfully into a RAID1 since.
Finally, on Friday 3/3 I swapped one of the disks (sdc) in this RAID1 with a brand new identical disk. After creating the partitions and syncing I issued
install-grub /dev/sdc and there were no warnings. If my grub was broken why would there be no warning but a week ago doing the exact disk swap/same sequence of commands I got a warning. Nothing on the system was changed during that time.
Thank you.
next prev parent reply other threads:[~2017-03-06 22:13 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
2017-03-02 13:17 ` Wols Lists
2017-03-06 22:13 ` Peter Sangas [this message]
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='008401d296c6$f5ee1e80$e1ca5b80$@wnsdev.com' \
--to=pete@wnsdev.com \
--cc=antlists@youngman.org.uk \
--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).