All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: the order of the modules when create core image
Date: Sat, 22 Nov 2008 21:00:22 +0100	[thread overview]
Message-ID: <20081122200022.GD7779@thorin> (raw)
In-Reply-To: <917276.21692.qm@web15701.mail.cnb.yahoo.com>

On Mon, Nov 17, 2008 at 03:22:19PM +0800, yue315012-grub2@yahoo.com.cn wrote:
> Hi, all,
> I don't know which mail list should I send this question to, so I send to here. Hope somebody will help me.
> I create a MD raid0 in my VirtualBox that has two virtual disks (I create the Virtual PC according to my old PC.) Each disk has 2 partitions, one for raid, one for swap. no LVM on the raid0. and I want to use grub2 on it.
> I got the src from svn 2008-11-11. and compiled it successfully. But when I install it with 
> grub-install --modules=mdraid /dev/hda, the grub2 can't enter into normal mode. With ls command, it don't show the md1 device.
> So I changed the module order in grub-install when create core image, move the $module to after biosdisk, and install again, the it shows the md1device. 

Supporting this from user input is quite tricky.  Would be much better if it
can be auto-detected, like we do for LVM, etc.

What does "grub-probe -t abstraction /boot/grub" print?

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



      reply	other threads:[~2008-11-22 20:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-17  7:22 the order of the modules when create core image yue315012-grub2
2008-11-22 20:00 ` Robert Millan [this message]

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=20081122200022.GD7779@thorin \
    --to=rmh@aybabtu.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.