Hi, after I did a BIOS update and a Windows Update, I could no longer boot from my Linux ESP.
However, main problem was that Windows took ESP for itself, so I moved it (it being windows) to a different drive.
Now, trying to repair my ESP and getting everything back to normal; My boots are always failing with /efi can’t be mounted during bootup.
I chrooted like 5 times now but I don’t see what’s wrong.
What I did was: (leaving out everything unrelated, because I deleted the ESP and created a new one instead)
- delete the ESP volume on that drive; created a new vfat volume w/ esp and boot flags set, 500MB
- fired up rescue system
- mounted / and /efi → arch-chrooted
4 # bootctl install and install kernels
- checked my UUIDs were correct
And I don’t see what I was missing. Currently in my rescuesys, now I try and dump everything I’ve got
My symptom is:
I get a boot menu with all (4) Kernels as I was used to; Regular + Zen + fallbacks for each.
So no space issue; then when loading an entry, /efi fails to mount and I get stuck on boot when it says something to the effect of:
“root password or Ctrl + D to continue to boot”
I do NOT use secure boot or fast boot.
What bootctl says about that entry:
Boot Loaders Listed in EFI Variables: Title: Linux Boot Manager ID: 0x0001 Status: active, boot-order Partition: /dev/disk/by-partuuid/982c4491-xxxx-xxxx-xxxx-a77a55882877 File: └─/EFI/systemd/systemd-bootx64.efi
I see my fstab has the /efi listed as UUID not PARTUUID though. I never changed that:
# <file system> <mount point> <type> <options> <dump> <pass> UUID=7XXX-XXX7 /efi vfat defaults,noatime 0 2
I have no clue if they are supposed to match, but I’ll do that now, until I reboot back in my live usb.
that’s this one:
/dev/nvme0n1p1: UUID="7xxx-xxx7" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="XXEFI" PARTUUID="982c4491-xxxx-xxxx-xxxx-a77a55882877"
So, my Windows ESP is now on a different disk, so I don’t expect there to be any more interventions from Windows. /root and /home get mounted before it quits no problem (it seemed) - as I did not get any error or warning.
(maybe the fstab entry solves it; but I need to reboot first)
~# cat /efi/loader/entries/bc33e34161c741e9b5ff224d2170edb0-6.5.9-arch2-1.conf
# Boot Loader Specification type#1 entry # File created by /etc/kernel/install.d/90-loaderentry.install (systemd 254.1-1-arch) title EndeavourOS version 6.5.9-arch2-1 machine-id bc33e34161c741e9b5ff224d2170edb0 sort-key endeavouros-6.5.9-arch2-1 options nvme_load=YES nowatchdog rw root=UUID=4fa508e4-xxxx-xxxx-xxxx-f3e68d59786d systemd.machine_id=bc33e34161c741e9b5ff224d2170edb0 linux /bc33e34161c741e9b5ff224d2170edb0/6.5.9-arch2-1/linux initrd /bc33e34161c741e9b5ff224d2170edb0/6.5.9-arch2-1/initrd
the xxxx786d is also my root in fstab and blkid (UUID, not PARTUUID.)