Failed to write bootloader configuration

[Tjzabel]

@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]

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.

[axk4545]

@ct-martin Will look into it soo.

[Tjzabel]

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

[linux-modder]

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

[axk4545]

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

[axk4545]

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

[ct-martin]

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

[ct-martin]

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

[axk4545]

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

[axk4545]

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

[linux-modder]

@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]

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

[axk4545]

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

[axk4545]

@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]

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

[Tjzabel]

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

[axk4545]

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

[ct-martin]

So, what did we change between then and now?

[linux-modder]

@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]

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

[Tjzabel]

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

[axk4545]

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

[Tjzabel]

@axk4545 How should I go about finding that out.

[axk4545]

@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]

This install used linuxmodder.iso

[axk4545]

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]

Will check @AdamWill on any issues the logs may reveal

[axk4545]

@Tjzabel's install was accidentally done in BIOS mode

[jibby0]

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]

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

[AdamWill]

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]

@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]

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]

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

[axk4545]

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]

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

[Rtoax]

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