[Bug 1026450] Re: Pangolin installer problem

[stlubuntu]

I also experienced this bug while performing a desktop install using the
32-bit (and 64-bit separately) desktop livecd installers.  Both images
(as they are all now isohybrid) were written to a usb stick (2GB) using
dd.  At the partitioning stage, it asked where to install the MBR and
the default choice was /dev/sdb (which was the usb stick from which it
was being installed.)  /dev/sda was the sole hard drive installed (PATA
drives.)

The expected behavior would be to default to /dev/sda or the first hard
drive and not the usb stick from which it was being installed.

Based on this, does this bug also affect ubiquity since it occurs in the
case of livecd / desktop installs, too?

This is a regression from Ubuntu 10.04 when it did not occur.  If the
user does not catch this, the fresh install is unbootable and drops to a
grub> prompt when attempting to boot.

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

Title:
  Pangolin installer problem

Status in “debian-installer” package in Ubuntu:
  Confirmed

Bug description:
  I'm attempting to install precise pangolin on an HP BL35P blade using
  an ubuntu server x86-64 CD.  HP BL35P blades have broadcomm nics that
  need restricted firmware, which I have placed on a USB key.  The USB
  key must be inserted prior to booting the installer CD or it doesn't
  seem readable.  That in itself is no big deal, however, the USB key
  becomes /dev/sda.  The internal hard disk is assigned to /dev/sdb.

  During installation, the installer lets me choose which drive to
  install the operating system onto.  It shows a selection for the 1GB
  USB key, and the 140GB raid array.  I choose the raid array, and the
  installed files are written there with no difficulty.

  The problem comes when attempting to do the grub installation.  The
  installer defaults to writing the master boot record to /dev/sda,
  which in this case, is the USB stick with the restricted firmware on
  it.  After a couple tries at re-installing I do finally notice the
  issue, but I don't think a novice would see it at all.  Of course, I
  have to override the installer so it will write the MBR to /dev/sdb
  and then the system will boot correctly, and the installer does
  support that cause of action.

  What I expect to happen: The installer should default to writing grub
  to the disk that was chosen for the server install.

  What happened: The installer rather blindly chooses /dev/sda by
  default.

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