Ubuntu Won't Start: GNU GRUB version 2.02~beta2-36ubuntu3.17How to create UEFI-only bootable USB live...

What has been your most complicated TikZ drawing?

Welcoming 2019 Pi day: How to draw the letter π?

Could the Saturn V actually have launched astronauts around Venus?

Converting Functions to Arrow functions

Why are the outputs of printf and std::cout different

Why doesn't the EU now just force the UK to choose between referendum and no-deal?

Is a lawful good "antagonist" effective?

What does it mean to make a bootable LiveUSB?

Sword in the Stone story where the sword was held in place by electromagnets

Who is our nearest planetary neighbor, on average?

How could a female member of a species produce eggs unto death?

How to simplify this time periods definition interface?

My adviser wants to be the first author

Brexit - No Deal Rejection

How to deal with taxi scam when on vacation?

Know when to turn notes upside-down(eighth notes, sixteen notes, etc.)

Russian cases: A few examples, I'm really confused

Does the statement `int val = (++i > ++j) ? ++i : ++j;` invoke undefined behavior?

PlotLabels with equations not expressions

Good allowance savings plan?

Why doesn't using two cd commands in bash script execute the second command?

Why do passenger jet manufacturers design their planes with stall prevention systems?

Current sense amp + op-amp buffer + ADC: Measuring down to 0 with single supply

Employee lack of ownership



Ubuntu Won't Start: GNU GRUB version 2.02~beta2-36ubuntu3.17


How to create UEFI-only bootable USB live media?How to prepare a disk on an EFI based PC for Ubuntu?How to boot USB from GNU GRUB 2.02~beta2-9ubuntu1?Operating System not found (Grub error)How to get rid of Ubuntu GrubGnu Grub 2.02 beta2-9ubuntu1.3Boot Ubuntu 16.04 server ISO from grubDelete the GNU GRUB from my computerHow do I start Ubuntu from grub?cannot install windows XP after deleting Ubuntu 16.04 and formating all the hard drive?GNU GRUB version 2.02 after update crashGNU Grub version 2.02 error













0















I am trying to install Ubuntu on an empty, MBR, NTFS-formatted 500GB Samsung SSD. To do this, I downloaded ubuntu-18.04-desktop-amd64.iso onto my main hard drive, a Windows 10, 1TB NVME drive. I created a "live USB" using Rufus, writing in ISO mode (default), selecting MBR Partition Scheme for BIOS or UEFI (default), NTFS file system so I could select the 4096 cluster size shown in the tutorial. All other settings were default. The live USB seems to work fine.



When I restart my computer with the live USB set as the highest priority boot disk, I am presented with a command-line interface and the following message:




GNU GRUB version 2.02~beta2-36ubuntu3.17



Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists possible
device or file completions.



grub>




I was not presented with any other option. I tried downloading an older version of Ubuntu: ubuntu-16.04.4-desktop-amd64.iso, thinking there was an issue with the current version. I had the same error. I tried to restart without luck. I am posing this question because while there seem to be a number of posts seeking to address this issue, none of the solutions have worked for me.



Any leads or step-by-step advice for a less-technical person are appreciated.










share|improve this question
















bumped to the homepage by Community 4 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.











  • 1





    ntfs file system for the usb sounds problematic. Usually they are fat, maybe ext4. Doubt you can boot Ubuntu off an ntfs drive.

    – Organic Marble
    Jul 18 '18 at 3:51













  • If you have Windows 10 in UEFI boot mode, you want new SSD as gpt and install Ubuntu in UEFI boot mode. UEFI only USB key, just extract ISO ( 7 zip or similar) to FAT32 formated flash & set boot flag. askubuntu.com/questions/395879/… & askubuntu.com/questions/743095/… Only use Something Else install option.

    – oldfred
    Jul 18 '18 at 14:36


















0















