Unable to install grub on /dev/sda9 during 12.04 beta1 installation with btrfs

[John.Zhong]

Unable to install grub on /dev/sda9 during 12.04 beta1 installation with btrfs

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ubiquity 2.9.23
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
CasperVersion: 1.305
Date: Sat Mar 3 16:24:54 2012
InstallCmdLine: boot=casper iso-scan/filename=/ubuntu-12.04-beta1-desktop-amd64.iso ro quiet splash
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
ProcEnviron:
 TERM=unknown
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

[Gary M (garym)]

Mar 3 08:22:24 ubuntu grub-installer: info: Installing grub on '/dev/sda9'
Mar 3 08:22:24 ubuntu grub-installer: info: grub-install supports --no-floppy
Mar 3 08:22:24 ubuntu grub-installer: info: Running chroot /target grub-install --no-floppy --force "/dev/sda9"
Mar 3 08:22:26 ubuntu grub-installer: /usr/sbin/grub-setup: warn: Attempting to install GRUB to a partitionless disk or to a partition. This is a BAD idea..
Mar 3 08:22:26 ubuntu grub-installer: /usr/sbin/grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..
Mar 3 08:22:31 ubuntu grub-installer: /usr/sbin/grub-setup: error: cannot read `/@/boot/grub/core.img' correctly.
Mar 3 08:22:31 ubuntu grub-installer: error: Running 'grub-install --no-floppy --force "/dev/sda9"' failed.

[Gary M (garym)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 879109, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.