Boot-Repair custom entries fail when SecureBoot enabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Boot-Repair |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Summary:
I used Boot-Repair 3.197 under ubuntu 12.10 to re-configure the bootsetup (Windows 8, Fedora 18, ubuntu 12.10, all under UEFI Secure Boot). Boot-Repair left the configuration unusable.
How can I create a boot process with the following characteristics:
1. ubuntu bootloader is the standard bootloader
2. ubuntu bootloader shows all other systems (Windows 8, Fedora 18) and their respective modes (Advanced Options, Rescue Mode etc.)
Details of Hardware:
\pkt[Hardware]
HP ENVY 6-1160ez
- Chip: Intel® Core™ i5-3317U (1,7 GHz, 3 MB L3-Cache)
- RAM: 8 GB DDR3
- Disk: 500 GB SATA (5400 U/min) + 32 GB mSATA SSD
- Display: HD BrightView LED-Display mit einer Diagonalen von 39,6 cm (15,6") und Hintergrundbele
- Graphic: Intel HD Graphics 4000 (bis zu 1,65 GB)
- Details: http://
- the Laptop comes with pre-installed Windows 8 and UEFI
Details of the partition table (as shown by gparted with some addititional comments):
/dev/sda1 Windows Recovery Partition: 400 MB
/dev/sda2 EFI System Partition, fat16 260 MB *
/dev/sda3 ?? 128 MB
/dev/sda4 Windows8 (C:) NTFS: 97 GB
/dev/sda5 Partition (L:) exFAT: 50 GB (exchange partition between Windows and Linux)
/dev/sda6 Windows8 Recovery 17 GB (steht fast ganz am Ende)
/dev/sda7 Fedora18 EFI Boot, fat16 200 MB *
/dev/sda8 Fedora18 /boot 500 MB
/dev/sda9 Fedora18 /home 60 GB
/dev/sda10 Fedora18 swap 8 GB
/dev/sda11 Fedora18 / 30 GB
/dev/sda12 ubuntu12.10 /boot 477 MB
/dev/sda13 ubuntu12.10 EFI Boot, fat32 191 MB *
/dev/sda14 ubuntu12.10 / 30 GB
/dev/sda15 ubuntu12.10 /home 56 GB
/dev/sda16 ubuntu12.10 swap 7 GB
unallocated 111 GB
More details can be found under:
http://
Details of Bug:
I booted ubuntu 12.10 via UEFI (-> F9 "Boot Options" -> select ubuntu) . I then started Boot-Repair and set the following options in the "advanced menue":
- ubuntu is the preferred operating system to be booted as standard
- /dev/sda2 is used as UEFI System Partition
I then pressed "apply" which resulted in changes to the files in /dev/sda2 and potentially elsewhere.
Then a re-boot shows the following characterisitics
1. ubuntu bootloader is the standard bootloader
2. the ubuntu bootloader shows some additional 15-25 entries for Windows 8 and Fedora 18. When chosen all other enteries except ubuntu enter directly in an error
3. re-booting Windows 8 via the UEFI (-> F9 "Boot Options") leads Windows into the rescue mode. Checking disks shows not errors. Reboot of Windows via UEFI then works. . The ubuntu bootloader still shows some additional 15-25 entries for Windows 8 and Fedora 18. When chosen all other enteries except ubuntu enter directly in an error
4. manually restoring all original files in /dev/sda2 brings back Windows 8 as standard bootloader. But:
a.) re-booting ubuntu via UEFI (-> F9 "Boot Options") and then chosing "Windows 8" in grub menue directly leads to an error
b.) re-booting Fedora 18 via UEFI (-> F9 "Boot Options") and then chosing "Windows 8" in grub menue directly leads to an error
Details of the setup can be seen here:
http://
Anybody can help? How can I create a boot process with the following characteristics:
1. ubuntu bootloader is the standard bootloader
2. ubuntu bootloader shows all other systems (Windows 8, Fedora 18) and their respective modes (Advanced Options, Rescue Mode etc.)
description: | updated |
affects: | ubuntu → boot-repair |
summary: |
- Boot-Repair does not work for dual boot system (ubuntu 12.10 and Windows - 8 with UEFI Secure Boot) + Boot-Repair custom entries fail when SecureBoot enabled |
Changed in boot-repair: | |
status: | Incomplete → Invalid |
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/1116741/ +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.]