I’m having the same issue as @ajgringo619 did, but it is not at all clear to me from reading the thread how to fix the issue. Can anyone sum it up in simple steps? I’m using BTRFS if that matters.
1 Like
My issue was completely self-inflicted. I changed the default bootloader ID back in April of last year due to having a triple-boot with (2) other EOS installs, just didn’t see a problem until one of the core GRUB modules was updated (don’t know which one).
1 Like
I see. How did you begin troubleshooting? Even just doing ls HD0 in GRUB rescue locks up the system.
At first, all I did was downgrade grub. But @dalto figured out that my pacman hooks were installing the updated files into a different directory, hence the boot errors. Your issue is sounding more like the Arch forum post I linked to.
1 Like
I think you need to use a live usb, chroot to your system and reinstall the grub package to have all its bits and pieces. After that a grub-install followed perhaps by a grub update. There is an article in EndeavourOS wiki about how to rescue a system with Grub problem.
1 Like
Between te lines, is it possible to check bios and look if you got another entry…maybe you can boot through that. On telegram had a situation uefi os entry windows grub messed but could boot through bios…
Otherwise check btrfsbpart to mount .https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/
Are you not able to revert to a previous snapshot? Otherwise i would do as @cactux said in post #5 to arch-chroot , reinstall grub and run the update grub command.
Are you not able to revert to a previous snapshot?
No, because I cannot access the GRUB menu.
i would do as @cactux said in post #5 to arch-chroot , reinstall grub and run the update grub command.
It’s looking like this is what I’ll have to try next; I’m hesitant to chroot into the system as it seems complicated on BTRFS (I’ve done it once before and promptly forgot how), but needs must.
I’m a bit annoyed because I haven’t done anything interesting with this system at all; it just sits by the TV and I use it to play video games haha.
1 Like
No it’s not complicated. Look under mount needed partitions & BTRFS filesystem installs.
https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/
Note: Not all subvolumes need to get mounted to use arch-chroot it needs mainly the / (@) if you only want to repair grub per example
1 Like
So, here’s what I’ve done so far: (not 100% accurate terminal output as I’m typing on my phone)
First I boot into a live ISO.
sudo lsblk - f returns:
sda1 vfat FAT32
sda2 btrfs endeavouros
So I then mount sda2:
sudo mount -o subvol=@ /dev/sda2 /mnt
Then my “ESP”:
sudo mount /dev/sda1 /mnt/boot/efi
(Fstab shows /boot/efi, but attempting to mount here shows an error: mount point does not exist)
Then I use arch-chroot:
sudo arch-chroot /mnt
But now ls /home returns nothing. Any ideas where I went wrong?
1 Like
OK, so it looks like the ls /home output is a non-issue. Was able to run yay successfully, but:
grub-install returns `error: install device not specified
And grub-install --target=86_64-efi --efi-directory=/boot/efi returns:
EFI variables are not supported on this system.
EFI variables are not supported on this system.
grub-install: error: efibootmgr failed to register the boot entry: No such file or directory.
grub-install --target=86_64-efi /dev/sda1 returns the same as above.
1 Like
OK, I have now run:
pacman -S grub
grub-install
grub-mkconfig -o /boot/grub/grub.cfg
And the issue is still present.
1 Like
No, I only have UEFI OS in BIOS - nothing else.
I did find another entry in the boot override section. It boots succesfully. Now when I run grub-install I get error: disk 'hostdisk//dev/sda1' not found.
1 Like
Unfortunately this didn’t solve the issue.
efibootmgr
What is the output?
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0004,0000,0006,0007,0001,0005
Boot0000* endeavouros HD(1,GPT,00c8d36a-069e-4e52-975f-9cf7da0a7b24,0x1000,0x1f4000)/\EFI\ENDEAVOUROS\GRUBX64.EFI
Boot0001 Hard Drive BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0200)0000474f00004e4fc9000000080000008b004b0049004e004700530054004f004e0020005300410034003000300053003300370031003200300047000000050109000200000000010416008b12e85cec2cf040837280640e3dc85802007fff040002010c00d041030a0000000001010600030101010600010003120a000000ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce63000350032003000420036003700370041003700300030003900340032004100200020002000200000007fff04000000424f00004e4fbd000000080000008b004300540032003000300030004200580035003000300053005300440031000000050109000200000000010416008b12e85cec2cf040837280640e3dc85802007fff040002010c00d041030a0000000001010600030101010600010003120a000400ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce63300320032003000360045004400390039003000300038002000200020002000200020002000200000007fff04000000424f
Boot0004* UEFI OS HD(1,GPT,00c8d36a-069e-4e52-975f-9cf7da0a7b24,0x1000,0x1f4000)/\EFI\BOOT\BOOTX64.EFI0000424f
Boot0005 USB KEY BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0b00)0000474f00004e4fb1000000080000006f00470065006e006500720069006300200046006c0061007300680020004400690073006b00200038002e00300037000000050109000200000000010416008b12e85cec2cf040837280640e3dc8580b007fff040002010c00d041030a000000000101060001070101060003000305060001007fff040001042600ef47642dc93ba041ac194d51d01b4ce64600380045003700450035003800420000007fff04000000424f
Boot0006* UEFI: Generic Flash Disk 8.07 PciRoot(0x0)/Pci(0x7,0x1)/Pci(0x0,0x3)/USB(1,0)/CDROM(1,0x593ce0,0x58840)0000424f
Boot0007* UEFI: Generic Flash Disk 8.07, Partition 2 PciRoot(0x0)/Pci(0x7,0x1)/Pci(0x0,0x3)/USB(1,0)/HD(2,MBR,0x394f561e,0x593ce0,0x58800)0000424f
Can you test this boot option?
1 Like
So I managed to find a boot option in the BIOS, which I think is Boot0000, that allows me to boot.
The option labeled UEFI OS in the BIOS is the one that goes straight to GRUB rescue. When I run grub-install from my current boot I get error: disk 'hostdisk//dev/sda1' not found.
1 Like
Change the boot order in BIOS to have 0000 first.
1 Like
For some reason, it isn’t available in the boot order selector, only in the “Boot Override” section?
I had to go into “Boot\UEFI Hard Disk Drive BBS Priorities” and swap UEFI OS with endeavouros. How bizarre. Any idea why this happened out of the blue?
I very much appreciate your help: thank you!
2 Likes