[Bug 1045178] Re: grub-install failed - "/usr/share/ubiquity/plugininstall.py", line 1724, in <module>

Johann Popper jpopper7 at gmail.com
Sun Sep 16 01:50:44 UTC 2012

Bug #1050590 is marked as duplicate of this bug. Are you sure this is
the case? I see nothing here to indicate the following issue described
in Bug #1050590:

["'grub-efi' package failed to install into /target/. Without the GRUB boot loader, the installed system will not boot." 

This exact error occurs on a Lenovo B570 while attempting to install
UBuntu 12.10 daily builds, hence the special documentation for
installing Ubuntu on Lenovo B570s with instructions for overriding grub-
efi with 64-bit installations in order to boot after installation (the
B570 uses MBR, not GPT) no longer works, since grub-efi-amd64 will not
even install in the first place, for whatever reason.

This really ought to be dealt with before release. It's a show-stopping
bug for affected hardware (at least some ASUS and Lenovo).]

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.

  grub-install failed - "/usr/share/ubiquity/plugininstall.py", line
  1724, in <module>

Status in “grub-installer” package in Ubuntu:
Status in “grub2” package in Ubuntu:
Status in “ubiquity” package in Ubuntu:

Bug description:
  Grub install failed at clean install. core.img too large to fit into
  64 sectors ( 32Kb )

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: ubiquity 2.11.18
  ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
  Uname: Linux 3.5.0-6-generic i686
  ApportVersion: 2.4-0ubuntu5
  Architecture: i386
  CasperVersion: 1.320
  Date: Mon Sep  3 07:48:03 2012
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
  LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120724.2)
   PATH=(custom, no user)
  SourcePackage: grub-installer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list