this post was submitted on 17 Mar 2025
618 points (99.2% liked)
linuxmemes
23907 readers
1708 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
3. Post Linux-related content
sudo
in Windows.4. No recent reposts
5. 🇬🇧 Language/язык/Sprache
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Important Edit
The information below applies to emergency mode boot when grub is intact but OS isn’t booting. It doesn’t apply to grub rescue. Sorry about that folks, I screwed up here and don’t wanna misinform.
—————-
Protip: If you see this error, press”e” on grub boot to edit your commands and add the following to the end of the kernel line in grub:
Then boot.
Fixes the issue like 90% of the time.
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
Well shit. You’re right, I’m mixing up grub rescue and emergency mode. Yeah, you would need a USB rescue disk to fix this most likely.
My bad, I’ll update the original comment to avoid confusion.
All good! Thanks for updating.