Manual bootloader update needed for Fedora 37 IoT on AArch64
by Paul Whalen
With the recent move to the 6.2 Kernel in Fedora 37 IoT, some AArch64
systems may not boot with the following error:
error: ../../grub-core/loader/arm64/linux.c:57:invalid magic number.
error: ../../grub-core/loader/arm64/linux.c:297:you need to load the
kernel first.
To fix this manually you need to update the bootloader. Before doing so it
is recommended you back up any data.
Boot into the last working deployment and run the following command:
cp /sysroot/ostree/deploy/fedora-iot/deploy/e5b7596f4a84020118bbc3b63c2291768ee975430dc8e050f6338048b7fc2a31.0/usr/lib/ostree-boot/efi/EFI/fedora/*
/boot/efi/EFI/fedora/
You will need to adjust the commit based on your local deployment.
After doing that you should be able to boot the new kernel.
Apologies for any trouble,
Paul
2 months
potential turbulence ahead with 6.2 kernel on aarch64 devices
by Dusty Mabe
In Fedora CoreOS we found an issue today where systems that have been
around for a while won't have a new enough bootloader bits to boot
the new 6.2 aarch64 kernel.
https://github.com/coreos/fedora-coreos-tracker/issues/1441
This kernel is already in the F38 beta, and unfortunately coming very soon
to F37/F36, which limits the amount of time we have to react to the problem.
Of course, anyone with console access can simply boot the older deployment
and update the bootloader.
We're working through how to handle this for Fedora CoreOS now, but that
solution may look different than what is done for IoT.
Dusty
2 months, 3 weeks