My machine always reboot into the GRUB prompt instead of GRUB menu
I got a problem that is after rebooting grub CLI always appears instead of grub menu. For me the problem is not being unable to boot into any kernels (it is simple: type exit and enter twice do the job and the grub menu reappear). What I want is to boot into grub menu instead of CLI. Is there any way to fix this?
I'm using Ubuntu 18.04 with GRUB2.
grub2 dual-boot grub reboot
asked May 7 '18 at 9:49
Aiden BheAiden Bhe
62
add a comment |
I got a problem that is after rebooting grub CLI always appears instead of grub menu. For me the problem is not being unable to boot into any kernels (it is simple: type exit and enter twice do the job and the grub menu reappear). What I want is to boot into grub menu instead of CLI. Is there any way to fix this?
I'm using Ubuntu 18.04 with GRUB2.
grub2 dual-boot grub reboot
asked May 7 '18 at 9:49
Aiden BheAiden Bhe
62
Once you boot, runsudo update-grub
– defalt
May 12 '18 at 13:26
add a comment |
I got a problem that is after rebooting grub CLI always appears instead of grub menu. For me the problem is not being unable to boot into any kernels (it is simple: type exit and enter twice do the job and the grub menu reappear). What I want is to boot into grub menu instead of CLI. Is there any way to fix this?
I'm using Ubuntu 18.04 with GRUB2.
grub2 dual-boot grub reboot
asked May 7 '18 at 9:49
Aiden BheAiden Bhe
62
I got a problem that is after rebooting grub CLI always appears instead of grub menu. For me the problem is not being unable to boot into any kernels (it is simple: type exit and enter twice do the job and the grub menu reappear). What I want is to boot into grub menu instead of CLI. Is there any way to fix this?
I'm using Ubuntu 18.04 with GRUB2.
grub2 dual-boot grub reboot
grub2 dual-boot grub reboot
asked May 7 '18 at 9:49
Aiden BheAiden Bhe
62
asked May 7 '18 at 9:49
Aiden BheAiden Bhe
62
edited May 7 '18 at 11:13
Aiden Bhe
asked May 7 '18 at 9:49
Aiden BheAiden Bhe
62
asked May 7 '18 at 9:49
Aiden BheAiden Bhe
62
asked May 7 '18 at 9:49
Aiden BheAiden Bhe
62
62
Once you boot, runsudo update-grub
– defalt
May 12 '18 at 13:26
add a comment |
Once you boot, runsudo update-grub
– defalt
May 12 '18 at 13:26
Once you boot, run
sudo update-grub– defalt
May 12 '18 at 13:26
Once you boot, run
sudo update-grub– defalt
May 12 '18 at 13:26
add a comment |
2 Answers
2
active
oldest
votes
I had the same issue apart from that it was booting not at all.
Reason: My fresh install of Ubuntu 18.04, 17.10 and Mate 18.04 had all put the wrong uuid in /boot/efi/EFI/ubuntu/grub.cfg.
Version 1 (grub-cmd):
From grub shell, find root folder by peeking into the outputs of ls (e.g. ls (hd0,gpt2)/) and make sure to know on which partition your system was installed! For me, it was sda2 since ESP is recommended to be the first.
set root=(hd0,gpt2)
linux /boot/vmlinuz-number-generic root=/dev/sda2
initrd /boot/initrd.img-number-generic
boot
If booting is successful now, you can get your uuid's (not partuuid) by typing blkid and verify that the correct one is noted in /boot/efi/EFI/ubuntu/grub.cfg.
For me:
search.fs_uuid <uuid> root hd0,gpt2
...
Version 2 (install-stick):
If you happen to have a bootable linux-stick, you can also boot that, mount your ESP and change the uuid there:
# Create folder to mount ESP
mkdir /tmp/esp
# Mount ESP (assuming sda1) to esp
sudo mount /dev/sda1 /tmp/esp
# Get UUID's of devices
sudo blkid
# Ensure correct `uuid` is set in `/tmp/esp/efi/EFI/ubuntu/grub.cfg`
reboot
answered Jul 10 '18 at 14:41
SuuuehgiSuuuehgi
48549
add a comment |
You say you can get into your Ubuntu install, so it should be simple enough to update/reinstall grub and see if that fixes the issue.
First, try simply using sudo update-grub if you haven't already, then reboot to check if that fixed it.
If this doesn't work, try manually reinstalling it with sudo grub-install /dev/sd## (replace ## with the current location of grub). This should be enough to reset any files that might be causing your issue.
Note: if you customized your grub install originally, this may reset those changes.
answered Jan 27 at 4:30
Jwalbrecht2000Jwalbrecht2000
11
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f442272%2fmy-machine-always-reboot-into-the-grub-prompt-instead-of-grub-menu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I had the same issue apart from that it was booting not at all.
Reason: My fresh install of Ubuntu 18.04, 17.10 and Mate 18.04 had all put the wrong uuid in /boot/efi/EFI/ubuntu/grub.cfg.
Version 1 (grub-cmd):
From grub shell, find root folder by peeking into the outputs of ls (e.g. ls (hd0,gpt2)/) and make sure to know on which partition your system was installed! For me, it was sda2 since ESP is recommended to be the first.
set root=(hd0,gpt2)
linux /boot/vmlinuz-number-generic root=/dev/sda2
initrd /boot/initrd.img-number-generic
boot
If booting is successful now, you can get your uuid's (not partuuid) by typing blkid and verify that the correct one is noted in /boot/efi/EFI/ubuntu/grub.cfg.
For me:
search.fs_uuid <uuid> root hd0,gpt2
...
Version 2 (install-stick):
If you happen to have a bootable linux-stick, you can also boot that, mount your ESP and change the uuid there:
# Create folder to mount ESP
mkdir /tmp/esp
# Mount ESP (assuming sda1) to esp
sudo mount /dev/sda1 /tmp/esp
# Get UUID's of devices
sudo blkid
# Ensure correct `uuid` is set in `/tmp/esp/efi/EFI/ubuntu/grub.cfg`
reboot
answered Jul 10 '18 at 14:41
SuuuehgiSuuuehgi
48549
add a comment |
I had the same issue apart from that it was booting not at all.
Reason: My fresh install of Ubuntu 18.04, 17.10 and Mate 18.04 had all put the wrong uuid in /boot/efi/EFI/ubuntu/grub.cfg.
Version 1 (grub-cmd):
From grub shell, find root folder by peeking into the outputs of ls (e.g. ls (hd0,gpt2)/) and make sure to know on which partition your system was installed! For me, it was sda2 since ESP is recommended to be the first.
set root=(hd0,gpt2)
linux /boot/vmlinuz-number-generic root=/dev/sda2
initrd /boot/initrd.img-number-generic
boot
If booting is successful now, you can get your uuid's (not partuuid) by typing blkid and verify that the correct one is noted in /boot/efi/EFI/ubuntu/grub.cfg.
For me:
search.fs_uuid <uuid> root hd0,gpt2
...
Version 2 (install-stick):
If you happen to have a bootable linux-stick, you can also boot that, mount your ESP and change the uuid there:
# Create folder to mount ESP
mkdir /tmp/esp
# Mount ESP (assuming sda1) to esp
sudo mount /dev/sda1 /tmp/esp
# Get UUID's of devices
sudo blkid
# Ensure correct `uuid` is set in `/tmp/esp/efi/EFI/ubuntu/grub.cfg`
reboot
answered Jul 10 '18 at 14:41
SuuuehgiSuuuehgi
48549
add a comment |
I had the same issue apart from that it was booting not at all.
Reason: My fresh install of Ubuntu 18.04, 17.10 and Mate 18.04 had all put the wrong uuid in /boot/efi/EFI/ubuntu/grub.cfg.
Version 1 (grub-cmd):
From grub shell, find root folder by peeking into the outputs of ls (e.g. ls (hd0,gpt2)/) and make sure to know on which partition your system was installed! For me, it was sda2 since ESP is recommended to be the first.
set root=(hd0,gpt2)
linux /boot/vmlinuz-number-generic root=/dev/sda2
initrd /boot/initrd.img-number-generic
boot
If booting is successful now, you can get your uuid's (not partuuid) by typing blkid and verify that the correct one is noted in /boot/efi/EFI/ubuntu/grub.cfg.
For me:
search.fs_uuid <uuid> root hd0,gpt2
...
Version 2 (install-stick):
If you happen to have a bootable linux-stick, you can also boot that, mount your ESP and change the uuid there:
# Create folder to mount ESP
mkdir /tmp/esp
# Mount ESP (assuming sda1) to esp
sudo mount /dev/sda1 /tmp/esp
# Get UUID's of devices
sudo blkid
# Ensure correct `uuid` is set in `/tmp/esp/efi/EFI/ubuntu/grub.cfg`
reboot
answered Jul 10 '18 at 14:41
SuuuehgiSuuuehgi
48549
I had the same issue apart from that it was booting not at all.
Reason: My fresh install of Ubuntu 18.04, 17.10 and Mate 18.04 had all put the wrong uuid in /boot/efi/EFI/ubuntu/grub.cfg.
Version 1 (grub-cmd):
From grub shell, find root folder by peeking into the outputs of ls (e.g. ls (hd0,gpt2)/) and make sure to know on which partition your system was installed! For me, it was sda2 since ESP is recommended to be the first.
set root=(hd0,gpt2)
linux /boot/vmlinuz-number-generic root=/dev/sda2
initrd /boot/initrd.img-number-generic
boot
If booting is successful now, you can get your uuid's (not partuuid) by typing blkid and verify that the correct one is noted in /boot/efi/EFI/ubuntu/grub.cfg.
For me:
search.fs_uuid <uuid> root hd0,gpt2
...
Version 2 (install-stick):
If you happen to have a bootable linux-stick, you can also boot that, mount your ESP and change the uuid there:
# Create folder to mount ESP
mkdir /tmp/esp
# Mount ESP (assuming sda1) to esp
sudo mount /dev/sda1 /tmp/esp
# Get UUID's of devices
sudo blkid
# Ensure correct `uuid` is set in `/tmp/esp/efi/EFI/ubuntu/grub.cfg`
reboot
answered Jul 10 '18 at 14:41
SuuuehgiSuuuehgi
48549
edited Jul 10 '18 at 16:33
answered Jul 10 '18 at 14:41
SuuuehgiSuuuehgi
48549
answered Jul 10 '18 at 14:41
SuuuehgiSuuuehgi
48549
answered Jul 10 '18 at 14:41
SuuuehgiSuuuehgi
48549
48549
add a comment |
add a comment |
You say you can get into your Ubuntu install, so it should be simple enough to update/reinstall grub and see if that fixes the issue.
First, try simply using sudo update-grub if you haven't already, then reboot to check if that fixed it.
If this doesn't work, try manually reinstalling it with sudo grub-install /dev/sd## (replace ## with the current location of grub). This should be enough to reset any files that might be causing your issue.
Note: if you customized your grub install originally, this may reset those changes.
answered Jan 27 at 4:30
Jwalbrecht2000Jwalbrecht2000
11
add a comment |
You say you can get into your Ubuntu install, so it should be simple enough to update/reinstall grub and see if that fixes the issue.
First, try simply using sudo update-grub if you haven't already, then reboot to check if that fixed it.
If this doesn't work, try manually reinstalling it with sudo grub-install /dev/sd## (replace ## with the current location of grub). This should be enough to reset any files that might be causing your issue.
Note: if you customized your grub install originally, this may reset those changes.
answered Jan 27 at 4:30
Jwalbrecht2000Jwalbrecht2000
11
add a comment |
You say you can get into your Ubuntu install, so it should be simple enough to update/reinstall grub and see if that fixes the issue.
First, try simply using sudo update-grub if you haven't already, then reboot to check if that fixed it.
If this doesn't work, try manually reinstalling it with sudo grub-install /dev/sd## (replace ## with the current location of grub). This should be enough to reset any files that might be causing your issue.
Note: if you customized your grub install originally, this may reset those changes.
answered Jan 27 at 4:30
Jwalbrecht2000Jwalbrecht2000
11
You say you can get into your Ubuntu install, so it should be simple enough to update/reinstall grub and see if that fixes the issue.
First, try simply using sudo update-grub if you haven't already, then reboot to check if that fixed it.
If this doesn't work, try manually reinstalling it with sudo grub-install /dev/sd## (replace ## with the current location of grub). This should be enough to reset any files that might be causing your issue.
Note: if you customized your grub install originally, this may reset those changes.
answered Jan 27 at 4:30
Jwalbrecht2000Jwalbrecht2000
11
answered Jan 27 at 4:30
Jwalbrecht2000Jwalbrecht2000
11
answered Jan 27 at 4:30
Jwalbrecht2000Jwalbrecht2000
11
answered Jan 27 at 4:30
Jwalbrecht2000Jwalbrecht2000
11
11
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f442272%2fmy-machine-always-reboot-into-the-grub-prompt-instead-of-grub-menu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Once you boot, run
sudo update-grub– defalt
May 12 '18 at 13:26