You are not logged in.
Hi, sorry if it's not the right place to ask.
The day before yesterday, I ran pacman -Syu, and when I tried to reboot my system I was met with the bios. I've tried to downgrade on a live usb (I had to use the --overwrite flag for qt5-base, there was the error file exists in filesystem) which did not solve the problem so I updated the system today and it still does the same. I've searched for the problem online and found nothing. Are there any interesting logs to check? I use systemd-boot.
Last edited by Brokemyinstall (2021-10-09 07:44:36)
Offline
There's nothing usable here, what doesn't boot? Do you not even get to systemd-boot or does an entry selected in systemd-boot not boot? If you don't even get to systemd-boot you need to recheck your EFI NVRAM entries with efibootmgr or generally the bootable entries menu of your firmware? Which firmware is this? Which mainboard vendor?
Offline
I don't even get to systemd-boot. The boot entries are just fine, I've checked that already. I'm on an asus n751jx, firmware version 2.15.1236.
Offline
Check the available entries with efibootmgr/post the output. How does the free space on your /boot respectively your ESP look like, did you run out of space on a kernel update? To post outputs from a terminal/a live disk see: https://wiki.archlinux.org/title/List_o … n_services
Offline
The output form efibootmgr is http://ix.io/3BdS
My boot partition has 704MB free (32% full). I don't have an efi partition, all is on the boot partition.
Offline
Your /boot is your efi partition and there's no entry for systemd-boot, rerun the relevant bootctl command to reinstall systemd-boot from the chroot.
Offline
That wasn't the problem but put me on the right track.
Linux was somehow missing, after reinstalling it everything worked fine. Thanks for the help.
Offline
Make sure your /boot partition is actually mounted when you update your system otherwise you'll just repeat this the next time
Offline