You are not logged in.
Pages: 1
Hi everyone, I apologize if this doesn't belong here, I'm pretty sure it does.
I recently updated Windows 10 to Windows 11 and it screwed up my grub. I am able to boot once I manually enter everything manually in grub rescue, with the following commands:
set root=(hd0, gpt4)
set prefix=(hd0, gpt4)/boot/grub
insmod normal
normal
but I have to do it every time I boot up my computer now.
I read This post and tried running the following commands
sudo grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=arch_grub --recheck --debug
sudo grub-mkconfig -o /boot/grub/grub.cfg
This is the full output of the first command, but the most notable part is
grub-install: error: /boot doesn't look like an EFI partition.
The second command runs fine but doesn't resolve anything. When I reboot, I have to repeat the grub rescue process again.
Also, I'm not sure if this is also relevant information but when I was installing Arch on my laptop, iwctl would not detect my network device when I was doing the installation, so I got around that by using this Arch GUI installer.
So perhaps it did something differently with grub configurations that I'm not aware of? Nothing seemed out of line compared to my bare installation so I doubt it.
Any help would be appreciated, this issue has been giving me headache for a while now.
Last edited by Hoswoo (2022-01-20 06:34:52)
Offline
sigh... I don't why this happens but I tend to solve problems right after I ask the sometimes.
in my case, the command
sudo grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=arch_grub --recheck --debug
was supposed to be
sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=arch_grub --recheck --debug
I found this information by looking in my /etc/fstab
Offline
Pages: 1