utmapp
Boot partition is too small in Archlinux Image from Gallery.
I'm not sure if the OS images in the Gallery are maintained in this repo.
I downloaded the Archlinux image from the gallery and it runs fine, but when running the image for the first time, I updated with pacman -Syu. The linux-firmware package is one of the updated packages and outputs this message:
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
-> Early uncompressed CPIO image generation successful
gzip: stdout: No space left on device
bsdtar: Write error
bsdtar: Write error
==> ERROR: Initcpio image generation FAILED: 'bsdtar (step 1)' reported an error
error: command failed to execute correctly
Then, I installed gnome and every time I log in I get a notification from disk usage analyzer complaining that the /boot partition has 0 bytes available.
I'm having the same issue -- if you figured out a solution @rvega I would love ot hear about it! thank you.
A workaround is: install the arch instance from the gallery normally. Then boot the virtual machine with a “live cd” image from any arm64 distribution. I used Ubuntu. From there, use gparted to move and resize the partitions.
A workaround is: install the arch instance from the gallery normally. Then boot the virtual machine with a “live cd” image from any arm64 distribution. I used Ubuntu. From there, use gparted to move and resize the partitions.
thanks, this worked -- I downloaded the current Ubuntu desktop image, added the ISO as the source of my CD drive, and then spent a bit of time shifting the main partition (/dev/vd2) "right", to clear space for /boot (/dev/vda1) to grow. And yes it does feel like something the developers of the gallery image should do, but I can't see how to submit a suggestion for that.
Given that this is an image run in a VM for ephemeral purposes, I doubt I'll ever need a fallback image so I went a slightly different route: edited /etc/mkinitcpio.d/linux-aarch64.preset and removed "fallback" and deleted the fallback files in /boot/ ...
Given that this is an image run in a VM for ephemeral purposes, I doubt I'll ever need a fallback image so I went a slightly different route: edited
/etc/mkinitcpio.d/linux-aarch64.presetand removed "fallback" and deleted the fallback files in /boot/ ...
This seems much simpler than my workaround. I’ll try this next time :)
A workaround is: install the arch instance from the gallery normally. Then boot the virtual machine with a “live cd” image from any arm64 distribution. I used Ubuntu. From there, use gparted to move and resize the partitions.
I wonder which iso all live are amd64 and don't boot :-( Sad we don't have the doc on how this VM was made from scratch
A workaround is: install the arch instance from the gallery normally. Then boot the virtual machine with a “live cd” image from any arm64 distribution. I used Ubuntu. From there, use gparted to move and resize the partitions.
I tried using an ubuntu arm64 iso, but the GUI just wont load, is there a way to run gparted without gui
I tried using an ubuntu arm64 iso, but the GUI just wont load, is there a way to run gparted without gui
parted is the non-graphical version
parted can't move partitions; the move command was removed long ago. You can resize the 2nd partition with:
sudo e2fsck -f /dev/vda2
sudo resize2fs /dev/vda2 8600M
sudo parted /dev/vda
But then there's nothing to do. I've spent a while trying different combinations of fdisk/sfdisk/parted/resize2fs commands, but always ended up with a corrupt image.
I also couldn't find a way to get a GUI.
