My machine always reboot into the GRUB prompt instead of GRUB menu2019 Community Moderator ElectionDual booting Ubuntu and Windows 8. w8 boots through grub shell, but not from menuProblems in using GRUB2 - ManjaroGrub not loading config file or booting into linux automaticallyGRUB starts in command line after rebootGRUB terminal instead of logon screanProblem while trying to setup Linux OpenSuse from USB DiscGrub2 boots into prompt instead of menu after grub2-installCan't see GRUB menu on Boot, ChromebookFedora 28 not showing up in Grub2 menu after installing GnomeDebian fresh install booting to grub prompt
Why is there a voltage between the mains ground and my radiator?
How do you like my writing?
How can The Temple of Elementary Evil reliably protect itself against kinetic bombardment?
Is there an equal sign with wider gap?
Replacing Windows 7 security updates with anti-virus?
Could you please stop shuffling the deck and play already?
Good for you! in Russian
Do f-stop and exposure time perfectly cancel?
PL tone removal?
In the late 1940’s to early 1950’s what technology was available that could melt a LOT of ice?
Rejected in 4th interview round citing insufficient years of experience
How to create a hard link to an inode (ext4)?
Why is this plane circling around the LKO airport every day?
Moving plot label
The bar has been raised
How strictly should I take "Candidates must be local"?
Good allowance savings plan?
Reverse string, can I make it faster?
Should QA ask requirements to developers?
Try Catch Block Affecting a Variable in an Enclosing Scope
Examples of a statistic that is not independent of sample's distribution?
Do I really need to have a scientific explanation for my premise?
Word-Letter Ladder
Single word request: Harming the benefactor
My machine always reboot into the GRUB prompt instead of GRUB menu
2019 Community Moderator ElectionDual booting Ubuntu and Windows 8. w8 boots through grub shell, but not from menuProblems in using GRUB2 - ManjaroGrub not loading config file or booting into linux automaticallyGRUB starts in command line after rebootGRUB terminal instead of logon screanProblem while trying to setup Linux OpenSuse from USB DiscGrub2 boots into prompt instead of menu after grub2-installCan't see GRUB menu on Boot, ChromebookFedora 28 not showing up in Grub2 menu after installing GnomeDebian fresh install booting to grub prompt
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
bumped to the homepage by Community♦ 3 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
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
bumped to the homepage by Community♦ 3 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
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
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
edited May 7 '18 at 11:13
Aiden Bhe
asked May 7 '18 at 9:49
Aiden BheAiden Bhe
62
62
bumped to the homepage by Community♦ 3 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 3 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
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
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.
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
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
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
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
edited Jul 10 '18 at 16:33
answered Jul 10 '18 at 14:41
SuuuehgiSuuuehgi
55549
55549
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.
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.
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.
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
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
-dual-boot, grub, grub2, reboot
Once you boot, run
sudo update-grub
– defalt
May 12 '18 at 13:26