[Bug 1026450] Re: Pangolin installer problem

[Rich Duzenbury]

Thanks for trying to help me.  The installer can certainly _default_ to the
chosen disk particularly if thats the drive where the installer is running
from.  Perhaps warn the user? Or force a choice?

Also this bug report is some years old and seems to now have activity and
I'm not sure why.  I don't know if newer installers have the same issue or
not and I don't have the capability to test them out at this time.

Perhaps it would be best to let this issue die and spend time on more
recent items?

On 3:31pm, Wed, Jan 27, 2016 Phillip Susi <phillsusi at gmail.com> wrote:

> It can't just install to the disk chosen to install Ubuntu to since in a
> dual disk situation, the system still boots from the first disk.  I
> believe the issue of the usb stick being detected as sda instead of the
> first hard disk was fixed some time ago, but precise is ancient and you
> should not be putting into new systems.  Please try with 14.04.
>
>
> ** Changed in: debian-installer (Ubuntu)
>        Status: Confirmed => Incomplete
>
> ** Changed in: ubiquity (Ubuntu)
>        Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1026450
>
> Title:
>   Pangolin installer problem
>
> Status in debian-installer package in Ubuntu:
>   Incomplete
> Status in ubiquity package in Ubuntu:
>   Incomplete
>
> 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
>

-- 
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:
  Incomplete
Status in ubiquity package in Ubuntu:
  Incomplete

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