[Bug 1059158] Re: ubiquity fails with "grub-efi package failed to install to /target/"

melchiaros melchiaros at aol.com
Sun Sep 30 17:28:21 UTC 2012

*** This bug is a duplicate of bug 965213 ***

There seems to be the main problem with sda5:

Sep 30 16:32:12 kubuntu kernel: [ 1383.927719] end_request: I/O error, dev sda, sector 514392064
Sep 30 16:32:12 kubuntu kernel: [ 1383.927734] EXT4-fs error (device sda5): ext4_wait_block_bitmap:447: comm install.py: Cannot read block bitmap - block_group = 96, block_bitmap = 3145728
Sep 30 16:32:12 kubuntu kernel: [ 1383.927735] ata1: EH complete
Sep 30 16:32:18 kubuntu kernel: [ 1389.396564] Aborting journal on device sda5-8.
Sep 30 16:32:23 kubuntu kernel: [ 1394.917899] EXT4-fs (sda5): Remounting filesystem read-only
Sep 30 16:32:36 kubuntu kernel: [ 1408.238185] EXT4-fs error (device sda5) in ext4_reserve_inode_write:4476: Journal has aborted
Sep 30 16:32:42 kubuntu kernel: [ 1413.598471] EXT4-fs error (device sda5) in ext4_evict_inode:238: Journal has aborted

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

  ubiquity fails with "grub-efi package failed to install to /target/"

Status in “ubiquity” package in Ubuntu:

Bug description:
  This is on a Mac Mini 5,1 (2011), running the Kubuntu 12.10 live USB
  which was booted via rEFIt.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: ubiquity 2.12.6 [modified: lib/partman/automatically_partition/question]
  ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.3-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.325
  Date: Sun Sep 30 12:33:21 2012
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity quiet splash --
  LiveMediaBuild: Kubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120928)
   PATH=(custom, no user)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list