Regression (from 9.10) LVM /boot MBR install /usr/sbin/grub-probe: error: no mapping exists for `lin-boot' - Lucid (10.04) netinstall (20100220)

Still doesn't work with 20100224.

Getting the same error when installing Lucid Alpha 3 Server amd64 using a cd image downloaded 2010-03-16 on a server with the root/boot filesystem on a RAID 1 setup using software raid.

After 3 unsucessfull attempts, I let the installation "Continue without installing the boot loader". I then rebooted to the install CD again, and chose rescue mode so I could get a shell. When I got to the shell, I tried to run grub-install --no-floppy --force /dev/sda, and got an error saying the filesystem (ext3 in my case) does not support UUIDs. Did some research, and apparently, installation should have chosen to install the old grub version instead of grub2.

So, using aptitude, I removed (purged) the grub-pc and grub-common packages, installed grub (and all uninstalled required dependencies), ran grub-install, then ran update-grub.

I'm now able to boot the system properly.

The intent is definitely to use GRUB 2, but it's not quite entirely
working yet. I have a patch which should address this, which I intend
to land for beta-2 after some testing.

This bug was fixed in the package grub2 - 1.98-1ubuntu2

---------------
grub2 (1.98-1ubuntu2) lucid; urgency=low

  * Fix LVM/RAID probing in the absence of /boot/grub/device.map
    (LP: #525085, #527401).
  * Backport my upstream patch to copy .mo files from /usr/share/locale to
    match where 'make install' puts them (LP: #537998).
  * Look for .mo files in /usr/share/locale-langpack as well, in preference
    (LP: #537998).
  * Don't generate /boot/grub/device.map during grub-mkconfig (we already
    suppressed it during grub-install, but then grub-mkconfig generated it
    shortly afterwards, producing confusing results).
  * Don't run /etc/grub.d/README, even if it somehow ended up being
    executable (LP: #537123).
 -- Colin Watson <email address hidden> Mon, 22 Mar 2010 19:57:10 +0000