Re: Bug#659460: grub-pc: grub-install can't install on raid0 device (grub-probe can't find /boot)

Re: Bug#659460: grub-pc: grub-install can't install on raid0 device (grub-probe can't find /boot)

[Vladimir 'φ-coder/phcoder' Serbinenko]

[-- 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 --]

Re: Bug#659460: grub-pc: grub-install can't install on raid0 device (grub-probe can't find /boot)

[John Hughes]

On 11/02/12 12:19, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> On 11.02.2012 12:02, John Hughes wrote:
>>
>> 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.

What scam?  As far as I can tell it's just a mdadm raid with an intel 
container format rather than a mdadm container format.

Re: Bug#659460: grub-pc: grub-install can't install on raid0 device (grub-probe can't find /boot)

[Vladimir 'φ-coder/phcoder' Serbinenko]

[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]

On 11.02.2012 12:36, John Hughes wrote:
> On 11/02/12 12:19, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>> On 11.02.2012 12:02, John Hughes wrote:
>>>
>>> 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.
>
> What scam?  As far as I can tell it's just a mdadm raid with an intel
> container format rather than a mdadm container format.
>
Adding BIOS driver for this screws things up.
And the scam is adding this to mobo features as a "RAID" and an attempt
to make this pass as if it was a hardware RAID.
GRUB currently considers mdX as a non-available through BIOS unless user
overrides it in device.map, we need to add a logic to handle the
fakeraid as a BIOS disk.
It's possible to add support for intel RAID but it will be useless since
the member disks aren't available through BIOS to begin with.
>
>


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



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

Re: Bug#659460: grub-pc: grub-install can't install on raid0 device (grub-probe can't find /boot)

[Phillip Susi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2/11/2012 7:15 AM, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> Adding BIOS driver for this screws things up. And the scam is
> adding this to mobo features as a "RAID" and an attempt to make
> this pass as if it was a hardware RAID. GRUB currently considers
> mdX as a non-available through BIOS unless user overrides it in
> device.map, we need to add a logic to handle the fakeraid as a BIOS
> disk. It's possible to add support for intel RAID but it will be
> useless since the member disks aren't available through BIOS to
> begin with.

I started a cross mailing list discussion of this last year, and I
think the conclusion was that grub needs to ask mdadm what the
metadata format is, and if it is the intel format, assume the raid is
bios accessible the way it currently does for dmraid.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPOTfxAAoJEJrBOlT6nu75giwIAIepAzVB43PV2Ix4i02cQie6
sy3MK9uqjHkLX75XPCDB68Tyfejb9KenBxEjJqZmVt3m9flK5dIbcLRe8baMvVuZ
pu2uMZ9dLc+WVVrQ3Jwd5eJfy13wRgo5bKiBvgnUVta+6DKtFCR5en9DWzmgBjWg
qF88ClnG7iNjZ4wpqMkcubcBA5/lGPP69Z7ohCtQ2a4vcmBWpmyPmu4dcnyaM8OY
CviSULB/nCyMs9cCCYx8IPiOdsEiB1jGaxL8Dab7oJzNTN3PDb+7Z7rUJCKK5nxS
L3SCQYPGe8zSun6GCCObMkZ0O9AFMRpXFnMSVLcFVoklXnEP4MUzPuAWH/oQBlY=
=mFNd
-----END PGP SIGNATURE-----