Hello all, Currently I have an issue where i cannot boot into my Grub menu.
Its simply gone.
Currently I am running the live USB to trouble shoot an bring it back up.
CH root fix did not help.
I tried the garuda boot options and garuda boot repair and it didnt help
The drop down menus show nothing and give no options to be selected.
CHroot trough terminal is inaccessible at the sudo mount commmand it says its already mounter
and when i run the fix it simply fails
running the ch root from the assistant menu i ran all through to grub install target command and it gives me efi boot manager failed tto register boot entry.
UEFI shows no bootable options for linux.
Live usb though shows the installation is still there
The windows boot manager is present. just not the GRUb menu
I have, before i came ti the live usb, i checked the complete uefi settings. Tried uefi +legacy checked uefi checked secure boot boot sequence.
I would really like to save this install. But if nothing can be done...
The ESP seems to be OK to me... but there is still something unclear from the initial post on what is failing and how, when you try to chroot.
Please execute the following steps from a terminal without trying to chroot with the button (that might be a reason why the mount was failing):
lsblk -f
Careful, -f not /f, then check what is your btrfs partition, e.g. /dev/sda2 in the following. Same for the efi system partition, e.g. /dev/sda1 in the following. Adjust as needed.
sudo mkdir -p /mnt/broken
sudo mount /dev/sda5 /mnt/broken
sudo garuda-chroot /mnt/broken/@
mount /dev/sda1 /boot/efi
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=garuda --recheck
update-grub
Please provide all input and outputs as text. The live USB should normally have a internet connection, so you can enter the forum from there, copy and paste.
PS: Check also in the BIOS that also fast boot is disabled, not only secure boot.
< garuda@garuda in ~ as 🧙 took 11ms
λ sudo mkdir -p /mnt/broken
sudo mount /dev/sda2 /mnt/broken
sudo garuda-chroot /mnt/broken/@
mount /dev/sda1 /boot/efi
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=garuda --recheck
update-grub
mount: /mnt/broken: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error.
==> ERROR: Can't create chroot on non-directory /mnt/broken/@
mount: /boot/efi: mount point does not exist.
Installing for x86_64-efi platform.
grub-install: error: failed to get canonical path of `/boot/grub'.
grub-mkconfig: You must run this as root
Im an idiot i need to adjust the commands first, and identify the correct sda
sh-5.1# ^[[200~ sudo mkdir -p /mnt/broken
sh: $'\E[200~': command not found
sh-5.1# sudo mount /dev/sda2 /mnt/broken
mount: /mnt/broken: mount point does not exist.
sh-5.1# sudo garuda-chroot /mnt/broken/@
sudo: garuda-chroot: command not found
sh-5.1# mount /dev/sda1 /boot/efi
sh-5.1# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=garuda --recheck
Installing for x86_64-efi platform.
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.
sh-5.1# update-grub
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/garuda/theme.txt
Found linux image: /boot/vmlinuz-linux-zen
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-zen.img
Found fallback initrd image(s) in /boot: amd-ucode.img initramfs-linux-zen-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
Detecting snapshots ...
Found snapshot: 2022-01-20 14:34:26 | @/.snapshots/30/snapshot | post | botan fakeroot garuda-update libnma power-profiles-daemon qt5-base qt5-w |
Found snapshot: 2022-01-20 14:34:21 | @/.snapshots/29/snapshot | pre | /usr/bin/pamac-daemon |
Found snapshot: 2022-01-19 19:44:02 | @/.snapshots/28/snapshot | post | alsa-card-profiles archlinux-keyring gnome-control-center gnome-settings |
Found snapshot: 2022-01-19 19:43:46 | @/.snapshots/27/snapshot | pre | pacman -Syu |
Found snapshot: 2022-01-18 19:32:25 | @/.snapshots/26/snapshot | post | nextcloud-client qt5-graphicaleffects qt5-location qt5-quickcontrols2 qt |
Found snapshot: 2022-01-18 19:32:23 | @/.snapshots/25/snapshot | pre | /usr/bin/pamac-daemon |
Found snapshot: 2022-01-18 19:28:03 | @/.snapshots/24/snapshot | post | c-ares code electron13 ripgrep |
Found snapshot: 2022-01-18 19:28:00 | @/.snapshots/23/snapshot | pre | /usr/lib/packagekitd |
Found snapshot: 2022-01-18 19:27:34 | @/.snapshots/22/snapshot | post | godot libwslay mbedtls miniupnpc |
Found snapshot: 2022-01-18 19:27:32 | @/.snapshots/21/snapshot | pre | /usr/lib/packagekitd |
Found 10 snapshot(s)
Unmount /tmp/grub-btrfs.k6eCeiMe8x .. Success
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
sh-5.1# ~
sh: /root: Is a directory
No, please, the text above must be executed from a "normal" terminal session in the live USB, not after chrooting.
Exit from chroot screen and reboot from the live ISO, then re-execute the steps from a terminal (do not chroot, that step is done with those steps).
It's getting more and more confusing.
If you're still in chroot type exit, to return to the normal USB terminal, then sudo umount /dev/sda5
Then try to repeat, starting from sudo mount /dev/sda5 /mnt/broken ( /mnt/broken should already exist) providing input and outputs line by line (not all together).
Even more, I’d try again to sudo umount /dev/sda5 and repeat from sudo mount /dev/sda5 /mnt/broken (if /mnt/broken already exists), line by line (to get any possible error message).
The terminal prompt should be initially something like garuda@garuda, e.g.:
garuda@garuda in ~ took NNms
╰─λ sudo mkdir -p /mnt/broken
╭─garuda@garuda in ~ took NNms
╰─λ sudo mount /dev/sda5 /mnt/broken
╭─garuda@garuda in ~ took NNms
╰─λ sudo garuda-chroot /mnt/broken/@
sh-5.1#
garuda@garuda in ~ as 🧙 took 19ms
[🔴] × sudo umount /dev/sda5
umount: /mnt/broken: target is busy.
garuda@garuda in ~ as 🧙 took 15ms
[🔴] ×
At this point, I am willing to stop taking up your time. Either I am not doing it right, being a fresh user and simply reinstall. if that would be a better option ?