I am trying to install Ubuntu on an empty, MBR, NTFS-formatted 500GB Samsung SSD. To do this, I downloaded ubuntu-18.04-desktop-amd64.iso onto my main hard drive, a Windows 10, 1TB NVME drive. I created a "live USB" using Rufus, writing in ISO mode (default), selecting MBR Partition Scheme for BIOS or UEFI (default), NTFS file system so I could select the 4096 cluster size shown in the tutorial. All other settings were default. The live USB seems to work fine.



When I restart my computer with the live USB set as the highest priority boot disk, I am presented with a command-line interface and the following message:




GNU GRUB version 2.02~beta2-36ubuntu3.17



Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists possible
device or file completions.



grub>




I was not presented with any other option. I tried downloading an older version of Ubuntu: ubuntu-16.04.4-desktop-amd64.iso, thinking there was an issue with the current version. I had the same error. I tried to restart without luck. I am posing this question because while there seem to be a number of posts seeking to address this issue, none of the solutions have worked for me.



Any leads or step-by-step advice for a less-technical person are appreciated.










share|improve this question
















bumped to the homepage by Community 4 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.











  • 1





    ntfs file system for the usb sounds problematic. Usually they are fat, maybe ext4. Doubt you can boot Ubuntu off an ntfs drive.

    – Organic Marble
    Jul 18 '18 at 3:51













  • If you have Windows 10 in UEFI boot mode, you want new SSD as gpt and install Ubuntu in UEFI boot mode. UEFI only USB key, just extract ISO ( 7 zip or similar) to FAT32 formated flash & set boot flag. askubuntu.com/questions/395879/… & askubuntu.com/questions/743095/… Only use Something Else install option.

    – oldfred
    Jul 18 '18 at 14:36
















0












0








0








I am trying to install Ubuntu on an empty, MBR, NTFS-formatted 500GB Samsung SSD. To do this, I downloaded ubuntu-18.04-desktop-amd64.iso onto my main hard drive, a Windows 10, 1TB NVME drive. I created a "live USB" using Rufus, writing in ISO mode (default), selecting MBR Partition Scheme for BIOS or UEFI (default), NTFS file system so I could select the 4096 cluster size shown in the tutorial. All other settings were default. The live USB seems to work fine.



When I restart my computer with the live USB set as the highest priority boot disk, I am presented with a command-line interface and the following message:




GNU GRUB version 2.02~beta2-36ubuntu3.17



Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists possible
device or file completions.



grub>




I was not presented with any other option. I tried downloading an older version of Ubuntu: ubuntu-16.04.4-desktop-amd64.iso, thinking there was an issue with the current version. I had the same error. I tried to restart without luck. I am posing this question because while there seem to be a number of posts seeking to address this issue, none of the solutions have worked for me.



Any leads or step-by-step advice for a less-technical person are appreciated.










share|improve this question
















I am trying to install Ubuntu on an empty, MBR, NTFS-formatted 500GB Samsung SSD. To do this, I downloaded ubuntu-18.04-desktop-amd64.iso onto my main hard drive, a Windows 10, 1TB NVME drive. I created a "live USB" using Rufus, writing in ISO mode (default), selecting MBR Partition Scheme for BIOS or UEFI (default), NTFS file system so I could select the 4096 cluster size shown in the tutorial. All other settings were default. The live USB seems to work fine.



When I restart my computer with the live USB set as the highest priority boot disk, I am presented with a command-line interface and the following message:




GNU GRUB version 2.02~beta2-36ubuntu3.17



Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists possible
device or file completions.



grub>




I was not presented with any other option. I tried downloading an older version of Ubuntu: ubuntu-16.04.4-desktop-amd64.iso, thinking there was an issue with the current version. I had the same error. I tried to restart without luck. I am posing this question because while there seem to be a number of posts seeking to address this issue, none of the solutions have worked for me.



Any leads or step-by-step advice for a less-technical person are appreciated.







boot dual-boot grub2






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 18 '18 at 12:53







user2205916

















asked Jul 18 '18 at 2:13









user2205916user2205916

