From: "Timothy D. Lenz" <tlenz@vorgon.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: Putting grub back on new mirror disk
Date: Thu, 14 Mar 2013 21:41:18 -0700 [thread overview]
Message-ID: <5142A66E.9010304@vorgon.com> (raw)
In-Reply-To: <A7E78320-768A-43AE-AE1D-1BF9E52D5713@colorremedies.com>
Ok, was thinking it was checking that grub got installed. So the map may
have had the old drive listed instead of the new drive. But the map was
force updated to match.
On 3/14/2013 5:57 PM, Chris Murphy wrote:
> On Mar 14, 2013, at 6:48 PM, Timothy D. Lenz <tlenz@vorgon.com> wrote:
>
>> hd0 would have changed because it's a new drive. But all the numbers match the device list at /dev/disk/by-id
>
> I don't understand what you're saying or asking. The --recheck flag causes grub-install to look at /dev/disk/by-id to create a new device.map. So the device.map and /dev/disk/by-id should be the same, at least with this variant of GRUB. Some use /dev/sdX designations, some use UUID.
>
>
> Chris Murphy
>
next prev parent reply other threads:[~2013-03-15 4:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 2:29 Putting grub back on new mirror disk Timothy D. Lenz
[not found] ` <CAD4F9C5-6A55-421A-BFAD-B23D72662054@colorremedies.com>
2013-03-14 7:13 ` Timothy D. Lenz
2013-03-14 21:01 ` Timothy D. Lenz
2013-03-14 21:07 ` Chris Murphy
[not found] ` <51423CB4.6010803@vorgon.com>
[not found] ` <947D0B46-E42D-41A6-A408-99CB4AAA374C@colorremedies.com>
[not found] ` <514241A2.6020301@vorgon.com>
2013-03-14 21:39 ` Chris Murphy
2013-03-15 0:48 ` Timothy D. Lenz
[not found] ` <A7E78320-768A-43AE-AE1D-1BF9E52D5713@colorremedies.com>
2013-03-15 4:41 ` Timothy D. Lenz [this message]
2013-03-15 4:48 ` Chris Murphy
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=5142A66E.9010304@vorgon.com \
--to=tlenz@vorgon.com \
--cc=linux-raid@vger.kernel.org \
--cc=lists@colorremedies.com \
/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.