Arch Linux

elfomelo

Member

Registered: 2011-10-27

Posts: 47

Re: [Solved]Trying to recover after a broken update, pacman can't resol...

I gave up and am doing a fresh install. Will mark solved if it works

elfomelo

Member

Registered: 2011-10-27

Posts: 47

Re: [Solved]Trying to recover after a broken update, pacman can't resol...

New layer of problems. If you think I need to start a new topic, please, let me know.

I rebooted the system and started a new install. However, now I can't install a boot manager.

grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB

results in

Could not delete variable: invalid argument
grub-install: error: efibootmgr failed to register the boot entry: Block device required

Then I tried systemd-boot but

bootctl install

gives

Failed to write 'LoaderSystemToken' EFI variable: Input/output error

From a quick troubleshooting I believe the efi partition is correctly mounted on boot, judging by 'ls', and the system is booted in efi mode, "ls /sys/firmware/efi/efivars" exists in the iso and in the chroot. I'm stumped now

GaKu999

Member

From: US/Eastern

Registered: 2020-06-21

Posts: 696

Re: [Solved]Trying to recover after a broken update, pacman can't resol...

New layer of problems. If you think I need to start a new topic, please, let me know.

I rebooted the system and started a new install. However, now I can't install a boot manager.

grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB

results in

Could not delete variable: invalid argument
grub-install: error: efibootmgr failed to register the boot entry: Block device required

Then I tried systemd-boot but

bootctl install

gives

Failed to write 'LoaderSystemToken' EFI variable: Input/output error

From a quick troubleshooting I believe the efi partition is correctly mounted on boot, judging by 'ls', and the system is booted in efi mode, "ls /sys/firmware/efi/efivars" exists in the iso and in the chroot. I'm stumped now

Definitely a new topic...

But this seems like UEFI derp...
You can use the fallback boot path '/boot/EFI/BOOT/BOOTX64.EFI'
So that will work even if creating a bootloader entry is impossible...

For GRUB2 you need to add '--no-nvram --removable'

---

My repos • Some snippets

Heisenberg might have been here.