[Bug 704763] Re: boot loader not installed to target disk
Jason Schuh
704763 at bugs.launchpad.net
Wed Mar 14 20:31:03 UTC 2012
** Changed in: casper (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to casper in Ubuntu.
https://bugs.launchpad.net/bugs/704763
Title:
boot loader not installed to target disk
Status in “casper” package in Ubuntu:
Incomplete
Bug description:
Binary package hint: casper
Advised by "ubuntu brainstorm" moderator "cheesehead" (please see
http://brainstorm.ubuntu.com/idea/26998/) to file this as a "bug
report" against the "casper" package of ubuntu release 10.x While I
can see similarities between what follows and bug #223428, I am not
sure they are the same. At any rate, here goes...
Like many people, I suspect, I wanted to install unbuntu on a physical
drive completely separate from the one containing my legacy OS
(Windows Vista); in my case, an external hard-drive connected to my
computer by USB. After some trial-and-error, I realized that the
installation option I should use was the "Erase and use entire disk"
option (though this was scary, because at first I didn't know that I
would later be presented with a choice of WHICH disk to erase and
use). The trouble was, though, that even when I realized I could
specify the external disk as the one to which ubuntu should be
installed, and did so, the installer STILL overwrote the boot loader
of my computer's INTERNAL hard-drive (the one containing Windows
Vista) with GRUB. Because of this, I could not boot the computer at
all unless my external hard-drive was connected. I finally got around
this by going with the "specify partitions manually" installation
option, which also gave me the option to specify the location of the
boot loader, but not before I had made my computer unbootable (by
futzing around with the computer's boot sector) and had to hunt down
and create a Windows Vista restore disk just for the purpose of
restoring the boot loader stored on the computer's internal hard-
drive.
Suggested solutions:
1. Somehow indicate, early on, that the installer (person) will be presented with a CHOICE of which disk will be erased and used entirely (please see the description in the above "idea rationale" section).
2. Write the boot loader (GRUB) to the disk targeted for the ubuntu installation when the "erase and use entire disk" installation option is chosen.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/704763/+subscriptions
More information about the foundations-bugs
mailing list