On Fedora 39 ( arm-image-installer-3.9)
I did this
🐚 sudo arm-image-installer --image=Fedora-Server-39-1.5.aarch64.raw.xz --media=/dev/sda --resizefs --relabel --showboot --sysrq --target=rpi02w ===================================================== ************************************************** = 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-39-1.5.aarch64.raw.xz = Selected Media : /dev/sda = U-Boot Target : rpi02w = SELinux relabel will be completed on first boot. = System Request debugging of the kernel will be enabled. = Root partition will be resized = Boot messages will be shown onscreen. ===================================================== ***************************************************** ***************************************************** ******** WARNING! ALL DATA WILL BE DESTROYED ******** ***************************************************** ***************************************************** Type 'YES' to proceed, anything else to exit now = Proceed? YES = Writing: = Fedora-Server-39-1.5.aarch64.raw.xz = To: /dev/sda .... 7516192768 bytes (7,5 GB, 7,0 GiB) copied, 1446 s, 5,2 MB/s 1792+0 records in 1792+0 records out 7516192768 bytes (7,5 GB, 7,0 GiB) copied, 1445,97 s, 5,2 MB/s = Writing image complete! = Resizing /dev/sda .... WARNING: VG name fedora is used by VGs ER75Cp-DCj3-SzmN-9x5W-a8t1-EqvR-pXQr4y and rUI6BI-wiwM-ykws-Dhue-6yU8-PyzH-Tz9cTx. Fix duplicate VG names with vgrename uuid, a device filter, or system IDs. WARNING: VG name fedora is used by VGs ER75Cp-DCj3-SzmN-9x5W-a8t1-EqvR-pXQr4y and rUI6BI-wiwM-ykws-Dhue-6yU8-PyzH-Tz9cTx. Fix duplicate VG names with vgrename uuid, a device filter, or system IDs. Processing VG fedora because of matching UUID ER75Cp-DCj3-SzmN-9x5W-a8t1-EqvR-pXQr4y Volume group "ER75Cp-DCj3-SzmN-9x5W-a8t1-EqvR-pXQr4y" successfully renamed to "fedora-server" Checking that no-one is using this disk right now ... OK Disk /dev/sda: 57,98 GiB, 62260248576 bytes, 121602048 sectors Disk model: MMC Storage 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: 0x76005dca Old situation: Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048 1230847 1228800 600M 6 FAT16 /dev/sda2 1230848 3327999 2097152 1G 83 Linux /dev/sda3 3328000 14680063 11352064 5,4G 8e Linux LVM /dev/sda3: New situation: Disklabel type: dos Disk identifier: 0x76005dca Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048 1230847 1228800 600M 6 FAT16 /dev/sda2 1230848 3327999 2097152 1G 83 Linux /dev/sda3 3328000 121602047 118274048 56,4G 8e Linux LVM The partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks. Physical volume "/dev/sda3" 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 56,39 GiB (14437 extents). Logical volume fedora-server/root successfully resized. = No U-Boot files found for rpi02w. = Enabling System Request debugging of the kernel. = Touch /.autorelabel on rootfs. = Installation Complete! Insert into the rpi02w and boot.
Then checking actual FS size:
🐚 sudo vgchange -ay fedora-server 🐚 sudo mount /dev/fedora-server/root /mnt/ 🐚 df -h | tail -1 /dev/mapper/fedora--server-root 5,4G 2,6G 2,9G 48% /mnt
To workaround I had to:
🐚 sudo xfs_growfs /dev/fedora-server/root
Result
🐚 df -h ... /dev/mapper/fedora--server-root 57G 2,9G 54G 6% /mnt
Thanks, could you try the latest version - arm-image-installer-4.1-2.fc39? It should be in Fedora 39 updates. You can also download it here: https://koji.fedoraproject.org/koji/buildinfo?buildID=2410893
My bad. I'm actually running Fedora 38. I installed the new package though and it resizes properly.
There is still an issue though. The boot process freezes at
Exiting boot services..
Any ideas about that? Maybe I should file another issue for it?
P.S. For the test I installed Raspbian with rpi-imager and it worked well with wifi and everything.
rpi-imager
That's not a problem with arm-image-installer
Exiting boot services.. Any ideas about that? Maybe I should file another issue for it?
You seem to have added --showboot, check that did remove the "rhgb quiet" bits from the kernel cmd line in grub. Maybe take it to the fedora arm mailing list if that doesn't work. It's not a arm-image-installer bug.
That's irrelevant in the Fedora context.
Metadata Update from @pbrobinson: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
--showboot didn't make any difference except that I now didn't see where it failed. I just see the "Booting ..." line and nothing more comes up.
--showboot
Tried flashing Fedora-Server-37-1.7.aarch64.raw.xz and it indeed booted. So obviously the issue is with Fedora.
Fedora-Server-37-1.7.aarch64.raw.xz
Thank a lot for the help to debug this!
Just FYI if anybody comes along this thread by search, I asked in the fedora arm mailing list here:
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org/thread/63ZBASZY7TU5BQ4MTYNPMIE4JDEGLLEG/
Log in to comment on this ticket.