Skip to content
This repository has been archived by the owner on Oct 1, 2022. It is now read-only.

Failed to write bootloader configuration #58

Closed
Tjzabel opened this issue Oct 14, 2017 · 37 comments
Closed

Failed to write bootloader configuration #58

Tjzabel opened this issue Oct 14, 2017 · 37 comments

Comments

@Tjzabel
Copy link
Member

Tjzabel commented Oct 14, 2017

@axk4545 @ct-martin When installing TigerOS GNOME edition to my physical laptop, the bootloader fails to install properly.

When I select the exact same configuration on the official Fedora 26 distro, the installation goes fine.

@ct-martin
Copy link
Member

Debugged w/ @Tjzabel - Confirmed issue exists and involves UEFI, BIOS install works fine.

@axk4545 going to assign this to you since this is your territory.

@ct-martin ct-martin added this to the Switch to GNOME3 milestone Oct 14, 2017
@ct-martin ct-martin added the bug label Oct 14, 2017
@axk4545
Copy link
Member

axk4545 commented Oct 14, 2017

@ct-martin Will look into it soo.

@Tjzabel
Copy link
Member Author

Tjzabel commented Oct 14, 2017

UPDATE: Currently this issue is present both in the Cinnamon and GNOME TigerOS installations.

@linux-modder
Copy link
Contributor

@axk4545 @Tjzabel confirm installer / install image have grub2-efi package installed. If so, file bug upstream with both anaconda and grub2 developers.

@axk4545
Copy link
Member

axk4545 commented Oct 15, 2017

@linux-modder @Tjzabel @ct-martin it is in the ks. please confirm it is actually in the resultant image.

@axk4545
Copy link
Member

axk4545 commented Oct 15, 2017

per @linux-modder add --efi to LMC command in build scripts.

@ct-martin
Copy link
Member

@axk4545 Can confirm grub2-efi is installed on the liveusb, will rebuild with —efi and then we can retest

@ct-martin
Copy link
Member

"livemedia-creator: error: unrecognized arguments: --efi"
(cc @axk4545 @linux-modder )

@axk4545
Copy link
Member

axk4545 commented Oct 16, 2017

This makes me think we should also test on Mac as they have a special EFI implementation

@axk4545
Copy link
Member

axk4545 commented Oct 17, 2017

@axk4545 Attempted an install with a TigerOS live USB burned with Fedora Media Writer. Same result

@linux-modder
Copy link
Contributor

@ct-martin on live doesn't mean it's in the squashfs tho the squahsfs is what is rsync'd off for install on a non netinstall iso

Will check the present ks today and see if I can find a bug in the logic or usage.

@ct-martin
Copy link
Member

@linux-modder do you have a command I can run on the live to test if it's there?

@axk4545
Copy link
Member

axk4545 commented Oct 22, 2017

@Tjzabel will test once we get a build. currently blocked on gstreamer dep issues upstream

@axk4545
Copy link
Member

axk4545 commented Oct 25, 2017

@Tjzabel can I have the logs from the install and the exact error message? the logs will be at /tmp/anaconda.log, /tmp/program.log and /tmp/syslog on the installer system(when running from the install disk/live usb). they can also be pulled from the installed system in /var/log/anaconda if you skip the GRUB step and complete the install.

@axk4545
Copy link
Member

axk4545 commented Oct 25, 2017

It might be an issue with the anaconda install class. I will look at it.

@Tjzabel
Copy link
Member Author

Tjzabel commented Oct 28, 2017

Soooo The UEFI build works!! How should I proceed? This issue may be available to close.

@axk4545
Copy link
Member

axk4545 commented Oct 28, 2017

@Tjzabel test it repeatedly. also if you have the old one with logs grab them please.

@ct-martin
Copy link
Member

So, what did we change between then and now?

@Tjzabel Tjzabel added the retest label Oct 28, 2017
@linux-modder
Copy link
Contributor

@Tjzabel what iso was tested? was it bare metal or virtual? so I can secondarily confirm and possibly peck at the logs and such to iron out the actual part that fixed this.

@Tjzabel
Copy link
Member Author

