[Bug 1267922] Re: Installer becomes confused and crashes when grub-install fails
Daniel van Vugt
daniel.van.vugt at canonical.com
Fri Jul 26 06:36:27 UTC 2019
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.
** Changed in: ubiquity (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1267922
Title:
Installer becomes confused and crashes when grub-install fails
Status in ubiquity package in Ubuntu:
Won't Fix
Bug description:
If grub-install fails, ubiquity screws up in two ways:
1) It unmounts /target/dev, so when you select another location ( the correct one ) to install grub to, that attempt fails as well
2) After selecting a different loation, the installer goes immediately to the installation complete dialog, while attempting to install grub in the background. At this point, clicking just about anything causes ubiquity to crash.
You can easily reproduce this in a vm with two disk drives. Install
the system on sda, but select sdb1 for grub. This will fail because
cross disk installs require the embed area. When the prompt comes up
to pick another location, pick sdb or sda, both of which will work if
you chose them the first time. The installation complete message pops
up immediately. A second or two later, the grub install failed dialog
comes back. In syslog you will see the second attempt failed because
grub-probe could not find /boot. This is because /dev is not mounted
in /target at this point.
We get many crash reports filed to grub as a result of this where the
wrong grub target was chosen the first time, then the user picks the
correct place, but installing there fails too.
Further, often the grub install failed dialog box locks up and won't
respond to any button presses.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1267922/+subscriptions
More information about the foundations-bugs
mailing list