grub-efi-amd64 picks wrong UUID for root fs when using RAID and LVM

[Beastyvoid]

When installing a system with RAID 1 on two disks on a EFI computer, Ubuntu installs grub-efi-amd64 instead of grub-pc. This should be the correct behaviour, but at the end of the installation, the system in unbootable.

For info, Debian testing Wheezy, nightly build of yesterday (sep 5 2011) is working, because it doesn't install grub-efi-amd64 but sticks to grub-pc

I've testing with two identical drives in mirror, first with a GPT label, then with a MSDOS label. The result is the same, system not bootable.

I have tested with Ubuntu AMD64 11.10 Beta 1, and 11.04. The result is the same with both releases.

I would like to see a true UEFI disto being able to install with all functionnalities : RAID, LVM, UEFI, GPT, but there is still some work.

The system is a brand new HP Ellite 8200 CMT (Core i7, 4G RAM).

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Franck (alci)]

I think the bug is still present in 13.04 as well as in 13.10 beta.
I manged to get things working, and found the source of the problem: the search.fs_uuid set in EFI/ubuntu/grub.cfg on the UEFI system partition is not correct, as it does not relate to the root fs.

So I had to boot from a rescue disk, open a shell on my target root filesystem, get its UUID with bkid, mount /boot/efi and edit grub.gcf with the right UUID. After that, things worked.
I also used dd to clone the ESP on the second disk of the raid to be able to boot in case one of them fails...

So I think the bug is when picking the UUID of the root fs when generating the /boot/efi/EFI/ubuntu/grub.cfg file.