You are not logged in.

#1 2021-10-30 19:59:22

george.angel
Member
Registered: 2021-10-30
Posts: 2

[SOLVED] Unable to start after re-creating /boot EFI partition

Caveat, I can boot, but only if I interrupt the start-up process, and select my disk from the "boot menu".

What happened was, I used archinstall to setup Arch, but ran into this bug: https://github.com/archlinux/archinstall/issues/591 - my /boot filesystem was too small to accommodate fwupd.

I tried following https://superuser.com/a/1289122 - to recreate /boot partition and end up with a filesystem that occupies all 512MB.

I couldn't update the UUID in fstab straight away (it didn't show up different straight after being recreated), but after a failed boot and entering recovery mode, that bit was solved.

Now if I try to start up normally, I end up on a Windows looking screen with some text, which includes;

Your device/PC needs to be repaired

File: \\Windows\system32\winload.efi
Error code: 0xc000000e
$ efibootmgr -v
BootCurrent: 0019
Timeout: 2 seconds
BootOrder: 0001,0000,0010,0011,0012,0013,0017,0018,0019,001A,001B,001C,001D,001E
Boot0000* Windows Boot Manager  HD(1,GPT,450a9c67-5871-4327-bdbf-12cd09b0d0de,0x800,0x100000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...M................
Boot0001* Linux Boot Manager    HD(1,GPT,77fe3444-b72d-43f5-af09-222fe07a73fc,0x800,0x100000)/File(\EFI\systemd\systemd-bootx64.efi)
Boot0010  Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011  Boot Menu     FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0012  Diagnostic Splash Screen      FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0013  Lenovo Diagnostics    FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
Boot0014  Startup Interrupt Menu        FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
Boot0015  Rescue and Recovery   FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
Boot0016  MEBx Hot Key  FvFile(ac6fd56a-3d41-4efd-a1b9-870293811a28)
Boot0017* USB CD        VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot0018* USB FDD       VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0019* NVMe0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400)
Boot001A* ATA HDD0      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot001B* USB HDD       VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot001C* PCI LAN       VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot001D  Other CD      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a35406)
Boot001E  Other HDD     VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f606)
Boot001F* USBR BOOT CDROM       PciRoot(0x0)/Pci(0x14,0x0)/USB(11,1)
Boot0020* USBR BOOT Floppy      PciRoot(0x0)/Pci(0x14,0x0)/USB(11,0)
Boot0021* ATA HDD       VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)
Boot0022* ATAPI CD      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)

Torxed pointed out:

The PARTUUID might have changed, or whatever equivalent Windows uses on their partitions to find their boot loader.

and a comment on SO - https://superuser.com/questions/1230741 … 27_1289122

It seems like I need to update the EFI Windows bit with the reference to the newly created partition? I'm a bit lost where do go next from here.

As always, any help is highly appreciated.

Thank you.

Last edited by george.angel (2021-10-31 09:32:40)

Offline

#2 2021-10-31 09:32:19

george.angel
Member
Registered: 2021-10-30
Posts: 2

Re: [SOLVED] Unable to start after re-creating /boot EFI partition

Alright, resolution was quite simple.

Looking at:

$ efibootmgr -v

I can see that the first item in the boot order is:

Boot0001* Linux Boot Manager    HD(1,GPT,77fe3444-b72d-43f5-af09-222fe07a73fc,0x800,0x100000)/File(\EFI\systemd\systemd-bootx64.efi)

but if I check:

$ blkid
/dev/nvme0n1p1: UUID="E91E-AF06" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="450a9c67-5871-4327-bdbf-12cd09b0d0de"
/dev/nvme0n1p2: UUID="daeb53cb-1fe3-44d8-93f2-6153259e2df4" TYPE="crypto_LUKS" PARTLABEL="primary" PARTUUID="370473ed-9a82-4bbb-912a-87c47f819873"

We can see that PARTUUID doesn't not match.

I did a

$ sudo bootctl update

which is what I think (I didn't check at the time) created a new boot entry:

$ efibootmgr -v
BootCurrent: 0019
Timeout: 2 seconds
BootOrder: 0001,0000,0010,0011,0012,0013,0017,0018,0019,001A,001B,001C,001D,001E,0002
Boot0000* Windows Boot Manager  HD(1,GPT,450a9c67-5871-4327-bdbf-12cd09b0d0de,0x800,0x100000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...M................
Boot0001* Linux Boot Manager    HD(1,GPT,77fe3444-b72d-43f5-af09-222fe07a73fc,0x800,0x100000)/File(\EFI\systemd\systemd-bootx64.efi)
Boot0002* Linux Boot Manager    HD(1,GPT,450a9c67-5871-4327-bdbf-12cd09b0d0de,0x800,0x100000)/File(\EFI\systemd\systemd-bootx64.efi)
...

Now that I can see the correct boot entry that matches  PARTUUID to my /boot, was to set it to be the first in the boot order:

$ sudo efibootmgr -o 0002,0001,0000,0010,0011,0012,0013,0017,0018,0019,001A,001B,001C,001D,001E

That did it for me.

Offline

Board footer

Powered by FluxBB