installer crashed on writing grub.

[Joshua Camp]

Ubuntu 12.04 DVD x64 install. Created a / and /home in btrfs, and a swap with gparted before running installer. I'm wondering if there needs to be a /boot in ext2/3/4. Will try this next.

Installer ran fine until writing grub. A popup notified me writing to grub had failed. It offered to write it to somewhere else, with a default of /sdb, which would have been disastrous as this is my usb flash drive I'm installing from.

Please let me know what other relevant info I can provide.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ubiquity 2.10.16
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu5
Architecture: amd64
CasperVersion: 1.315
Date: Fri Apr 27 01:51:30 2012
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
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)

[Joshua Camp (silvernoose)]

Ok. Rebooting, reformatting with a 200 MB ext2 /boot, and re-running the installer gives the same error. Trying to get it to install grub on /boot or / also quits with a fatal error. Am now going to try rebooting again and letting Ubuntu choose my partition scheme.

[Jean-Baptiste Lallement (jibel)]

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 987418, 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. Please continue to report any other bugs you may find.

[Joshua Camp (silvernoose)]

Letting Ubuntu assign the partitioning scheme was successfu. So I'm hesitantly wondering if btrfs was a/the culprit.