Bug#611537:

[franck hamelin]

same for me:  mdadm + RAID1 => boot fail from the second drive when grub is in graphical mode.
The console mode is an acceptable work around, but it would be nice to avoid it.


here is my configuration:
# uname -a
Linux bigtour 2.6.32-5-amd64 #1 SMP Mon Mar 7 21:35:22 UTC 2011 x86_64 GNU/Linux

# dpkg -l *grub* | grep ii
ii  grub                                 0.97-64                        GRand Unified Bootloader (dummy package)
ii  grub-common                          1.98+20100804-14               GRand Unified Bootloader, version 2 (common files)
ii  grub-pc                              1.98+20100804-14               GRand Unified Bootloader, version 2 (PC/BIOS version)

# cat /proc/mdstat 
Personalities : [raid1] [raid6] [raid5] [raid4] 
md2 : active raid5 sdf[4] sde[2] sdb[1] sdd[0]
      5860538880 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]
      
md1 : active raid1 sda2[2] sdc2[1]
      488133865 blocks super 1.2 [2/2] [UU]
      
md0 : active raid1 sda1[2] sdc1[1]
      248964 blocks super 1.2 [2/2] [UU]

# mount | grep -e boot -e root
/dev/mapper/bigtour-root on / type xfs (rw)
/dev/md0 on /boot type ext2 (rw)

when I boot with a degraded md0 with grub in graphical mode
- with only sda it works
- with only sdc it fails.
when I set GRUB_TERMINAL=console in /etc/default/grub it works in degraded mode with sda only or sdc only.

Fails here means:
GRUB loading.
Welcome to GRUB!

error: fd0 read error. (as usual not the problem)
=> does not switch to the graphical mode it stuck here for ever.


I've check the correct installation of grub on both drive with http://bootinfoscript.sourceforge.net/
You'll find an extract of RESULT.txt here under:

                  Boot Info Script 0.60    from 17 May 2011
============================= Boot Info Summary: ===============================

 => Grub2 (v1.97-1.98) is installed in the MBR of /dev/sda and looks at sector 
    1 of the same hard drive for core.img. core.img is at this location and 
    looks for (md/0)/grub on this drive.
 => No boot loader is installed in the MBR of /dev/sdb.
 => Grub2 (v1.97-1.98) is installed in the MBR of /dev/sdc and looks at sector 
    1 of the same hard drive for core.img. core.img is at this location and 
    looks for (md/0)/grub on this drive.
============================ Drive/Partition Info: =============================

Drive: sda _____________________________________________________________________

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sda1    *             63       498,014       497,952  fd Linux raid autodetect
/dev/sda2             498,015   976,768,064   976,270,050  fd Linux raid autodetect

Drive: sdc _____________________________________________________________________

Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sdc1                  63       498,014       497,952  fd Linux raid autodetect
/dev/sdc2             498,015   976,768,064   976,270,050  fd Linux raid autodetect


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-grub-devel/attachments/20110605/20434e17/attachment.html>