A Linux server fails to boot after a recent change to a custom GRUB script. Instead of loading the operating system, it drops to the grub> prompt. You identify that the prefix variable is pointing to the wrong partition, so you correct the values and load the normal module:
grub> set root=(hd0,1)
grub> set prefix=(hd0,1)/boot/grub
grub> insmod normal
Which single command should you issue next to display the standard GRUB menu and continue booting the system so you can fix the misconfiguration permanently?
After the normal module is loaded, the normal command tells GRUB to enter normal mode and read the configured menu (by default from $prefix/grub.cfg). This restores the usual boot menu, allowing the administrator to select a kernel and boot the OS. The other commands do not achieve this:
boot attempts to start whatever kernel is already loaded, but none has been chosen yet, so it will fail.
configfile /boot/grub/grub.cfg could parse the configuration, but it requires an absolute path that may differ; it is not the documented recovery step and is error-prone if the path is wrong.
exit leaves the GRUB shell (or chain-loads a previous stage), which would simply reboot or drop back to firmware without presenting the menu.
Therefore, normal is the correct command to resolve the immediate GRUB misconfiguration and proceed with booting.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is GRUB and what role does it play in the Linux boot process?
Open an interactive chat with Bash
What does the `set root` and `set prefix` commands do in GRUB?
Open an interactive chat with Bash
What is the difference between the `normal` and `boot` commands in GRUB?
Open an interactive chat with Bash
CompTIA Linux+ XK0-006 (V8)
Troubleshooting
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access