You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to install a fedora 41 bootc through anaconda on raid-devices.
I have a test setup using VMs to mimick what will be on real-baremetal.
The installation procedure works if I do not configure raid devices in anaconda. As soon as I start configuring raid devices it fails to install the bootloader
It fails with the following error message from the anaconda package log:
DEBUG:anaconda.modules.payloads.payload.rpm_ostree.installation:Adding --update-
firmware to bootupdctl call
INFO:program:Running in chroot '/mnt/sysroot'... bootupctl backend install --aut
o --write-uuid --update-firmware --device /dev/vda /
INFO:program:error: boot data installation failed: installing component EFI: Upd
ating EFI firmware variables: Adding new EFI boot entry: Failed to read /sys/cla
ss/block/md125/partition: No such file or directory (os error 2)
DEBUG:program:Return code: 1
The kickstart file I try to use is:
# Basic setup
text
network --bootproto=dhcp --device=link --activate
timezone --utc UTC
bootloader --location=mbr --append="panic=30 console=tty0 console=ttyS1,115200"
# Basic partitioning
zerombr
clearpart --all --initlabel --disklabel=gpt --drives=/dev/vda,/dev/vdb
ignoredisk --only-use=/dev/vda,/dev/vdb
part raid.01 --ondrive=/dev/vda --size=1024
part raid.02 --ondrive=/dev/vda --size=512
part raid.03 --ondrive=/dev/vda --size=15000
part raid.04 --ondrive=/dev/vda --grow --size=1
part raid.11 --ondrive=/dev/vdb --size=1024
part raid.12 --ondrive=/dev/vdb --size=512
part raid.13 --ondrive=/dev/vdb --size=15000
part raid.14 --ondrive=/dev/vdb --grow --size=1
raid /boot --fstype=xfs --level=1 --device=boot raid.01 raid.11
raid /boot/efi --fstype=efi --level=1 --device=efi raid.02 raid.12
raid / --fstype=xfs --level=1 --device=root raid.03 raid.13
raid pv.02 --level=1 --device=data1 raid.04 raid.14
volgroup storage pv.02
# Here's where we reference the container image to install - notice the kickstart
# has no `%packages` section! What's being installed here is a container image.
ostreecontainer --url quay.io/fedora/fedora-bootc:41
firewall --disabled
services --enabled=sshd
# Only inject a SSH key for root
rootpw --iscrypted locked
sshkey --username root "ssh-ed25519 AAAACxxxx"
reboot
%post
%end
As you might notice I try to have dedicated /boot and /boot/efi partitions, since eventualyl I'd like to use luks to encrypt my root filesystem. However, I first wanted to make sure I can have a bootable system with raid, before diving into the luks part.
I had different variants on how to configure the raid, but eventually, it always failed with the same issue when installing the bootloader.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am trying to install a fedora 41 bootc through anaconda on raid-devices.
I have a test setup using VMs to mimick what will be on real-baremetal.
The installation procedure works if I do not configure raid devices in anaconda. As soon as I start configuring raid devices it fails to install the bootloader
It fails with the following error message from the anaconda package log:
The kickstart file I try to use is:
As you might notice I try to have dedicated /boot and /boot/efi partitions, since eventualyl I'd like to use luks to encrypt my root filesystem. However, I first wanted to make sure I can have a bootable system with raid, before diving into the luks part.
I had different variants on how to configure the raid, but eventually, it always failed with the same issue when installing the bootloader.
Beta Was this translation helpful? Give feedback.
All reactions