Installer ignores boot loader device

[Nick Booker]

Binary package hint: ubiquity

I specified an alternative device manually (/dev/sda12 which is the root partition I installed Ubuntu to) for the GRUB boot loader in the Advanced dialogue, however the installer installed GRUB to /dev/sda.

This may be related in some way to #525029 I reported earlier, but isn't exactly the same problem.

Booting into the newly-installed Lucid and manually installing with grub-install worked, however I need to use the --force option. I've attached a transcript of my shell session for doing that.
EDIT: Despite the warnings, I can then chainload to /dev/sda12 from another GRUB installation and boot Lucid via its own GRUB with no problems.

ProblemType: Bug
Architecture: i386
Date: Sat Feb 20 20:45:45 2010
DistroRelease: Ubuntu 10.04
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100220)
Package: ubiquity 2.1.22
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
SourcePackage: ubiquity
Uname: Linux 2.6.32-13-generic i686

[Colin Watson (cjwatson)]

This doesn't look like a syslog file from a completed installation run; it only goes up to language selection, right at the start of the installer.

Any chance you could reproduce this with ubiquity in debug mode? You can do this by running 'ubiquity -d' in a terminal window; once the installation has completed, we need /var/log/syslog, /var/log/partman, and /var/log/installer/debug. Thanks in advance.

[Nick Booker (nmbooker)]

I ran apport-bug ubiquity from the installer disc, to get the right
version info etc, because I don't know if there are side-effects of
installing ubiquity in an installed environment.

Do you want me to collect some info from the installed environment?

On 22 February 2010 23:52, Colin Watson <email address hidden> wrote:
> This doesn't look like a syslog file from a completed installation run;
> it only goes up to language selection, right at the start of the
> installer.
>
> Any chance you could reproduce this with ubiquity in debug mode?  You
> can do this by running 'ubiquity -d' in a terminal window; once the
> installation has completed, we need /var/log/syslog, /var/log/partman,
> and /var/log/installer/debug.  Thanks in advance.
>
> ** Changed in: ubiquity (Ubuntu)
>       Status: New => Incomplete
>
> --
> Installer ignores boot loader device
> https://bugs.launchpad.net/bugs/525040
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Nick Booker (nmbooker)]

I've installed again with Ubiquity 2.1.24 and it installed GRUB2 to sda12 as expected.
Thank you.

[Charlie Kravetz (cjkgeek)]

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[Bob Jonkman (bjonkman)]

I have just installed Lucid Lynx from ubuntu-10.04-beta1-desktop-amd64.iso and have experience the same problem: The "Advanced" option will not let me select "/dev/sda15" as the partition on which to install the boot loader.

Is the updated Ubiquity not shipping with this ISO?

--Bob.

[Nick Booker (nmbooker)]

You need to enter the partition in the box manually on the beta because the drop-down doesn't work.

That problem is described in a separate bug: #539204
  https://bugs.launchpad.net/bugs/539204