When selecting to not install bootloader on MBR I end up with no boot loader

Bug #613685 reported by Tom Pino
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

Just installed 10.10 A3 rebuild RC ISO.

Selected to not install boot loader so as not to have to deal with it. I have a custom menu that is installed on the MBR,

Ended up with no working grub. This is not much of a problem for me as I have a chroot script on all my installs to copy to the Live Session. Just rebooted, installed the grub I want, reported this bug.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: ubiquity 2.3.3
ProcVersionSignature: Ubuntu 2.6.35-14.19-generic 2.6.35
Uname: Linux 2.6.35-14-generic x86_64
Architecture: amd64
Date: Thu Aug 5 00:48:32 2010
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100803.1)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity

Revision history for this message
Tom Pino (metalsmith-rangeweb) wrote :
tags: added: iso-testing
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Hello Tom:
There's two point to clarify:
- In advanced option popup, if you uncheck 'install bootloader' , you tell to the system "don't install grub on MBR".
- Elsewhere, if you lay checked, you can select where install grub and so boot from that position.
:)Fabio

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Tom Pino (metalsmith-rangeweb) wrote :

Yes I am aware what telling it not to install does.

What I am saying is that it did not install on the MBR but did screw up the grub that was installed on the MBR. This caused me to not be able to boot to anything.

When I am in a hurry I generally install this way. I have set partitions and use a custom menu with symbolic entries. This means that I can use the entry for the partition and boot any Debian based OS that happens to be on it at the momment. I can then worry about setting grub up as I want later.

I just chrooted to the OS I want for grub/root and installed it on the MBR.

While not perhaps connected to this problem, when I did get back to the bugger grub was not properly installed. The only file in /boot/grub was grub.cfg. Reinstalling got me one more. apt-get purge grub-pc grub-common and then installing same gave me the same deal. I transplanted a working /boot/grub to that install. Then I could update-grub without a page of errors.

I have several installs of 10.10 for testing different things and to have "through away" installs to test update/upgrades on. Do not and have not had this problem with grub on any others but have not installed any more from the A3 series of images.

Changed in ubiquity (Ubuntu):
status: Incomplete → New
Revision history for this message
Simon Quigley (tsimonq2) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 613685

and any other logs that are relevant for this particular issue.

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.