10114




10114





bumped to the homepage by Community 4 mins 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 4 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.










  • 1





    ntfs file system for the usb sounds problematic. Usually they are fat, maybe ext4. Doubt you can boot Ubuntu off an ntfs drive.

    – Organic Marble
    Jul 18 '18 at 3:51













  • If you have Windows 10 in UEFI boot mode, you want new SSD as gpt and install Ubuntu in UEFI boot mode. UEFI only USB key, just extract ISO ( 7 zip or similar) to FAT32 formated flash & set boot flag. askubuntu.com/questions/395879/… & askubuntu.com/questions/743095/… Only use Something Else install option.

    – oldfred
    Jul 18 '18 at 14:36
















  • 1





    ntfs file system for the usb sounds problematic. Usually they are fat, maybe ext4. Doubt you can boot Ubuntu off an ntfs drive.

    – Organic Marble
    Jul 18 '18 at 3:51













  • If you have Windows 10 in UEFI boot mode, you want new SSD as gpt and install Ubuntu in UEFI boot mode. UEFI only USB key, just extract ISO ( 7 zip or similar) to FAT32 formated flash & set boot flag. askubuntu.com/questions/395879/… & askubuntu.com/questions/743095/… Only use Something Else install option.

    – oldfred
    Jul 18 '18 at 14:36










1




1





ntfs file system for the usb sounds problematic. Usually they are fat, maybe ext4. Doubt you can boot Ubuntu off an ntfs drive.

– Organic Marble
Jul 18 '18 at 3:51







ntfs file system for the usb sounds problematic. Usually they are fat, maybe ext4. Doubt you can boot Ubuntu off an ntfs drive.

– Organic Marble
Jul 18 '18 at 3:51















If you have Windows 10 in UEFI boot mode, you want new SSD as gpt and install Ubuntu in UEFI boot mode. UEFI only USB key, just extract ISO ( 7 zip or similar) to FAT32 formated flash & set boot flag. askubuntu.com/questions/395879/… & askubuntu.com/questions/743095/… Only use Something Else install option.

– oldfred
Jul 18 '18 at 14:36







If you have Windows 10 in UEFI boot mode, you want new SSD as gpt and install Ubuntu in UEFI boot mode. UEFI only USB key, just extract ISO ( 7 zip or similar) to FAT32 formated flash & set boot flag. askubuntu.com/questions/395879/… & askubuntu.com/questions/743095/… Only use Something Else install option.

– oldfred
Jul 18 '18 at 14:36












1 Answer
1






active

oldest

votes


















0














This message is to be expected if you selected NTFS as your filesystem whereas the GRUB bootloader of Ubuntu wasn't compiled with NTFS module support (which means that GRUB can't read its configuration file and bails out).



Why did you change the file system in Rufus?



The default from Rufus with Linux ISOs is FAT32 and you should bear in mind that Rufus tries to select the options (file system, etc.) that are most likely to ensure that your USB will boot. So, unless you know what you are doing, you shouldn't try to second-guess the "best" options to use. Else, you will get into exactly the kind of issue you reported...



Also, you should have gotten a prompt asking you whether you wanted to create your USB in ISO or DD mode, and explicitly advising you to try first in ISO mode and then recreate your USB in DD mode if you encountered an issue. Have you tried that?



Rufus is trying its best to help YOU so that you can avoid the many pitfalls associated with booting. So please don't ignore what it tells you...






share|improve this answer
























  • The official Ubuntu tutorial says the cluster size should be 4096 bytes. FAT32 did not allow that option. So, I was left to pick one of the two settings.

    – user2205916
    Jul 18 '18 at 12:44











  • The cluster sizes available depend on the total size of your drive (and I'd be very curious to see a user report where Ubuntu fails to boot because of FAT32 cluster size, as it seems very unlikely), so it's puzzling that Ubuntu would advise to use a specific cluster size for FAT32, as this is not something that can be controlled. Can you point out where you saw that recommendation about the cluster size?

    – Akeo
    Jul 18 '18 at 19:48













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%2f1057093%2fubuntu-wont-start-gnu-grub-version-2-02beta2-36ubuntu3-17%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














This message is to be expected if you selected NTFS as your filesystem whereas the GRUB bootloader of Ubuntu wasn't compiled with NTFS module support (which means that GRUB can't read its configuration file and bails out).



Why did you change the file system in Rufus?



The default from Rufus with Linux ISOs is FAT32 and you should bear in mind that Rufus tries to select the options (file system, etc.) that are most likely to ensure that your USB will boot. So, unless you know what you are doing, you shouldn't try to second-guess the "best" options to use. Else, you will get into exactly the kind of issue you reported...



Also, you should have gotten a prompt asking you whether you wanted to create your USB in ISO or DD mode, and explicitly advising you to try first in ISO mode and then recreate your USB in DD mode if you encountered an issue. Have you tried that?



Rufus is trying its best to help YOU so that you can avoid the many pitfalls associated with booting. So please don't ignore what it tells you...






share|improve this answer
























  • The official Ubuntu tutorial says the cluster size should be 4096 bytes. FAT32 did not allow that option. So, I was left to pick one of the two settings.

    – user2205916
    Jul 18 '18 at 12:44











  • The cluster sizes available depend on the total size of your drive (and I'd be very curious to see a user report where Ubuntu fails to boot because of FAT32 cluster size, as it seems very unlikely), so it's puzzling that Ubuntu would advise to use a specific cluster size for FAT32, as this is not something that can be controlled. Can you point out where you saw that recommendation about the cluster size?

    – Akeo
    Jul 18 '18 at 19:48


















0














This message is to be expected if you selected NTFS as your filesystem whereas the GRUB bootloader of Ubuntu wasn't compiled with NTFS module support (which means that GRUB can't read its configuration file and bails out).



Why did you change the file system in Rufus?



The default from Rufus with Linux ISOs is FAT32 and you should bear in mind that Rufus tries to select the options (file system, etc.) that are most likely to ensure that your USB will boot. So, unless you know what you are doing, you shouldn't try to second-guess the "best" options to use. Else, you will get into exactly the kind of issue you reported...



Also, you should have gotten a prompt asking you whether you wanted to create your USB in ISO or DD mode, and explicitly advising you to try first in ISO mode and then recreate your USB in DD mode if you encountered an issue. Have you tried that?



Rufus is trying its best to help YOU so that you can avoid the many pitfalls associated with booting. So please don't ignore what it tells you...






share|improve this answer
























  • The official Ubuntu tutorial says the cluster size should be 4096 bytes. FAT32 did not allow that option. So, I was left to pick one of the two settings.

    – user2205916
    Jul 18 '18 at 12:44











  • The cluster sizes available depend on the total size of your drive (and I'd be very curious to see a user report where Ubuntu fails to boot because of FAT32 cluster size, as it seems very unlikely), so it's puzzling that Ubuntu would advise to use a specific cluster size for FAT32, as this is not something that can be controlled. Can you point out where you saw that recommendation about the cluster size?

    – Akeo
    Jul 18 '18 at 19:48
















0












0








0







This message is to be expected if you selected NTFS as your filesystem whereas the GRUB bootloader of Ubuntu wasn't compiled with NTFS module support (which means that GRUB can't read its configuration file and bails out).



Why did you change the file system in Rufus?



The default from Rufus with Linux ISOs is FAT32 and you should bear in mind that Rufus tries to select the options (file system, etc.) that are most likely to ensure that your USB will boot. So, unless you know what you are doing, you shouldn't try to second-guess the "best" options to use. Else, you will get into exactly the kind of issue you reported...



Also, you should have gotten a prompt asking you whether you wanted to create your USB in ISO or DD mode, and explicitly advising you to try first in ISO mode and then recreate your USB in DD mode if you encountered an issue. Have you tried that?



