( 8/10) Checking for .pacnew and .pacsave files…
.pac* files found:
/etc/default/grub.pacnew
/etc/default/grub-btrfs/config.pacnew
Any possibility changes to grub & grub-btrfs/config could be an issue?
( 8/10) Checking for .pacnew and .pacsave files…
.pac* files found:
/etc/default/grub.pacnew
/etc/default/grub-btrfs/config.pacnew
Any possibility changes to grub & grub-btrfs/config could be an issue?
I’m really sorry guys, that was my fault.
This past week I have been using a live Garuda session to repair grub in two simultaneously installed Debian system that have two different kernels and kept overwriting each others grub. When you are chrooted into a system you use whatever the native command is, so I have been running apt reinstall grub-efi-amd64 and somehow it must have gotten stuck in my head.
My comment above had a few steps listed out, including that command. I quickly realized the mistake I had made and deleted the whole piece out of the comment, but waduhektemp must have already spotted the note and ran with it.
@waduhektemp, I’m sorry about that–my mistake. ![]()
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-zen.img
You see, there is a ^ instead of a space.
I am thinking this might be a red herring. In the original post, waduhektemp mentioned they had written out the error message manually (instead of copy/paste); it is possible the mysterious carrot symbol is a simple typo.
One thing I did spot is in one of the pastebin outputs above (the one where grub is successfully installed), update-grub is added to the end of the grub-install command.
I’m guessing the whole chunk was copied out of this command box as one piece:
This should be two commands. So:
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=garuda --recheck
After that command finishes, then run as a separate command:
update-grub
The way it was run together, I do not think it took the update-grub and so the grub configs weren’t correctly modified.
That fixed the issue thanks everyone for the support you guys have been incredibly helpful. @BluishHumility no worries it didn't cause any issues.
I'm gonna have to look into ways of lessening the chance of this happening again in the future.
I did copy the very final log
Visit this link to see the note. Giving the URL to anyone allows them to access the note, too.
Glad to hear you got things fixed up.
Try to mark an individual post that is closest to your final solution.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.