If it’s going to grub rescue then that’s before it can even get to the grub menu (thus no kernel line at this point). It’s usually easiest to boot to live/rescue ISO and reinstall grub. Sometimes you can manually load grub modules from lib to manually boot from the grub rescue shell to the normal grub shell, but that’s more advanced.
Not true, it’s grub rescue, appears after grub if the OS can’t boot. I’ve encountered this countless times at work over the years in customer environments.
This is false and there’s a simple way to show it.
Remove the grub.cfg file and the system will boot to the grub prompt (not grub rescue). You can manually boot past this by inputting the Linux and initramfs lines.
Then test again but leave grub.cfg intact. Remove an important module like normal.mod and test booting - system will land at grub rescue instead of the normal grub prompt.
Once you test it would be good if you edit your posts so that you aren’t sharing bad information with others
If it’s going to grub rescue then that’s before it can even get to the grub menu (thus no kernel line at this point). It’s usually easiest to boot to live/rescue ISO and reinstall grub. Sometimes you can manually load grub modules from lib to manually boot from the grub rescue shell to the normal grub shell, but that’s more advanced.
Not true, it’s grub rescue, appears after grub if the OS can’t boot. I’ve encountered this countless times at work over the years in customer environments.
This is false and there’s a simple way to show it.
Remove the grub.cfg file and the system will boot to the grub prompt (not grub rescue). You can manually boot past this by inputting the Linux and initramfs lines.
Then test again but leave grub.cfg intact. Remove an important module like normal.mod and test booting - system will land at grub rescue instead of the normal grub prompt.
Once you test it would be good if you edit your posts so that you aren’t sharing bad information with others