Hi!
I followed these steps:
- Create a new VPS on Hetzner, choosing the official Fedora 43 image
sudo dnf -y install system-reinstall-bootcsystem-reinstall-bootc quay.io/fedora/fedora-bootc:43sudo reboot
The reboot seemed to work, but i got a “failed unit” bootloader-update
Jan 22 14:59:56 fedora bootupctl[839]: error: Failed adopt and update: opening EFI dir: No such file or directory (os error 2)
As I am no expert I wonder if someone here can help me troubleshoot this. Why is this happening, who’s “fault” is it, what does it mean, and what should the next step be?
I’m grateful for any helpful advice
EDIT
[root@static ~]# mount | grep boot
/dev/sda1 on /boot type ext4 (rw,relatime,seclabel)
[root@static ~]# mount | grep efi
[root@static ~]# ls /boot
boot bootupd-state.json grub2 loader loader.1 ostree
I mean, I clearly see that I do not have anything mounted at /boot/efi. But… is this my responsibility? I’m confused. Why is this not configured in quay.io/fedora/fedora-bootc:43 if it contains a unit that requires it to be present?
EDIT 2
I also got
Jan 26 17:17:08 fedora systemd[1]: Starting bootc-destructive-cleanup.service - Cleanup previous the installation after an alongside installation...
Jan 26 17:17:08 fedora fedora-bootc-destructive-cleanup[833]: + mount -o remount,rw /sysroot
Jan 26 17:17:08 fedora fedora-bootc-destructive-cleanup[845]: + xargs rpm -e --root=/sysroot --dbpath=/usr/lib/sysimage/rpm
Jan 26 17:17:08 fedora fedora-bootc-destructive-cleanup[844]: + rpm -qa --root=/sysroot --dbpath=/usr/lib/sysimage/rpm
Jan 26 17:17:08 fedora fedora-bootc-destructive-cleanup[869]: rpm: no packages given for erase
Jan 26 17:17:08 fedora systemd[1]: bootc-destructive-cleanup.service: Main process exited, code=exited, status=123/n/a
Jan 26 17:17:08 fedora systemd[1]: bootc-destructive-cleanup.service: Failed with result 'exit-code'.
Jan 26 17:17:08 fedora systemd[1]: Failed to start bootc-destructive-cleanup.service - Cleanup previous the installation after an alongside installation.