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

[John Hughes]

Package: grub-pc
Version: 1.99-14
Severity: important
Tags: d-i

Dear Maintainer,

* What led up to the situation?

I tried to install wheezy on a Sony Vaio Z2 which has a raid0 disk

* What exactly did you do (or not do) that was effective (or
ineffective)?

Tried to install grub

* What was the outcome of this action?

grub-install on /dev/md126 (the raid0) fails:

/usr/sbin/grub-probe: error: no such disk /dev/md126p5

* What outcome did you expect instead

Since /dev/md126p5 is /boot I expected grub to install


grub-install suggests the output of grub-probe -v might be interesting. Here it is:
# /usr/sbin/grub-install /dev/md126
/usr/sbin/grub-probe: error: no such disk.
Auto-detection of a filesystem of /dev/md126p5 failed.
Try with --recheck.
If the problem persists please report this together with the output of "/usr/sbin/grub-probe --device-map="/boot/grub/device.map" --target=fs -v /boot/grub" to <bug-...@gnu.org>
# /usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v /boot/grub
/usr/sbin/grub-probe: info: Scanning for dmraid_nv RAID devices on disk hd0.
/usr/sbin/grub-probe: info: the size of hd0 is 250069680.
/usr/sbin/grub-probe: info: the size of hd0 is 250069680.
/usr/sbin/grub-probe: info: Scanning for dmraid_nv RAID devices on disk hd1.
/usr/sbin/grub-probe: info: the size of hd1 is 250069680.
/usr/sbin/grub-probe: info: the size of hd1 is 250069680.
/usr/sbin/grub-probe: info: scanning hd0 for LVM.
/usr/sbin/grub-probe: info: the size of hd0 is 250069680.
/usr/sbin/grub-probe: info: no LVM signature found.
/usr/sbin/grub-probe: info: the size of hd0 is 250069680.
/usr/sbin/grub-probe: info: scanning hd1 for LVM.
/usr/sbin/grub-probe: info: the size of hd1 is 250069680.
/usr/sbin/grub-probe: info: no LVM signature found.
/usr/sbin/grub-probe: info: the size of hd1 is 250069680.
/usr/sbin/grub-probe: info: Scanning for mdraid09 RAID devices on disk hd0.
/usr/sbin/grub-probe: info: the size of hd0 is 250069680.
/usr/sbin/grub-probe: info: the size of hd0 is 250069680.
/usr/sbin/grub-probe: info: Scanning for mdraid09 RAID devices on disk hd1.
/usr/sbin/grub-probe: info: the size of hd1 is 250069680.
/usr/sbin/grub-probe: info: the size of hd1 is 250069680.
/usr/sbin/grub-probe: info: Scanning for mdraid1x RAID devices on disk hd0.
/usr/sbin/grub-probe: info: the size of hd0 is 250069680.
/usr/sbin/grub-probe: info: the size of hd0 is 250069680.
/usr/sbin/grub-probe: info: Scanning for mdraid1x RAID devices on disk hd1.
/usr/sbin/grub-probe: info: the size of hd1 is 250069680.
/usr/sbin/grub-probe: info: the size of hd1 is 250069680.
/usr/sbin/grub-probe: info: Scanning for mdraid09 RAID devices on disk hd0.
/usr/sbin/grub-probe: info: the size of hd0 is 250069680.
/usr/sbin/grub-probe: info: the size of hd0 is 250069680.
/usr/sbin/grub-probe: info: Scanning for mdraid09 RAID devices on disk hd0,msdos3.
/usr/sbin/grub-probe: info: the size of hd0 is 250069680.
/usr/sbin/grub-probe: info: Scanning for mdraid09 RAID devices on disk hd0,msdos2.
/usr/sbin/grub-probe: info: the size of hd0 is 250069680.
/usr/sbin/grub-probe: info: Scanning for mdraid09 RAID devices on disk hd0,msdos1.
/usr/sbin/grub-probe: info: the size of hd0 is 250069680.
/usr/sbin/grub-probe: info: Scanning for mdraid09 RAID devices on disk hd1.
/usr/sbin/grub-probe: info: the size of hd1 is 250069680.
/usr/sbin/grub-probe: info: the size of hd1 is 250069680.
/usr/sbin/grub-probe: info: Scanning for mdraid1x RAID devices on disk hd0.
/usr/sbin/grub-probe: info: the size of hd0 is 250069680.
/usr/sbin/grub-probe: info: the size of hd0 is 250069680.
/usr/sbin/grub-probe: info: Scanning for mdraid1x RAID devices on disk hd0,msdos3.
/usr/sbin/grub-probe: info: the size of hd0 is 250069680.
/usr/sbin/grub-probe: info: Scanning for mdraid1x RAID devices on disk hd0,msdos2.
/usr/sbin/grub-probe: info: the size of hd0 is 250069680.
/usr/sbin/grub-probe: info: Scanning for mdraid1x RAID devices on disk hd0,msdos1.
/usr/sbin/grub-probe: info: the size of hd0 is 250069680.
/usr/sbin/grub-probe: info: Scanning for mdraid1x RAID devices on disk hd1.
/usr/sbin/grub-probe: info: the size of hd1 is 250069680.
/usr/sbin/grub-probe: info: the size of hd1 is 250069680.
/usr/sbin/grub-probe: info: scanning hd0 for LVM.
/usr/sbin/grub-probe: info: the size of hd0 is 250069680.
/usr/sbin/grub-probe: info: no LVM signature found.
/usr/sbin/grub-probe: info: the size of hd0 is 250069680.
/usr/sbin/grub-probe: info: scanning hd0,msdos3 for LVM.
/usr/sbin/grub-probe: info: the size of hd0 is 250069680.
/usr/sbin/grub-probe: info: no LVM signature found.
/usr/sbin/grub-probe: info: scanning hd0,msdos2 for LVM.
/usr/sbin/grub-probe: info: the size of hd0 is 250069680.
/usr/sbin/grub-probe: info: no LVM signature found.
/usr/sbin/grub-probe: info: scanning hd0,msdos1 for LVM.
/usr/sbin/grub-probe: info: the size of hd0 is 250069680.
/usr/sbin/grub-probe: info: no LVM signature found.
/usr/sbin/grub-probe: info: scanning hd1 for LVM.
/usr/sbin/grub-probe: info: the size of hd1 is 250069680.
/usr/sbin/grub-probe: info: no LVM signature found.
/usr/sbin/grub-probe: info: the size of hd1 is 250069680.
/usr/sbin/grub-probe: info: changing current directory to /dev.
/usr/sbin/grub-probe: info: changing current directory to mapper.
/usr/sbin/grub-probe: info: opening md126,5.
/usr/sbin/grub-probe: error: no such disk.

