Since the move to btrfs for rootfs, the --resizefs option is partially broken. It "resizes" the partition fine as per gpt so tools like parted and fdisk show the full partition size. But btrfs itself is unaware of the change so the usable size remains the default 8GB, this can be seen the the df -h output post boot. The current workaround is to use btrfs filesystem resize +<size>g / post boot, although a similar fix should work on the host system as well before booting the image but I have not tested that yet.
--resizefs
df -h
btrfs filesystem resize +<size>g /
Could you paste the command you used and version of the script?
Could you paste the command you used and version of the script? arm-image-installer-3.1 sudo arm-image-installer --image ~/nfs-data/OS_Collection/unix/Fedora/Fedora-Workstation-33-1.3.aarch64.raw.xz --media /dev/sde --norootpass --resizefs --target=none
arm-image-installer-3.1 sudo arm-image-installer --image ~/nfs-data/OS_Collection/unix/Fedora/Fedora-Workstation-33-1.3.aarch64.raw.xz --media /dev/sde --norootpass --resizefs --target=none
arm-image-installer-3.1
sudo arm-image-installer --image ~/nfs-data/OS_Collection/unix/Fedora/Fedora-Workstation-33-1.3.aarch64.raw.xz --media /dev/sde --norootpass --resizefs --target=none
Hmm. Interesting, I've hit something similar not so long ago, and the interesting thing is that the resize would work with no issues on a sdcard, but would fail when writing to an nvme disk.
[fidencio@fedora Downloads]$ sudo arm-image-installer --media=/dev/nvme0n1 --resizefs --target=none --image=Fedora-Workstation-34-1.2.aarch64.raw.xz ===================================================== = Selected Image: = Fedora-Workstation-34-1.2.aarch64.raw.xz = Selected Media : /dev/nvme0n1 = U-Boot Target : none = Root partition will be resized ===================================================== ***************************************************** ***************************************************** ******** WARNING! ALL DATA WILL BE DESTROYED ******** ***************************************************** ***************************************************** Type 'YES' to proceed, anything else to exit now = Proceed? YES = Writing: = Fedora-Workstation-34-1.2.aarch64.raw.xz = To: /dev/nvme0n1 .... 11697364992 bytes (12 GB, 11 GiB) copied, 293 s, 39,9 MB/s 0+1347824 registros leídos 0+1347824 registros escritos 11811160064 bytes (12 GB, 11 GiB) copied, 296,682 s, 39,8 MB/s = Writing image complete! = Resizing /dev/nvme0n1 .... Comprobando que nadie esté utilizando este disco en este momento... Correcto Disco /dev/nvme0n1: 476,94 GiB, 512110190592 bytes, 1000215216 sectores Modelo de disco: Samsung SSD 970 PRO 512GB Unidades: sectores de 1 * 512 = 512 bytes Tamaño de sector (lógico/físico): 512 bytes / 512 bytes Tamaño de E/S (mínimo/óptimo): 512 bytes / 512 bytes Tipo de etiqueta de disco: dos Identificador del disco: 0x327db5c6 Situación anterior: Disposit. Inicio Comienzo Final Sectores Tamaño Id Tipo /dev/nvme0n1p1 * 2048 1230847 1228800 600M 6 FAT16 /dev/nvme0n1p2 1230848 3327999 2097152 1G 83 Linux /dev/nvme0n1p3 3328000 23068671 19740672 9,4G 83 Linux /dev/nvme0n1p3: Situación nueva: Tipo de etiqueta de disco: dos Identificador del disco: 0x327db5c6 Disposit. Inicio Comienzo Final Sectores Tamaño Id Tipo /dev/nvme0n1p1 * 2048 1230847 1228800 600M 6 FAT16 /dev/nvme0n1p2 1230848 3327999 2097152 1G 83 Linux /dev/nvme0n1p3 3328000 1000215215 996887216 475,4G 83 Linux Se ha modificado la tabla de particiones. Llamando a ioctl() para volver a leer la tabla de particiones. Se están sincronizando los discos. ERROR: not a btrfs filesystem: /tmp/root mount: /tmp/root: la llamada al sistema mount(2) ha fallado: El fichero ya existe. = No U-Boot files found for none. = Installation Complete! Insert into the none and boot.
This should be fixed in the current release, if the problem persists please reopen.
Metadata Update from @pwhalen: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.