Arm image pi4 transaction failed

Ask Fedora
1

fedora 42 arm pi4 rpm error more space needed filesystem, never had this problem before should the image not be fixed to allow more space?

How can I fix it please, searched and not found anything

[191/191] Total 100% | 0.0 B/s | 0.0 B | 00m05s
Running transaction
Transaction failed: Rpm transaction failed.

  • installing package glibc-all-langpacks-2.41-5.fc42.aarch64 needs 118MB more space on the / filesystem
  • installing package uboot-images-armv8-1:2025.04-2.fc42.noarch needs 437MB more space on the / filesystem
2

When I use fedora’s arm-image-installer with the --resizefs option it grows the root partition to fill up the sdcard.

If you did not do that then you have a minimal root partition.

3

I did use this line sudo arm-image-installer --image=Fedora-Server-40-1.14.aarch64.raw --media=/dev/sda --target=rpi4 --resizefs and still get the space error

Attached image may help, this is fedora 42 on pi4, I have put fedora 41 onto my pi3 in the same way as this, and it went though install and update without any problems, apart from being slow.

Screenshot_20250511_170651
Screenshot_20250511_1706511915×200 16.5 KB

4

Can you post the output of lsblk -f as preformatted text, using the </> button please?

5

As Requested thanks again, hoping there is a fix as really need to get it running

lsblk -f
NAME                FSTYPE      FSVER    LABEL  UUID                                   FSAVAIL FSUSE% MOUNTPOINTS
mmcblk1                                                                                               
├─mmcblk1p1         vfat        FAT16    EFI    4299-B0AF                               460.7M     8% /boot/efi
├─mmcblk1p2         ext4        1.0      BOOT   4a33b579-e653-4a28-8cd3-e2eef1c89600    634.7M    27% /boot
└─mmcblk1p3         LVM2_member LVM2 001        F7MYnt-kd7L-yqjA-Qjsx-E21N-k3py-XtC1FJ                
  └─systemVG-LVRoot xfs                  fedora 9bf0a85e-bb35-4e70-ba4d-5947098557d2    303.3M    93% /
zram0               swap        1        zram0  17ccca5a-f591-4535-b428-430ee9935eb4                  [SWAP]
6

My pi servers do not have LVM setup. Is that something you did?

I guess that sudo pvscan will show that you have unused space in your LVM that you will need to allocation some of to LVRoot and then grow the xfs file system.

7

No I just got the Arm image and used the arm image installer with this line as I always do.

sudo arm-image-installer --image=Fedora-Server-40-1.14.aarch64.raw --media=/dev/sda --target=rpi4 --resizefs 

sudo pvscan
[sudo] password for webdoc: 
  PV /dev/mmcblk0p3   VG systemVG   lvm2 [8.53 GiB / <4.04 GiB free]
  Total: 1 [8.53 GiB] / in use: 1 [8.53 GiB] / in no VG: 0 [0   ]

I’m assumimg I can use cockpit in some way to fix this?

Fedora 41 cockpit

fedora-41-cockpit
fedora-41-cockpit1536×452 22.6 KB

Fedora 42 cockpit

Fedora-42-cockpit
Fedora-42-cockpit1585×391 22.7 KB

8

I’m not familiar with resizing xfs. Also always using command line tools to work on my systems and not cockpit.

But you do have 4.04 GiB that you can add to the / partition.

9

I see this SO talks about how to resize an xfs on line: https://stackoverflow.com/questions/38160794/how-to-resize-root-partition-online-on-xfs-filesystem

But first you need to grow the / partition which you can do with the lvresize command.

10

replace --resizefs with --xfs_growfs then? and what size would I put lvresize and how?

11

No. From the terminal use the program xfs_growfs as the SO reply says.

12

This or the next answer

ou're working on an XFS filesystem, in this case you need to use xfs_growfs instead of resize2fs. Two commands are needed to perform this task :

# growpart /dev/sda 1
growpart is used to expand the sda1 partition to the whole sda disk.

# xfs_growfs -d /dev/sda1
xfs_growfs is used to resize and apply the changes.

# df -h
13

I don’t have any sda drives bit lost here

14

The steps should be:

  1. grow the lv with lvresize
  2. Run xfs_resize to add the new space to /
15

No command with matching syntax recognised. Run ‘lvresize --help’ for more information.

16

does the following look right to you?

$ sudo lvresize -l +100%FREE /dev/systemVG/LVRoot
  Size of logical volume systemVG/LVRoot changed from 8.53 GiB (2184 extents) to 28.25 GiB (7233 extents).
  Logical volume systemVG/LVRoot successfully resized.
webdoc@skynet-pi4:~$ sudo xfs_growfs /dev/systemVG/LVRoot
meta-data=/dev/mapper/systemVG-LVRoot isize=512    agcount=8, agsize=294656 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=1, sparse=1, rmapbt=1
         =                       reflink=1    bigtime=1 inobtcount=1 nrext64=1
         =                       exchange=0  
data     =                       bsize=4096   blocks=2236416, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0, ftype=1, parent=0
log      =internal log           bsize=4096   blocks=128250, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
data blocks changed from 2236416 to 7406592
webdoc@skynet-pi4:~$ df -h
Filesystem                   Size  Used Avail Use% Mounted on
/dev/mapper/systemVG-LVRoot   28G  3.5G   25G  13% /
devtmpfs                     4.0M     0  4.0M   0% /dev
tmpfs                        3.8G     0  3.8G   0% /dev/shm
efivarfs                     128K  3.0K  125K   3% /sys/firmware/efi/efivars
tmpfs                        1.6G  1.3M  1.6G   1% /run
tmpfs                        1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
/dev/mmcblk0p2               966M  266M  635M  30% /boot
tmpfs                        3.8G     0  3.8G   0% /tmp
/dev/mmcblk0p1               500M   40M  461M   8% /boot/efi
tmpfs                        1.0M     0  1.0M   0% /run/credentials/systemd-resolved.service
tmpfs                        1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
tmpfs                        1.0M     0  1.0M   0
17

Yes that looks correct, you now have the disk space you wanted I assume?

18

Would have been better if the image was fixed, so no need to go though all this, my sd card is 32GB, if the devs fix the image is this line how it would be

/dev/mapper/systemVG-LVRoot   28G  3.5G   25G  13% /

as in is that the 3rd partition that all data goes too, if that makes sence?

I have had other goes at doing this and the size only went to around 8GB

19

The image is required to be usable on a range of sdcard sizes.
Having a small image and doing the resize allows for that.

What is new is the use of LVM and the extra steps to complete the resize.
LVM is a good idea as it means you can add more partition like a seperate /var.

20

Only just got back into working on this I did get the raw image expanded on my sd card, I will get around to posting the info on how I did it.

In the meantime I have just got a raspberry pi5 8GB and I have used the deskpi case that allows the use of nvme drive, can anyone give me a quick answer as to if the kernal in fedora server 42 has the needed moduals for the nvme to enable?

Thanks again for the help here

Regards

Ian