Installer fails to create startup.nsh for EFI system on VirtualBox
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Opinion
|
High
|
Unassigned |
Bug Description
Summary:
When installing Ubuntu using LUKS & LVM onto a VirtualBox system, it creates a non-bootable system because it fails to create the file startup.nsh on the EFI partition.
How to duplicate:
1. Create a new virtual machine on VirtualBox with a sufficiently large disk drive. Ensure that "Enable EFI" is ticked in Settings > System > Motherboard.
2. Run the Ubuntu installer from a Live CD. Chose the default "Erase disk and install Ubuntu". Also tick "Encrypt the new Ubuntu installation for security", which automatically selects "Use LVM with the new Ubuntu installation".
3. Allow the installation to finish.
What should happen:
1. On rebooting the virtual machine, it should boot into Ubuntu.
What does happen:
1. On rebooting the virtual machine, it boots into the UEFI Interactive Shell and cannot proceed.
Workaround:
1. Create a file named startup.nsh on the FS0: drive (either using the UEFI Interactive Shell or by booting into the Live CD). The file should contain the following single line:
\EFI\ubuntu\
2. Reboot the virtual machine. It will boot into Ubuntu.
Proposed solution:
1. The Ubuntu installer should create the startup.nsh file when creating the EFI partition.
Further information:
• Tested on VirtualBox 5.1.14
• Tested with both Ubuntu 16.04.1 64-bit and Lubuntu 16.04.1 64-bit
affects: | ubuntu → ubiquity (Ubuntu) |
tags: | added: xenial |
Changed in grub2 (Ubuntu): | |
importance: | Undecided → High |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1665329/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]