[Bug 851704] Re: GRUB reports error after successful installation (Alternate)

[Colin Watson]

grub-installer (1.68ubuntu1) oneiric; urgency=low

  * Resynchronise with Debian (preseeding change in 1.68 fixes LP: #857548).
    Remaining changes:
    - Show the grub menu and raise the menu timeout if other operating
      systems are installed (only for GRUB Legacy right now).
    - Remove splash boot parameter unless debian-installer/framebuffer=true
      and debian-installer/splash=true.
    - If / or /boot are on a removable device, install GRUB there by
      default.
    - Only mount /target/proc if it isn't already mounted.
    - Support setting OVERRIDE_UNSUPPORTED_OS in the environment to force
      grub-installer to use its default MBR selection method despite there
      being unsupported operating systems on the disk.
    - Support grub-installer/bootdev_directory preseeding to make use of the
      relative path feature of grub4dos, so that we can point grub4dos at
      part of a disk for Wubi. Setting this disables normal grub
      installation, but still generates a device.map (for GRUB Legacy only);
      it also hides the menu.
    - Handle cases where /boot is bind-mounted.
    - Add support for writing an GRUB Legacy MBR on each disk in an
      mdadm-managed RAID providing /boot. (GRUB 2 can handle this already.)
    - Properly make use of output from os-prober to configure the booting of
      other operating systems on dmraid arrays. Attempt to guess where in
      the device map the array belongs, by substituting the first drive in
      the dmraid array for the dmraid array device node itself, and removing
      any reference to other member disks of the array.
    - Go back to using update-grub -y for GRUB Legacy for now; our grub
      package is a bit old and still requires this.
    - Default to grub2 for GPT systems.
    - Allow grub/grub2 choice for ext4, though still default to grub2.
    - If /boot is on an MD device and we're using GRUB 2, install GRUB there
      rather than (hd0); GRUB 2 will interpret that as meaning that it needs
      to install to each of the RAID members.
    - If using GRUB 2 and installing to a RAID device any of whose
      components are partitions, then default to installing to the MBRs of
      each of the containing disks, since GRUB 2 will refuse to install to
      the partition devices.
    - On i386/efi and amd64/efi subarchitectures, install grub-efi and purge
      grub, grub-legacy, and grub-pc; elsewhere, purge grub-efi*.
    - Add a preseedable grub-installer/timeout template to adjust the
      initial GRUB timeout.
    - Install GRUB to the SATA RAID or multipath device when /boot is on
      such a device, rather than installing to the first hard disk.
    - Remove grub-gfxpayload-lists in situations where we need to remove
      grub-pc.
    - Remove 'quiet' from target system command line if
      debian-installer/quiet is set to false.
    - When /boot is on a loopback device (i.e. Wubi), install GRUB there.
  * Simplify /proc and /sys mounting; make sure they're consistently mounted
    for the entire life of grub-installer, and consistently unmounted on
    exit (LP: #851704).

 -- Colin Watson <cjwatson at ubuntu.com>  Fri, 23 Sep 2011 21:29:13 +0100

** Changed in: grub-installer (Ubuntu Oneiric)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub-installer in Ubuntu.
https://bugs.launchpad.net/bugs/851704

Title:
  GRUB reports error after successful installation (Alternate)

Status in “grub-installer” package in Ubuntu:
  Fix Released
Status in “grub-installer” source package in Oneiric:
  Fix Released

Bug description:
  I'm using Kubuntu Oneiric Daily amd64 alternate iso for installation,
  date of 15. Sep.

  Partitioning setup is complex:

  /dev/sda1 -> /boot for Kubuntu 11.04
  /dev/sda2 -> /boot for (to be installed) Kubuntu 11.10
  /dev/sda3 -> Extended partition
  /dev/sda5 -> Crypto partition (LUKS)

  /dev/mapper/sda5_crypt -> LVM PV, only PV in VG system

  /dev/mapper/system-root1 -> / for Kubuntu 11.04
  /dev/mapper/system-root2 -> / for (to be installed) Kubuntu 11.10
  /dev/mapper/system-swap -> Swap partition for any Linux 
  /dev/mapper/system-home -> /home for any Linux

  Crypt partition and LVM are already set up by Kubuntu 11.04. During
  installation of Kubuntu 11.10, the crypt-partition in /dev/sda5 gets
  activated and every partition gets listed.  Installation works until
  GRUB installation.

  The installer identifies Kubuntu 11.04 as already installed and
  suggests to install GRUB into the MBR. Following that suggestion, the
  installer runs "grub-install /dev/sda", then "update-grub". Then the
  installer shows a red error screen, indicating that some process
  during GRUB installation ended with exit code 1. Retrying leads to the
  same result. Choosing "Continue without boot loader installation" from
  the main menu concludes the installation.

  After reboot, GRUB reports as version "1.99-12ubuntu3" (from Kubuntu 11.10) and offers to boot Kubuntu 11.10 (Linux 3.0.0-11-generic) as well as Kubuntu 11.04 (Linux 2.6.38-11-generic).
   
  So from my point of view, GRUB installs correctly and reports a false negative. Actually, this error is older and occurred in Natty (Maverick?) too, but I didn't bother to report it as I had to use some workarounds (cryptsetup, lvchange, ...) from a console to activate the existiting partitions without data loss.  With bug 420080 now resolved, this should be fixed too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/851704/+subscriptions