# ls /dev/md126p5
brw-rw-rw- 1 root root 259, 4 Feb 10 22:55 /dev/md126p5
# mount
/dev/md126p7 on / type ext3 (rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=ordered)
/dev/md126p5 on /boot type ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=1,data=ordered)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)

-- Package-specific info:

*********************** BEGIN /boot/grub/device.map
(hd0) /dev/disk/by-id/ata-SAMSUNG_MZRPC256HADR-000SO_S0T5NY0BA01617
(hd1) /dev/disk/by-id/ata-SAMSUNG_MZRPC256HADR-000SO_S0T5NY5BA01617
*********************** END /boot/grub/device.map

*********************** BEGIN /proc/mdstat
cat: /proc/mdstat: No such file or directory
*********************** END /proc/mdstat

*********************** BEGIN /dev/disk/by-id
total 0
lrwxrwxrwx 1 root root 9 Feb 10 22:42 ata-Optiarc_DVD_RW_AD-7690H -> ../../sr0
lrwxrwxrwx 1 root root 9 Feb 10 22:55 ata-SAMSUNG_MZRPC256HADR-000SO_S0T5NY0BA01617 -> ../../sda
lrwxrwxrwx 1 root root 9 Feb 10 22:42 ata-SAMSUNG_MZRPC256HADR-000SO_S0T5NY5BA01617 -> ../../sdb
lrwxrwxrwx 1 root root 11 Feb 10 22:42 md-uuid-4a056b95:1ce7c03b:3eb58093:215240fe -> ../../md127
lrwxrwxrwx 1 root root 11 Feb 10 22:44 md-uuid-e32e0439:7c03631e:a6ee5474:aed5fb87 -> ../../md126
lrwxrwxrwx 1 root root 13 Feb 10 22:44 md-uuid-e32e0439:7c03631e:a6ee5474:aed5fb87-part1 -> ../../md126p1
lrwxrwxrwx 1 root root 13 Feb 10 22:42 md-uuid-e32e0439:7c03631e:a6ee5474:aed5fb87-part2 -> ../../md126p2
lrwxrwxrwx 1 root root 13 Feb 10 22:42 md-uuid-e32e0439:7c03631e:a6ee5474:aed5fb87-part3 -> ../../md126p3
lrwxrwxrwx 1 root root 13 Feb 10 22:42 md-uuid-e32e0439:7c03631e:a6ee5474:aed5fb87-part4 -> ../../md126p4
lrwxrwxrwx 1 root root 13 Feb 10 22:55 md-uuid-e32e0439:7c03631e:a6ee5474:aed5fb87-part5 -> ../../md126p5
lrwxrwxrwx 1 root root 13 Feb 10 22:42 md-uuid-e32e0439:7c03631e:a6ee5474:aed5fb87-part6 -> ../../md126p6
lrwxrwxrwx 1 root root 13 Feb 10 22:44 md-uuid-e32e0439:7c03631e:a6ee5474:aed5fb87-part7 -> ../../md126p7
lrwxrwxrwx 1 root root 9 Feb 10 22:55 scsi-SATA_SAMSUNG_MZRPC25S0T5NY0BA01617 -> ../../sda
lrwxrwxrwx 1 root root 9 Feb 10 22:42 scsi-SATA_SAMSUNG_MZRPC25S0T5NY5BA01617 -> ../../sdb
lrwxrwxrwx 1 root root 9 Feb 10 22:55 wwn-0x50000f0043584d30 -> ../../sda
*********************** END /dev/disk/by-id

