12.04.1 installation crash as updating grub to sda12 the same ISO was used for live usb with no problems

[aimwin]

After download 12.04.1 I use in Live USB installed 2 times.
now I test with same iso image, but burn to DVD and this is the first "Live" then installation.
I will try again after this report, both usb and Dvd go into "Live" mode(try Ubuntu) first before order installation.
will give feed back

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ubiquity 2.10.18
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21
Uname: Linux 3.2.0-27-generic-pae i686
ApportVersion: 2.0.1-0ubuntu11
Architecture: i386
CasperVersion: 1.315
Date: Tue Jul 31 00:48:02 2012
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --
LiveMediaBuild: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120727)
ProcEnviron:
 LANGUAGE=en_AU.UTF-8
 TERM=unknown
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

[aimwin (aim-mail)]

I have execute Check Disk for Error before installation.
No error on the DVD report.

[aimwin (aim-mail)]

This bug report was done by autoreport during installation Live DVD crash.
I have the same crash but installed by Live USB.
The link is https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1030772

I think I identified the condition.
Which is I choose btrf file system instead of ext4 at the installation instruction.

Please look at details at bug report in the above link.

I test reinstall Ubuntu 12.04.1 with the same DVD and choose ext4 to the same partition sda12,
with 100% positive success.

[aimwin (aim-mail)]

Also more on installation of btrf.
http://ubuntuforums.org/showpost.php?p=8716089&postcount=1

[aimwin (aim-mail)]

Any one help on this report please do so at

The link is https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1030772

ADMIN please see if I should close this bug report?

[Launchpad Janitor (janitor)]

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