You are not logged in.

#1 2020-02-23 10:00:54

Aromatix
Member
Registered: 2019-03-25
Posts: 13

[SOLVED]Wrong partition name in efi bootentry; unable to boot

I have an existing Arch installation and used unused diskspace for Windows. It looks like, that during win installation my partition containing the luks container was renamed from sda7 to sda4 (can that happen?). I was using efi before the installation as well and my bootentry assumes the cryptdevice is /dev/sda7, therefore I can no longer boot into Arch.
I can think of two options now:
- rename the partition to sda7, i've read that this is a bad idea.
- edit the bootentry / add a new bootentry

I tried the second option from a live environment. Mounted the partitions and chrooted into my old system, but I cant use efibootmgr (it says there are no efi vars available).
Is there another option I oversaw or a way to make the second option work?

Last edited by Aromatix (2020-02-23 19:13:27)


I am here to learn. Feel free to message me about anything that might be interesting to me! Thanks wink

Offline

#2 2020-02-23 11:13:07

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,427

Re: [SOLVED]Wrong partition name in efi bootentry; unable to boot

You should not ever rely on /dev/sdXY anything for the purposes of booting and early mounting in fstab: https://wiki.archlinux.org/index.php/Pe … ice_naming

What are you using for booting? Most bootloaders allow to edit the entry before booting, or do you explicitly use EFISTUB?

Make sure you boot the stick in UEFI mode. If you managed to install in UEFI mode you should be able to get it booting in UEFI mode. When you select the stick to boot from there are usually two entries, you must select the one that entails UEFI boot.

Offline

#3 2020-02-23 19:13:09

Aromatix
Member
Registered: 2019-03-25
Posts: 13

Re: [SOLVED]Wrong partition name in efi bootentry; unable to boot

"Making sure you boot the stick in UEFI mode" did it.
I thought I am not booting in UEFI mode, since there was no /efi partition mounted. That is the wrong way to check it!
The right way is to check for the content of /sys/firmware/efi/efivars/ with:

ls /sys/firmware/efi/efivars/

From what I understand, if there is output, than ur system is booted in UEFI mode.

After that I was able to download efibootmgr on the live env and create a new bootentry.

p.s. I use UUID for naming in fstab. But last time I tryed I was not able to use UUID for the cryptdevice option of an UEFI bootentry, e.g.:

efibootmgr [...] -u "cryptdevice=UUID=xxxx-xxxx[...]" 

was not able to boot the system.

UPDATE:

efibootmgr [...] -u "cryptdevice=UUID=xxxx-xxxx[...]" 

works, must have been typo last time

Last edited by Aromatix (2020-02-24 07:59:36)


I am here to learn. Feel free to message me about anything that might be interesting to me! Thanks wink

Offline

Board footer

Powered by FluxBB