Yesterday I updated my system, today it didn't boot. I used the cool snapshot feature and booted my PC using an old snapshot. After I restored the state, I restarted the PC. Now it is stuck with an error I've never heard of.
error: symbol 'efi_wrap_1' not found.
Entering rescue mode...
grub rescue>
I already looked at few solutions including the one on this forum, but I couldn't solve the issue.
I created a bootable USB, but it doesn't load either. When I boot from there, it writes unknown filesystem.
I would like to get back my computer with all my files. I appreciate all help.
Could you try creating the live USB using ventoy this time? Also redownload the ISO it might be corrupt. Then chroot into your system and reinstall grub following this post:
After that you can follow this thread to prevent being stuck at the loading initramfs screen following the update
Okay, Ventroy made it work. Now I am inside the USB booted Garuda Linux.
I started to follow the post you linked about Grub reinstall, but I noticed something. In the Garuda Welcome there are few interesting things: "Chroot", "Garuda Boot Repair", "Garuda Boot Options". Aren't these existing solutions to my problem?
Till you answer, I am going to follow the post you linked.
I am confused at the step "In case you want to install the bootloader". I suppose I need this because I can't boot my PC. How do I know if my system is installed in UEFI or Legacy BIOS/MRB?
I am stuck at " Select the proper $esp partition (...) and mount it inside chroot".
I try to run the mount, but it returns: "/dev/sda is mounted or mount is already busy"
CONTEXT: I have two disks in my PC: one that is an SSD and has linux on it, one that is a HDD and has all kinds of files on it. At step "Mount and chroot into the installed system " I used one of the partition of my SSD which wrote btrfs (/dev/sda2). At step "Find existing $esp partitions if more than one" the command provided 2 outputs: one is my ssd (/dev/sda), the other one is the usb I am booted from right now.
Okay…now it works. Seems to be that I tried simply “sda” not “sda1”. Why “sda” though? If parted -l | grep -iE "^Disk /|esp" | grep -B1 esp shows simply “sda”?
I am not okay with these disks and all in linux. After my PC is fully back, I am going to study this. I am so sorry for this misunderstanding!
sda is the name of the disk and sda1 is the name of the partition on which your bootloader resides. Perform the next steps to install grub and inform if something errors out
After exiting I saw this on the terminal: umount: /mnt/broken/@: target is busy.
Is this an error (umount couldn't execute fully for example because target is busy), or it is OK and I can look over it?