From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: John Hughes <john@calvaedi.com>
Cc: The development of GRUB 2 <grub-devel@gnu.org>,
John Hughes <john@calva.com>,
659460@bugs.debian.org
Subject: Re: Bug#659460: grub-pc: grub-install can't install on raid0 device (grub-probe can't find /boot)
Date: Sat, 11 Feb 2012 12:19:48 +0100 [thread overview]
Message-ID: <4F364ED4.2000402@gmail.com> (raw)
In-Reply-To: <4F364ABC.6050806@calvaedi.com>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
On 11.02.2012 12:02, John Hughes wrote:
> On 11/02/12 11:29, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>> On 11.02.2012 11:14, John Hughes wrote:
>>> Package: grub-pc
>>> Version: 1.99-14
>>> Severity: important
>>> Tags: d-i
>>>
>>>
>>> /usr/sbin/grub-probe: error: no such disk /dev/md126p5
>> This looks like fakeraid rather than a honest software raid. You need to
>> manually add it to device.map.
>
> The difference is rather blurred now that it's mdadm that's handling
> it rather than the old dm-raid.
>
This is exactly the problem. GRUB can't distinguish between the both. Do
you know an ioctl, or at very least a command to distinguish them?
Also honest raid doesn't try to scam you into believing that it's a
hardware raid.
> I'll try adding it to the map by hand.
>
> Which seems to work.
>
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next parent reply other threads:[~2012-02-11 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120211101400.32649.13427.reportbug@debian>
[not found] ` <4F3642FF.1080205@gmail.com>
[not found] ` <4F364ABC.6050806@calvaedi.com>
2012-02-11 11:19 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2012-02-11 11:36 ` Bug#659460: grub-pc: grub-install can't install on raid0 device (grub-probe can't find /boot) John Hughes
2012-02-11 12:15 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-02-13 16:18 ` Phillip Susi
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=4F364ED4.2000402@gmail.com \
--to=phcoder@gmail.com \
--cc=659460@bugs.debian.org \
--cc=grub-devel@gnu.org \
--cc=john@calva.com \
--cc=john@calvaedi.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.