I have a https://endeavouros.com/headless-arm-server-install/ (I believe) on a Raspberry Pi 4b which is not booting any more after a recent system update using
yay. Has anyone else encountered this?
I tried to https://discovery.endeavouros.com/system-rescue/repair-a-non-booting-grub/2021/03/ and https://discovery.endeavouros.com/installation/systemd-boot/2022/12/ but
grub-install yields command not found and
bootctl complains about an
/efi mount not existing altough mounted.
I do not remember, if
bootctl is being used; at least the latter command is found. But is it not typical to get
grub on a headless ARM server? Is there a way to find - when
arch-chroot into it - if it uses
grub? (step 1)
The partition layout is such:
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 411647 409600 200M c W95 FAT32 (LBA)
/dev/sdb2 411648 62333951 61922304 29,5G 83 Linux
gparted says that out of the 200MiB 170MiB is used. Should that point to a size problem and it just needs an older kernel (which?) deleted?
In the meantime, I decided to re-install
enos (server image is not available any more) This is kind of a solution…
It is on my to-do list. Hopefully I can create a new image for this in the next few days.
Sounds good. Just out of curiosity: will
systemd-boot be used as a bootloader?
Any chance to increase the boot partition as I reckon this has caused the failure?
Neither One. On ARM devices, a bootloader takes the place of grub and systemd-boot. The most common one is u-boot and another is tow-boot.
To install EnOS ARM on an ARM device, one downloads a tar image or a bit-by-bit image and burns the image onto a storage device. The boot partition size is determined by the script that creates the images. So one would have to do a git clone to download the script, then edit the script manually before running it to creating an image.
I have never seen the boot size cause any problems on EnOS ARM devices.
I just updated my pi400 and had no issues.
And how full is the boot partition? Thanks
It is using 62 MB out of 268 MB.
This device has been up and running for about 18 months.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.