Problem booting into Fedora Server on Raspberry Pi 4

I wanted to try Fedora Server on my Raspberry Pi 4, but it won’t boot. I downloaded the latest Fedora 35 Server aarch64 raw image from https://alt.fedoraproject.org/alt/. Then I followed the instructions on Architectures/ARM/Raspberry Pi - Fedora Project Wiki to flash my microSD card.

Here is the output from arm-image-installer:

sudo arm-image-installer --image Fedora-Server-35-1.2.aarch64.raw.xz --resizefs --target rpi4 --media /dev/sde

=====================================================
**************************************************
= NOTE: This host system uses the same VG name as 
= the AArch64 disk image. To avoid issues, the VG 
= on the image will be renamed to 'fedora-server'.
**************************************************
= Selected Image:                                 
= Fedora-Server-35-1.2.aarch64.raw.xz
= Selected Media : /dev/sde
= U-Boot Target : rpi4
= Root partition will be resized
=====================================================
 
*****************************************************
*****************************************************
******** WARNING! ALL DATA WILL BE DESTROYED ********
*****************************************************
*****************************************************
 
 Type 'YES' to proceed, anything else to exit now 
 
= Proceed? YES
= Writing: 
= Fedora-Server-35-1.2.aarch64.raw.xz 
= To: /dev/sde ....
7514767360 bytes (7.5 GB, 7.0 GiB) copied, 271 s, 27.7 MB/s
0+728032 records in
0+728032 records out
7516192768 bytes (7.5 GB, 7.0 GiB) copied, 316.772 s, 23.7 MB/s
= Writing image complete!
= Resizing /dev/sde ....
  Processing VG fedora_fedora because of matching UUID fr0O3c-g90f-jeh0-9fjv-q63b-VCGi-wH8yIn
  Volume group "fr0O3c-g90f-jeh0-9fjv-q63b-VCGi-wH8yIn" successfully renamed to "fedora-server"
Checking that no-one is using this disk right now ... OK

Disk /dev/sde: 29.81 GiB, 32010928128 bytes, 62521344 sectors
Disk model: SD  Transcend   
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x8f4e3975

Old situation:

Device     Boot   Start      End  Sectors  Size Id Type
/dev/sde1  *       2048  1230847  1228800  600M  6 FAT16
/dev/sde2       1230848  3327999  2097152    1G 83 Linux
/dev/sde3       3328000 14680063 11352064  5.4G 8e Linux LVM

/dev/sde3: 
New situation:
Disklabel type: dos
Disk identifier: 0x8f4e3975

Device     Boot   Start      End  Sectors  Size Id Type
/dev/sde1  *       2048  1230847  1228800  600M  6 FAT16
/dev/sde2       1230848  3327999  2097152    1G 83 Linux
/dev/sde3       3328000 62521343 59193344 28.2G 8e Linux LVM

The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
  Physical volume "/dev/sde3" changed
  1 physical volume(s) resized or updated / 0 physical volume(s) not resized
  Size of logical volume fedora-server/root changed from 5.41 GiB (1385 extents) to 28.22 GiB (7225 extents).
  Logical volume fedora-server/root successfully resized.
meta-data=/dev/mapper/fedora--server-root isize=512    agcount=4, agsize=354560 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=1, sparse=1, rmapbt=0
         =                       reflink=1    bigtime=0 inobtcount=0
data     =                       bsize=4096   blocks=1418240, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
log      =internal log           bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
data blocks changed from 1418240 to 7398400
sed: can't read /tmp/fw/EFI/fedora/grubenv: No such file or directory
= Raspberry Pi 4 Uboot is already in place, no changes needed.

= Installation Complete! Insert into the rpi4 and boot.

However when I try to boot into the Pi, I get this:

[  170.267856] fedora dracut-initqueue[517]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
[  170.274414] fedora dracut-initqueue[517]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2ffedora_fedora\x2froot.sh: "[ -e "/dev/fedora_fedora/root" ]"
[  170.280613] fedora dracut-initqueue[517]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fmapper\x2ffedora_fedora-root.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
[  170.280613] fedora dracut-initqueue[517]:     [ -e "/dev/mapper/fedora_fedora-root" ]
[  170.280613] fedora dracut-initqueue[517]: fi"
[  170.288889] fedora dracut-initqueue[517]: Warning: dracut-initqueue: starting timeout scripts
[  170.424362] fedora dracut-initqueue[2342]: Scanning devices mmcblk0p3  for LVM logical volumes fedora_fedora/root
[  170.453211] fedora dracut-initqueue[2363]: WARNING: locking_type (4) is deprecated, using --sysinit --readonly.
[  170.497325] fedora dracut-initqueue[2363]: inactive          '/dev/fedora-server/root' [28.22 GiB] inherit
[  170.685535] fedora dracut-initqueue[2365]: WARNING: locking_type (4) is deprecated, using --sysinit --readonly.
[  170.715700] fedora dracut-initqueue[2365]: Allowing activation with --readonly --sysinit.
[  170.716098] fedora dracut-initqueue[2365]: Volume group "fedora_fedora" not found
[  170.716447] fedora dracut-initqueue[2365]: Cannot process volume group fedora_fedora

I believe this issue is because the LVM Volume Group on the SD card is fedora-server instead of fedora_fedora, but I am not sure how to fix this issue. If needed, I can post other sections from the rdosreport.txt that I copied off the system when I reached the dracut emergency shell.

Fixed the issue by renaming the volume group with sudo vgrename fedora-server fedora_fedora.

2 Likes