[Bug 1223435] Re: Grub fails to boot linux after install on dual boot with RAID+LVM

[cwsupport]

I have managed to get a system working.

Having rebooted using the install disk to 'Rescue Broken System'. Copied
out the /boot to a temp dir, remade the /boot filesystem as ext2
(instead of ext4) and then restoring the /boot data. I then executed:

update-grub
grub-install /dev/sda
grub-install /dev/sdb
grub-install /dev/sdc

On reboot I saw the menu and everything works. Will investigate further.
But I see little reason why this should have not worked initially but
worked on re-running. As I understand it ext4 is supported as a /boot
o/s on RAID using the built in ext2 module?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1223435

Title:
  Grub fails to boot linux after install on dual boot with RAID+LVM

Status in “grub2” package in Ubuntu:
  New

Bug description:
  Ive just been trying out new installs on a PC which was running
  Kubuntu 12.04.3 LTS (upgraded from Beta1). The 12.04 Beta 1 installed
  perfectly on this system and has been working for a long time.
  Essentially the system is fine so we can rule out related issues.

  Trying to install all of the following:

  Ubuntu Server 13.04
  Ubuntu Server 13.10 daily current

  Everything is fine, disk partitioning, RAID, LVM etc then grub fails
  on reboot and drops to grub rescue after "error: no such disk". Ive
  been unable to make a successful boot from the command line.

  Essentially the system has 3 disks.

  sda - 250GB seagate - Multiple partitions containing multi-boot Windows Vista64 bit and Windows XP 32bit.
  sdb - 500GB seagate - see below.
  sdc - 500GB seagate - see below.

  Both sdb/sdc are configured as 2 partitions 1GB and 499GB forming two
  raid sets

  md0 - 1GB for /boot
  md1 - 499GB for LVM

  The LVM has partitions for /, /home, /tmp and swap amongst others.

  I have tried with the partitions using both ext4 and resiserfs and the
  result is the same - fails to boot and goes into grub rescue.

  grub is referencing the drives as (muuid/blah).
  In grub resuce ls shows (md/0) and (md/1) along with the various hd bits for each of the drives and partitions.

  It should have booted without problem - it appears to be unable to
  find /boot properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1223435/+subscriptions