All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: grub legacy to grub2 upgrade path
Date: Thu, 23 Feb 2012 06:44:08 +0100	[thread overview]
Message-ID: <4F45D228.5030409@gmail.com> (raw)
In-Reply-To: <fc00e67ec8f0e787bdad4d23f9a1e0bb.squirrel@webmail.frugalware.org>

On 23.02.2012 05:14, ryuo@frugalware.org wrote:
> I am a senior developer for the Frugalware Linux distribution, and I am
> trying to find an upgrade path so we can leave grub legacy behind. Normal
> disk installations work perfectly under testing, however I have found a
> snag with RAID installations we have to support that were setup under grub
> legacy, which we installed under metadata 0.90 because of the limitations
> of grub legacy.
>
> The problem appears to be this bug: http://savannah.gnu.org/bugs/?34250
See parallel thread for heuristics. However note that this setup is 
fundamentally broken
> It effects RAID setups that only use a single partition per disk, and in
> my tests I got errors from grub-install of this kind:
> http://frugalware.org/paste/13418
>
> The problem seems to be that grub2 is unable to deduce *where* the RAID
> really is.
>
> I tried installing to the MBR of both disks and RAID device, using a
> simple grub-install command. (grub-install /dev/md0, etc.) I did my
> testing with a mostly vanilla 1.99 grub2.
>
> If any of our users happen to run into this issue, what are we to tell
> them to do? I'd like another option than forcing them to have to redo
> their RAID setup.
>
> Any insights would be appreciated.
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



  reply	other threads:[~2012-02-23  5:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23  4:14 grub legacy to grub2 upgrade path ryuo
2012-02-23  5:44 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2012-02-24  2:54   ` Jordan Uggla
2012-02-24 13:34     ` ryuo

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=4F45D228.5030409@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.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.