*********************** BEGIN /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 13 Feb 10 22:55 099708d3-6792-45a9-b7be-280e2b46d545 -> ../../md126p5
lrwxrwxrwx 1 root root 13 Feb 10 22:42 13f3e907-bfbe-497c-b0cf-975f927005f3 -> ../../md126p6
lrwxrwxrwx 1 root root 13 Feb 10 22:42 5066444266442AD4 -> ../../md126p3
lrwxrwxrwx 1 root root 13 Feb 10 22:44 7e7b48bc-ab09-4998-a0dc-961ba6c801f4 -> ../../md126p7
lrwxrwxrwx 1 root root 13 Feb 10 22:42 88C043A6C0439978 -> ../../md126p2
lrwxrwxrwx 1 root root 13 Feb 10 22:44 FC903F88903F4902 -> ../../md126p1
*********************** END /dev/disk/by-uuid

-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-1-amd64
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages grub-pc depends on:
ii debconf [debconf-2.0] 1.5.41
ii grub-common 1.99-14
ii grub-pc-bin 1.99-14
ii grub2-common 1.99-14
ii ucf 3.0025+nmu2

grub-pc recommends no packages.

grub-pc suggests no packages.

-- debconf information:
grub-pc/kopt_extracted: false
grub2/kfreebsd_cmdline:
grub2/device_map_regenerated:
* grub-pc/install_devices:
grub-pc/postrm_purge_boot_grub: false
grub-pc/install_devices_failed_upgrade: true
grub-pc/disk_description:
* grub2/linux_cmdline:
* grub-pc/install_devices_empty: true
grub2/kfreebsd_cmdline_default: quiet
grub-pc/partition_description:
grub-pc/install_devices_failed: false
grub-pc/install_devices_disks_changed:
* grub2/linux_cmdline_default: quiet
grub-pc/chainload_from_menu.lst: true
grub-pc/mixed_legacy_and_grub2: true



--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

[Vladimir 'φ-coder/phcoder' Serbinenko]

On 11.02.2012 11:14, John Hughes wrote:
> Package: grub-pc
> Version: 1.99-14
> Severity: important
> Tags: d-i
>
> Dear Maintainer,
>
> * What led up to the situation?
>
> I tried to install wheezy on a Sony Vaio Z2 which has a raid0 disk
>
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
>
> Tried to install grub
>
> * What was the outcome of this action?
>
> grub-install on /dev/md126 (the raid0) fails:
>
> /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.

> _______________________________________________
> Pkg-grub-devel mailing list
> Pkg-gru...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grub-devel
>


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

[John Hughes]

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.

I'll try adding it to the map by hand.

Which seems to work.

[Vladimir 'φ-coder/phcoder' Serbinenko]

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

[John Hughes]

On 11/02/12 12:02, John Hughes wrote:
> On 11/02/12 11:29, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>> 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.
>
> I'll try adding it to the map by hand.

Ok, adding

(hd2) /dev/md126

to target/boot/grub/device.map then re-running the grub-install works
(it didn't find the windows install, but doing an update-grub from the
running system fixed that).

Like you I get the feeling that the source of the problem is that it's a
mdadm raid using intel container format (aka fake raid). grub looks
like it's trying to cope with either the old dmraid, or linux raid being
handled by mdadm, but this case is beyond it's abilities.

Would you like me to try debugging this further?

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

[Vladimir 'φ-coder/phcoder' Serbinenko]

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.

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

[johnwinery]

Greeting ,I had written an earlier mail to you but without response