Tjzabel commented Oct 28, 2017

@linux-modder The latest ISO was tested using a UEFI build box. It was installed bare-metal.

@Tjzabel
Copy link
Member Author

Tjzabel commented Oct 28, 2017

There is no /boot/efi partition now, which is interesting

@axk4545
Copy link
Member

axk4545 commented Oct 28, 2017

@Tjzabel Make sure it wasn't done in BIOS mode by mistake

@Tjzabel
Copy link
Member Author

Tjzabel commented Oct 28, 2017

@axk4545 How should I go about finding that out.

@axk4545
Copy link
Member

axk4545 commented Oct 28, 2017

@Tjzabel @linux-modder @ct-martin I attempted a UEFI install and was able to reproduce the issue. Please see the attached logs. Also looping @AdamWill in on this as he expressed interest in helping me debug this
logs.zip

@axk4545
Copy link
Member

axk4545 commented Oct 28, 2017

This install used linuxmodder.iso

@axk4545
Copy link
Member

axk4545 commented Oct 28, 2017

Output of lsblk on the effected disk:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 74.5G 0 disk
├─sdb1 8:17 0 200M 0 part
├─sdb2 8:18 0 1G 0 part
└─sdb3 8:19 0 73.3G 0 part
├─tigeros-swap 253:3 0 7.5G 0 lvm
├─tigeros-home 253:4 0 21.6G 0 lvm
└─tigeros-root 253:5 0 44.3G 0 lvm

@axk4545
Copy link
Member

axk4545 commented Nov 3, 2017

Will check @AdamWill on any issues the logs may reveal

@axk4545
Copy link
Member

axk4545 commented Nov 3, 2017

@Tjzabel's install was accidentally done in BIOS mode

@jibby0
Copy link
Member

jibby0 commented Nov 3, 2017

I installed the latest build (linuxmodder.iso) in Virtualbox, forcing EFI. program.log indicates that grub2-mkconfig is returning a nonzero status:

Picture

When I looked in /boot/efi/EFI/ after the install, there was no tigeros directory. I'm guessing this is the issue.

The grub2-efi package creates boot/efi/EFI/fedora automatically. If the issue is our EFI directory isn't being created, we should either use the fedora directory, or rename fedora to tigeros.

I'm gonna remove our EFI change, rebuild, and see if the install completes successfully.

@axk4545
Copy link
Member

axk4545 commented Nov 4, 2017

@Josh1147582 Let us know if it work and we can make the fix.

@AdamWill
Copy link

AdamWill commented Nov 4, 2017

Ah, that's a reasonable theory. Other install classes that change efi_dir, I think, come along with a different set of bootloader packages that provide the appropriate directory. E.g. RHEL changes it to (I think) "redhat", and of course ships with grub2 packages that provide bootloader bits in /boot/efi/EFI/redhat.

@axk4545
Copy link
Member

axk4545 commented Nov 4, 2017

@AdamWill so do we have a need to keep it as TigerOS as far as conflicting or IP stuff? It would be nice to not repackage grub stuff

@AdamWill
Copy link

AdamWill commented Nov 4, 2017

I can't speak Officially Legally, but I'd be really surprised if we considered that a branding violation. Obviously if you want to be parallel installable with real-Fedora, changing it is useful.

@axk4545
Copy link
Member

axk4545 commented Nov 4, 2017

@AdamWill ok. will talk it over with @RITlug/tigeros-team

@axk4545
Copy link
Member

axk4545 commented Nov 10, 2017

http://pkgs.fedoraproject.org/cgit/rpms/grub2.git/tree/grub2.spec?h=f22
So it appears that GRUB sets the efidir at build time in the specfile. Would be nice to see if this can be split out.

@axk4545
Copy link
Member

axk4545 commented Nov 17, 2017

We have implemented a temporary fix with #71 and opened #79 to track making a more permanent fix

@axk4545 axk4545 closed this as completed Nov 17, 2017
@Rtoax
Copy link

Rtoax commented Jun 22, 2022

I got

The following error occurred while installing the boot loader. The system will not be bootable, Would you like to ignore this and continue with installation?

failed to write boot loader configuration

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants