Description of problem: After upgrading to Fedora 16 and GRUB2 the boot sequence has become extremely slow. In numbers: (after 4 secs) GRUB Loading (after 1 sec ) Welcome to GRUB! (after 10 secs) error: fd0 read error (after 8 secs) Grub menu Version-Release number of selected component (if applicable): grub2-1.99-12.fc16.x86_64 How reproducible: 100% Steps to Reproduce: 1. Start with a F15 system using /boot on raid1 2. Upgrade to F16, including GRUB2 3. Reboot Actual results: An additional boot delay of 20 seconds. Expected results: Boot sequence without delay Additional info: It may be related to RAID: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/396564 Some info on the disk layout (sda, sdb and sdc all have the same layout): Personalities : [raid6] [raid5] [raid4] [raid1] md0 : active raid1 sda1[0] sdc1[2] sdb1[1] 496896 blocks [3/3] [UUU] md3 : active raid5 sdb5[0] sdc5[2] sda5[1] 146705280 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU] md2 : active raid5 sdb3[0] sdc3[2] sda3[1] 1027968 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU] md1 : active raid5 sdb2[0] sdc2[2] sda2[1] 163846656 blocks level 5, 256k chunk, algorithm 2 [3/3] [UUU] unused devices: <none> [root@home07 ~]# mount /boot mount: /dev/md0 already mounted or /boot busy mount: according to mtab, /dev/md0 is already mounted on /boot [root@home07 ~]# fdisk /dev/sda Command (m for help): p Disk /dev/sda: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xf691f691 Device Boot Start End Blocks Id System /dev/sda1 2048 996029 496991 fd Linux raid autodetect /dev/sda2 996030 164842964 81923467+ fd Linux raid autodetect /dev/sda3 164842965 165871124 514080 fd Linux raid autodetect /dev/sda4 165871125 312576704 73352790 5 Extended /dev/sda5 165871188 312576704 73352758+ fd Linux raid autodetect Command (m for help): q [root@home07 ~]#
*** This bug has been marked as a duplicate of bug 753643 ***