Public bug reported:
Binary package hint: ubiquity
As the summary says, my first boot after a fresh install (over the top
of 10.10) yielded a Grub error 17. My guess is that the installer didn't
clobber the 10.10 grub, and that that was what was picked up at boot
time. I first tried changing the order of the hard drives in BIOS, but I
got error 17 on two others, an finally "system disk not found" on the
fourth. (Did I really have three grubs hanging around? Possible, as the
computer's been through many years of dist-upgrades, and I did have
related problems in the past.) I finally logged in via the live cd, and
ran grub-install against the first disk as indicated by the BIOS. This
worked.
This is the kind of bug that will leave the average consumer to drop of
their computer at the geek squad to have windows reinstalled, and will
permanently sour them on ubuntu. It's crucial that ubiquity be able to
detect existing boot loaders, detect bios disk order, and leave the
system in a state that will boot.
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774839
Title:
Grub error 17 - first time booting Natty after install
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