Rufus is trying its best to help YOU so that you can avoid the many pitfalls associated with booting. So please don't ignore what it tells you...






share|improve this answer













This message is to be expected if you selected NTFS as your filesystem whereas the GRUB bootloader of Ubuntu wasn't compiled with NTFS module support (which means that GRUB can't read its configuration file and bails out).



Why did you change the file system in Rufus?



The default from Rufus with Linux ISOs is FAT32 and you should bear in mind that Rufus tries to select the options (file system, etc.) that are most likely to ensure that your USB will boot. So, unless you know what you are doing, you shouldn't try to second-guess the "best" options to use. Else, you will get into exactly the kind of issue you reported...



Also, you should have gotten a prompt asking you whether you wanted to create your USB in ISO or DD mode, and explicitly advising you to try first in ISO mode and then recreate your USB in DD mode if you encountered an issue. Have you tried that?



Rufus is trying its best to help YOU so that you can avoid the many pitfalls associated with booting. So please don't ignore what it tells you...







share|improve this answer












share|improve this answer



share|improve this answer










answered Jul 18 '18 at 11:49









AkeoAkeo

22527




22527













  • The official Ubuntu tutorial says the cluster size should be 4096 bytes. FAT32 did not allow that option. So, I was left to pick one of the two settings.

    – user2205916
    Jul 18 '18 at 12:44











  • The cluster sizes available depend on the total size of your drive (and I'd be very curious to see a user report where Ubuntu fails to boot because of FAT32 cluster size, as it seems very unlikely), so it's puzzling that Ubuntu would advise to use a specific cluster size for FAT32, as this is not something that can be controlled. Can you point out where you saw that recommendation about the cluster size?

    – Akeo
    Jul 18 '18 at 19:48





















  • The official Ubuntu tutorial says the cluster size should be 4096 bytes. FAT32 did not allow that option. So, I was left to pick one of the two settings.

    – user2205916
    Jul 18 '18 at 12:44











  • The cluster sizes available depend on the total size of your drive (and I'd be very curious to see a user report where Ubuntu fails to boot because of FAT32 cluster size, as it seems very unlikely), so it's puzzling that Ubuntu would advise to use a specific cluster size for FAT32, as this is not something that can be controlled. Can you point out where you saw that recommendation about the cluster size?

    – Akeo
    Jul 18 '18 at 19:48



















The official Ubuntu tutorial says the cluster size should be 4096 bytes. FAT32 did not allow that option. So, I was left to pick one of the two settings.

– user2205916
Jul 18 '18 at 12:44





The official Ubuntu tutorial says the cluster size should be 4096 bytes. FAT32 did not allow that option. So, I was left to pick one of the two settings.

– user2205916
Jul 18 '18 at 12:44













The cluster sizes available depend on the total size of your drive (and I'd be very curious to see a user report where Ubuntu fails to boot because of FAT32 cluster size, as it seems very unlikely), so it's puzzling that Ubuntu would advise to use a specific cluster size for FAT32, as this is not something that can be controlled. Can you point out where you saw that recommendation about the cluster size?

– Akeo
Jul 18 '18 at 19:48







The cluster sizes available depend on the total size of your drive (and I'd be very curious to see a user report where Ubuntu fails to boot because of FAT32 cluster size, as it seems very unlikely), so it's puzzling that Ubuntu would advise to use a specific cluster size for FAT32, as this is not something that can be controlled. Can you point out where you saw that recommendation about the cluster size?

– Akeo
Jul 18 '18 at 19:48




















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%2f1057093%2fubuntu-wont-start-gnu-grub-version-2-02beta2-36ubuntu3-17%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

Why do type traits not work with types in namespace scope?What are POD types in C++?Why can templates only be...

Will tsunami waves travel forever if there was no land?Why do tsunami waves begin with the water flowing away...

Simple Scan not detecting my scanner (Brother DCP-7055W)Brother MFC-L2700DW printer can print, can't...