Unable to boot Ubuntu - stuck at GRUB command-line
I've installed Ubuntu 18.10 on a brand new PC. First off, I wiped Windows that was pre-installed on the SSD + SATA disk. I installed Ubuntu no issue whatsoever (not the first time I do so, anyway). Now comes the time to remove the USB (install) media and reboot. So far so good.
It reboots, and I get dropped to the GRUB command prompt.
I googled around and found that I could fix whatever boot issue I had by using a nifty tool called "boot-repair", from the LiveCD.
I did so, but I could not effect the repairs as boot-repair insisted that I close all package managers such as synaptic and so. Thing is, none were running, so well, I could not complete the repair.
Boot-repair has a nice feature that allows it to collect info and publish it. If you need, you can consult it: http://paste.ubuntu.com/p/MYhdHt8kb5/
Now, I know there's nothing wrong about EFI, secureboot (disabled), CSM (Asus' "legacy mode") as I managed to install Fedora 29 with the same exact bios settings, on the same disk (actually the same, re-formatted partitions).
Before switching with a heavy heart to F29, I tried Ubuntu Server 18.04.1, Ubuntu 18.10, Kubuntu 18.10. Same result the 3 times.
I'm not that familiar on how to fix Grub in any way, I hope that my link above gives anyone enough to help me.
grub2 uefi
edited Feb 5 at 0:55
wjandrea
9,28942664
asked Feb 5 at 0:25
J.F.GrattonJ.F.Gratton
163
add a comment |
I've installed Ubuntu 18.10 on a brand new PC. First off, I wiped Windows that was pre-installed on the SSD + SATA disk. I installed Ubuntu no issue whatsoever (not the first time I do so, anyway). Now comes the time to remove the USB (install) media and reboot. So far so good.
It reboots, and I get dropped to the GRUB command prompt.
I googled around and found that I could fix whatever boot issue I had by using a nifty tool called "boot-repair", from the LiveCD.
I did so, but I could not effect the repairs as boot-repair insisted that I close all package managers such as synaptic and so. Thing is, none were running, so well, I could not complete the repair.
Boot-repair has a nice feature that allows it to collect info and publish it. If you need, you can consult it: http://paste.ubuntu.com/p/MYhdHt8kb5/
Now, I know there's nothing wrong about EFI, secureboot (disabled), CSM (Asus' "legacy mode") as I managed to install Fedora 29 with the same exact bios settings, on the same disk (actually the same, re-formatted partitions).
Before switching with a heavy heart to F29, I tried Ubuntu Server 18.04.1, Ubuntu 18.10, Kubuntu 18.10. Same result the 3 times.
I'm not that familiar on how to fix Grub in any way, I hope that my link above gives anyone enough to help me.
grub2 uefi
edited Feb 5 at 0:55
wjandrea
9,28942664
asked Feb 5 at 0:25
J.F.GrattonJ.F.Gratton
163
I have a hunch that the partitions from Fedora are causing a problem. Have you tried deleting them?
– wjandrea
Feb 5 at 1:02
1
F29 came after Ubuntu.. I tried installing Ubuntu, got stuck at Grub, then installed F29. I wasn't clear, sorry (Engl. is not my main language, apologies). Moreover... As I really hate Fedora, nowadays, so I took a chance and installed Debian 9 in the off-chance that it'll work.. so it did, re-using the partition scheme I had with F29 (I did not wipe anything). So it's most likely is a Ubuntu issue.
– J.F.Gratton
Feb 5 at 1:50
To recap: - Wiped Win10 pre-installed on pc - Tried to install ubuntu 18.10, ubuntu server 18.04.01, kubuntu 18.10. All installed succesfully but stuck at Grub - wiped disks, installed F29 : success - formated filesystems but kept the sizing and layout, installed Debian 9: works (writing this post from D9)
– J.F.Gratton
Feb 5 at 1:50
add a comment |
I've installed Ubuntu 18.10 on a brand new PC. First off, I wiped Windows that was pre-installed on the SSD + SATA disk. I installed Ubuntu no issue whatsoever (not the first time I do so, anyway). Now comes the time to remove the USB (install) media and reboot. So far so good.
It reboots, and I get dropped to the GRUB command prompt.
I googled around and found that I could fix whatever boot issue I had by using a nifty tool called "boot-repair", from the LiveCD.
I did so, but I could not effect the repairs as boot-repair insisted that I close all package managers such as synaptic and so. Thing is, none were running, so well, I could not complete the repair.
Boot-repair has a nice feature that allows it to collect info and publish it. If you need, you can consult it: http://paste.ubuntu.com/p/MYhdHt8kb5/
Now, I know there's nothing wrong about EFI, secureboot (disabled), CSM (Asus' "legacy mode") as I managed to install Fedora 29 with the same exact bios settings, on the same disk (actually the same, re-formatted partitions).
Before switching with a heavy heart to F29, I tried Ubuntu Server 18.04.1, Ubuntu 18.10, Kubuntu 18.10. Same result the 3 times.
I'm not that familiar on how to fix Grub in any way, I hope that my link above gives anyone enough to help me.
grub2 uefi
edited Feb 5 at 0:55
wjandrea
9,28942664
asked Feb 5 at 0:25
J.F.GrattonJ.F.Gratton
163
I've installed Ubuntu 18.10 on a brand new PC. First off, I wiped Windows that was pre-installed on the SSD + SATA disk. I installed Ubuntu no issue whatsoever (not the first time I do so, anyway). Now comes the time to remove the USB (install) media and reboot. So far so good.
It reboots, and I get dropped to the GRUB command prompt.
I googled around and found that I could fix whatever boot issue I had by using a nifty tool called "boot-repair", from the LiveCD.
I did so, but I could not effect the repairs as boot-repair insisted that I close all package managers such as synaptic and so. Thing is, none were running, so well, I could not complete the repair.
Boot-repair has a nice feature that allows it to collect info and publish it. If you need, you can consult it: http://paste.ubuntu.com/p/MYhdHt8kb5/
Now, I know there's nothing wrong about EFI, secureboot (disabled), CSM (Asus' "legacy mode") as I managed to install Fedora 29 with the same exact bios settings, on the same disk (actually the same, re-formatted partitions).
Before switching with a heavy heart to F29, I tried Ubuntu Server 18.04.1, Ubuntu 18.10, Kubuntu 18.10. Same result the 3 times.
I'm not that familiar on how to fix Grub in any way, I hope that my link above gives anyone enough to help me.
grub2 uefi
grub2 uefi
edited Feb 5 at 0:55
wjandrea
9,28942664
asked Feb 5 at 0:25
J.F.GrattonJ.F.Gratton
163
edited Feb 5 at 0:55
wjandrea
9,28942664
asked Feb 5 at 0:25
J.F.GrattonJ.F.Gratton
163
edited Feb 5 at 0:55
wjandrea
9,28942664
edited Feb 5 at 0:55
wjandrea
9,28942664
edited Feb 5 at 0:55
wjandrea
9,28942664
9,28942664
asked Feb 5 at 0:25
J.F.GrattonJ.F.Gratton
163
asked Feb 5 at 0:25
J.F.GrattonJ.F.Gratton
163
asked Feb 5 at 0:25
J.F.GrattonJ.F.Gratton
163
163
I have a hunch that the partitions from Fedora are causing a problem. Have you tried deleting them?
– wjandrea
Feb 5 at 1:02
1
F29 came after Ubuntu.. I tried installing Ubuntu, got stuck at Grub, then installed F29. I wasn't clear, sorry (Engl. is not my main language, apologies). Moreover... As I really hate Fedora, nowadays, so I took a chance and installed Debian 9 in the off-chance that it'll work.. so it did, re-using the partition scheme I had with F29 (I did not wipe anything). So it's most likely is a Ubuntu issue.
– J.F.Gratton
Feb 5 at 1:50
To recap: - Wiped Win10 pre-installed on pc - Tried to install ubuntu 18.10, ubuntu server 18.04.01, kubuntu 18.10. All installed succesfully but stuck at Grub - wiped disks, installed F29 : success - formated filesystems but kept the sizing and layout, installed Debian 9: works (writing this post from D9)
– J.F.Gratton
Feb 5 at 1:50
add a comment |
I have a hunch that the partitions from Fedora are causing a problem. Have you tried deleting them?
– wjandrea
Feb 5 at 1:02
1
F29 came after Ubuntu.. I tried installing Ubuntu, got stuck at Grub, then installed F29. I wasn't clear, sorry (Engl. is not my main language, apologies). Moreover... As I really hate Fedora, nowadays, so I took a chance and installed Debian 9 in the off-chance that it'll work.. so it did, re-using the partition scheme I had with F29 (I did not wipe anything). So it's most likely is a Ubuntu issue.
– J.F.Gratton
Feb 5 at 1:50
To recap: - Wiped Win10 pre-installed on pc - Tried to install ubuntu 18.10, ubuntu server 18.04.01, kubuntu 18.10. All installed succesfully but stuck at Grub - wiped disks, installed F29 : success - formated filesystems but kept the sizing and layout, installed Debian 9: works (writing this post from D9)
– J.F.Gratton
Feb 5 at 1:50
I have a hunch that the partitions from Fedora are causing a problem. Have you tried deleting them?
– wjandrea
Feb 5 at 1:02
I have a hunch that the partitions from Fedora are causing a problem. Have you tried deleting them?
– wjandrea
Feb 5 at 1:02
1
1
F29 came after Ubuntu.. I tried installing Ubuntu, got stuck at Grub, then installed F29. I wasn't clear, sorry (Engl. is not my main language, apologies). Moreover... As I really hate Fedora, nowadays, so I took a chance and installed Debian 9 in the off-chance that it'll work.. so it did, re-using the partition scheme I had with F29 (I did not wipe anything). So it's most likely is a Ubuntu issue.
– J.F.Gratton
Feb 5 at 1:50
F29 came after Ubuntu.. I tried installing Ubuntu, got stuck at Grub, then installed F29. I wasn't clear, sorry (Engl. is not my main language, apologies). Moreover... As I really hate Fedora, nowadays, so I took a chance and installed Debian 9 in the off-chance that it'll work.. so it did, re-using the partition scheme I had with F29 (I did not wipe anything). So it's most likely is a Ubuntu issue.
– J.F.Gratton
Feb 5 at 1:50
To recap: - Wiped Win10 pre-installed on pc - Tried to install ubuntu 18.10, ubuntu server 18.04.01, kubuntu 18.10. All installed succesfully but stuck at Grub - wiped disks, installed F29 : success - formated filesystems but kept the sizing and layout, installed Debian 9: works (writing this post from D9)
– J.F.Gratton
Feb 5 at 1:50
To recap: - Wiped Win10 pre-installed on pc - Tried to install ubuntu 18.10, ubuntu server 18.04.01, kubuntu 18.10. All installed succesfully but stuck at Grub - wiped disks, installed F29 : success - formated filesystems but kept the sizing and layout, installed Debian 9: works (writing this post from D9)
– J.F.Gratton
Feb 5 at 1:50
add a comment |
1 Answer
1
active
oldest
votes
Solved: instead of burning the kubuntu 18.10 ISO to an USB key (dd if=$SOURCE of=/dev/sdh bs=4M), I burned on a DVD. Slapped the DVD in the PC, and voilà.
Weird, tho.... dd is such a reliable tool.
answered Feb 5 at 20:13
J.F.GrattonJ.F.Gratton
163
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2faskubuntu.com%2fquestions%2f1115684%2funable-to-boot-ubuntu-stuck-at-grub-command-line%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Solved: instead of burning the kubuntu 18.10 ISO to an USB key (dd if=$SOURCE of=/dev/sdh bs=4M), I burned on a DVD. Slapped the DVD in the PC, and voilà.
Weird, tho.... dd is such a reliable tool.
answered Feb 5 at 20:13
J.F.GrattonJ.F.Gratton
163
add a comment |
Solved: instead of burning the kubuntu 18.10 ISO to an USB key (dd if=$SOURCE of=/dev/sdh bs=4M), I burned on a DVD. Slapped the DVD in the PC, and voilà.
Weird, tho.... dd is such a reliable tool.
answered Feb 5 at 20:13
J.F.GrattonJ.F.Gratton
163
add a comment |
Solved: instead of burning the kubuntu 18.10 ISO to an USB key (dd if=$SOURCE of=/dev/sdh bs=4M), I burned on a DVD. Slapped the DVD in the PC, and voilà.
Weird, tho.... dd is such a reliable tool.
answered Feb 5 at 20:13
J.F.GrattonJ.F.Gratton
163
Solved: instead of burning the kubuntu 18.10 ISO to an USB key (dd if=$SOURCE of=/dev/sdh bs=4M), I burned on a DVD. Slapped the DVD in the PC, and voilà.
Weird, tho.... dd is such a reliable tool.
answered Feb 5 at 20:13
J.F.GrattonJ.F.Gratton
163
answered Feb 5 at 20:13
J.F.GrattonJ.F.Gratton
163
answered Feb 5 at 20:13
J.F.GrattonJ.F.Gratton
163
answered Feb 5 at 20:13
J.F.GrattonJ.F.Gratton
163
163
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1115684%2funable-to-boot-ubuntu-stuck-at-grub-command-line%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
I have a hunch that the partitions from Fedora are causing a problem. Have you tried deleting them?
– wjandrea
Feb 5 at 1:02
1
F29 came after Ubuntu.. I tried installing Ubuntu, got stuck at Grub, then installed F29. I wasn't clear, sorry (Engl. is not my main language, apologies). Moreover... As I really hate Fedora, nowadays, so I took a chance and installed Debian 9 in the off-chance that it'll work.. so it did, re-using the partition scheme I had with F29 (I did not wipe anything). So it's most likely is a Ubuntu issue.
– J.F.Gratton
Feb 5 at 1:50
To recap: - Wiped Win10 pre-installed on pc - Tried to install ubuntu 18.10, ubuntu server 18.04.01, kubuntu 18.10. All installed succesfully but stuck at Grub - wiped disks, installed F29 : success - formated filesystems but kept the sizing and layout, installed Debian 9: works (writing this post from D9)
– J.F.Gratton
Feb 5 at 1:50