From: Jeroen Dekkers <jeroen@vrijschrift.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: 381150-forwarded@bugs.debian.org, martin f krafft <madduck@debian.org>
Subject: Re: Bug#381150: still not able to handle partitionable arrays
Date: Fri, 18 May 2007 01:28:15 +0200 [thread overview]
Message-ID: <87fy5vuj1s.wl@dekkers.cx> (raw)
In-Reply-To: <20070504232907.GA19279@aragorn>
At Sat, 5 May 2007 01:29:07 +0200,
Robert Millan wrote:
> It seems there are problems with accessing software RAID in devices with
> pathnames like /dev/md_d0p1
>
> On Sat, Jan 06, 2007 at 05:59:16PM +0100, martin f krafft wrote:
> >
> > grub2 1.95-2 still does not support partitionable arrays:
> >
> > [...]
> >
> > debian# grub-probe -v /boot
> > grub-probe: info: changing current directory to /dev
> > grub-probe: info: changing current directory to i2o
> > grub-probe: info: changing current directory to ataraid
> > grub-probe: info: changing current directory to shm
> > grub-probe: info: changing current directory to network
> > grub-probe: info: changing current directory to input
> > grub-probe: info: changing current directory to cciss
> > grub-probe: info: changing current directory to mapper
> > grub-probe: info: changing current directory to ida
> > grub-probe: info: changing current directory to rd
> > grub-probe: info: changing current directory to pts
> > cannot find a GRUB drive for md_d0p1.
My latest commit to GRUB2 CVS should fix this.
Jeroen Dekkers
next prev parent reply other threads:[~2007-05-17 23:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070106165916.GA7895@lapse.madduck.net>
2007-05-04 23:29 ` Bug#381150: still not able to handle partitionable arrays Robert Millan
2007-05-07 19:03 ` Yoshinori K. Okuji
2007-05-07 20:00 ` Robert Millan
2007-05-17 21:25 ` Jeroen Dekkers
2007-05-18 18:37 ` Yoshinori K. Okuji
2007-05-17 23:28 ` Jeroen Dekkers [this message]
2007-05-18 6:32 ` Robert Millan
2007-05-18 7:34 ` Michael Guntsche
2007-05-18 10:56 ` Jeroen Dekkers
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=87fy5vuj1s.wl@dekkers.cx \
--to=jeroen@vrijschrift.org \
--cc=381150-forwarded@bugs.debian.org \
--cc=grub-devel@gnu.org \
--cc=madduck@debian.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.