Unable to boot Ubuntu - stuck at GRUB command-line












0















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.










share|improve this question

























  • 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
















0















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.










share|improve this question

























  • 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














0












0








0








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.










share|improve this question
















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






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 5 at 0:55









wjandrea

9,45042664




9,45042664










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



















  • 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










1 Answer
1






active

oldest

votes


















0














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.






share|improve this answer























    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
    });


    }
    });














    draft saved

    draft discarded


















    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









    0














    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.






    share|improve this answer




























      0














      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.






      share|improve this answer


























        0












        0








        0







        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.






        share|improve this answer













        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.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 5 at 20:13









        J.F.GrattonJ.F.Gratton

        163




        163






























            draft saved

            draft discarded




















































            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.




            draft saved


            draft discarded














            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





















































            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







            Popular posts from this blog

            Human spaceflight

            Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?

            張江高科駅