Skip to main content ↑ ↓
Topic: Broken GRUB + EFI (Read 630 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Broken GRUB + EFI

Hey Everyone,

I think I got caught up in some openssl / cryptsetup + kernel updates that hosed my booting of LUKS volumes. :( I've seen some of the forum posts but mine (unfortunately) are not quite those issues.

After a recent update which only updated linux to latest (plus some inconsequential pkgs) reboot got **very** slow, like 2-3 minutes and during openrc start I was getting spammed by messages like 'waiting for dmcrypt' after every service tried to start. The end result was a stuck xorg but I could pop over to tty1 and log in via console.

After reading some of the posts re: openssl and cryptsetup and whirlpool + serpent I tried to downgrade the kernel as one OP stated they believe the crypto modules were taken out of kernel and provided as module. Another issue I saw was some warnings from grub stating there were unknown commands.

I proceeded to modify `/etc/default/grub` to trim down the Kernel command line to minimal example and then downgraded kernel package thinnking it would trigger a grub rebuild etc. It did and that killed my boot. :( That resulted in a prompt at boot to enter the passphrase for my crypt key-file located on encrypted root volume (which is normal) but it would halt right after that, no progression of bootup.

I booted an artix rescue iso and walked through steps rescue and fix grub. I *may* have forgotten to mount the efi volume but after that and now current state is after inserting passcode to encrypted volume (normal) I get an error in text right after the "passcode :" line on grub boot similar to error in grub_malloc_debug. Forum posts suggest there is an error in EFI.

So
- I've booted from artix rescue iso and unlocked volumes using key-file
- mounted root and efi volumes into the right mount points and used artix-chroot
- reverted to grub as working days ago
- forced 'upgrade' of the linux kernel again to latest
- This triggers mkinitcpio +grub hook as usual. I've not modified these hooks.

Grub still errors in grub_debug_malloc :'''(

I've uploaded some pastebin output if anyone can help! The LUKS are the nvme address, You can compare what's what from lsblk but 0.1.2 is ROOT, 0.1.3 is SWAP, 2.1.1 is OPT, and 1.1.1 is /home/me

Address - command output
https://pastebin.com/frzPi5K0   -  pacman_Syu
https://pastebin.com/sqtLkLsJ   -  cat_etcDefaultGrub
https://pastebin.com/R49X6vQK   -  ls_Boot_Grub
https://pastebin.com/nnbwr5Gj   -  LUKS-2.1.1
https://pastebin.com/KExWnYcb   -  LUKS-1.1.1
https://pastebin.com/Yguztq5L   -  LUKS-0.1.3
https://pastebin.com/dMkHkLaC   -  LUKS-0.1.2
https://pastebin.com/CtDcRSDH   lsblk

If you can help restore grub and then boot cryptsetup / dmcrypt correctly I'd be so grateful!

-V