What do I select for “GRUB install devices” after an update?Where should I install grub?What do I select for “GRUB install devices” after an update on a VM?“BAD idea” warning when trying to recover Grub, after Windows removed itUbuntu : unattended apt-get upgrade : GRUB install dialogGrub Stuck after installWhat option do I choose for this update?No video after update (10.04), how do I rescue?System doesn't show option to select operating system during startup!How do you run update-grub?Ubuntu : unattended apt-get upgrade : GRUB install dialogWhy does Grub report two items for Windows 7?GRUB 2 problem after Mac OS X updateWhat do I select for “GRUB install devices” after an update on a VM?problem in dual bootUpdate Manger offline errorGrub acting strange after recent update, Ubuntu 17.10/Windows Dual Boot
What kind of footwear is suitable for walking in micro gravity environment?
label a part of commutative diagram
Did Nintendo change its mind about 68000 SNES?
Is a square zero matrix positive semidefinite?
When should a starting writer get his own webpage?
What is the difference between something being completely legal and being completely decriminalized?
Does fire aspect on a sword, destroy mob drops?
Why I don't get the wanted width of tcbox?
pipe commands inside find -exec?
How can an organ that provides biological immortality be unable to regenerate?
Have any astronauts/cosmonauts died in space?
TDE Master Key Rotation
Homology of the fiber
Determine voltage drop over 10G resistors with cheap multimeter
Animating wave motion in water
Nested Dynamic SOQL Query
How are passwords stolen from companies if they only store hashes?
Exit shell with shortcut (not typing exit) that closes session properly
How can a new country break out from a developed country without war?
What (if any) is the reason to buy in small local stores?
"Marked down as someone wanting to sell shares." What does that mean?
Do people actually use the word "kaputt" in conversation?
Why are there no stars visible in cislunar space?
Why didn't Héctor fade away after this character died in the movie Coco?
What do I select for “GRUB install devices” after an update?
Where should I install grub?What do I select for “GRUB install devices” after an update on a VM?“BAD idea” warning when trying to recover Grub, after Windows removed itUbuntu : unattended apt-get upgrade : GRUB install dialogGrub Stuck after installWhat option do I choose for this update?No video after update (10.04), how do I rescue?System doesn't show option to select operating system during startup!How do you run update-grub?Ubuntu : unattended apt-get upgrade : GRUB install dialogWhy does Grub report two items for Windows 7?GRUB 2 problem after Mac OS X updateWhat do I select for “GRUB install devices” after an update on a VM?problem in dual bootUpdate Manger offline errorGrub acting strange after recent update, Ubuntu 17.10/Windows Dual Boot
After running Update Manager, a debconf window (titled "Configuring grub-pc"), popped up, requiring me to select the appropriateGRUB install devices for my system. I've made no changes to grub or the filesystem recently, and I don't remember what options I selected last time I did make a change.
How do I know what to select? I'm assuming the wrong answer could render my system unable to boot.
Here's the debconf dialog:

Here's the window and text that is displayed when selecting "help" :

grub2 update-manager mbr debconf
add a comment |
After running Update Manager, a debconf window (titled "Configuring grub-pc"), popped up, requiring me to select the appropriateGRUB install devices for my system. I've made no changes to grub or the filesystem recently, and I don't remember what options I selected last time I did make a change.
How do I know what to select? I'm assuming the wrong answer could render my system unable to boot.
Here's the debconf dialog:

Here's the window and text that is displayed when selecting "help" :

grub2 update-manager mbr debconf
8
This dialog also crops up when upgrading a virtualbox vm's ubuntu version (in my case, 10.10 -> 11.04).
– Noel
Jun 7 '11 at 13:33
3
As far as my experience with this, it looks like a usability bug. I have run updates countless times and whenever this dialog pops up, I click nothing in the first dialog and then confirm that I want to continue without installing grub. Never had a problem so far. I guess it is because grub is already installed in the proper MBR otherwise the machine would not have booted in the first place.
– Coffee_fan
Mar 22 '15 at 18:48
2
wtf is that ? I just wanted to update a few package as it was suggesting, now I need to make a choice that might kill my system... such bad bad bad stuff !!
– nicolas
Mar 3 '16 at 8:24
2
This is a terrifying experience! I just had it while simply doing an apt upgrade on Ubuntu 16.04.3 LTS (running inside a VirtualBox VM on a Windows 10 host which just got restarted due to updates, I thought it messed everything up) -- nevertheless it worked after choosing/dev/sda
– Daniel F
Nov 6 '17 at 22:52
add a comment |
After running Update Manager, a debconf window (titled "Configuring grub-pc"), popped up, requiring me to select the appropriateGRUB install devices for my system. I've made no changes to grub or the filesystem recently, and I don't remember what options I selected last time I did make a change.
How do I know what to select? I'm assuming the wrong answer could render my system unable to boot.
Here's the debconf dialog:

Here's the window and text that is displayed when selecting "help" :

grub2 update-manager mbr debconf
After running Update Manager, a debconf window (titled "Configuring grub-pc"), popped up, requiring me to select the appropriateGRUB install devices for my system. I've made no changes to grub or the filesystem recently, and I don't remember what options I selected last time I did make a change.
How do I know what to select? I'm assuming the wrong answer could render my system unable to boot.
Here's the debconf dialog:

Here's the window and text that is displayed when selecting "help" :

grub2 update-manager mbr debconf
grub2 update-manager mbr debconf
edited Mar 12 '11 at 4:53
belacqua
asked Jan 26 '11 at 19:35
belacquabelacqua
15.9k1473103
15.9k1473103
8
This dialog also crops up when upgrading a virtualbox vm's ubuntu version (in my case, 10.10 -> 11.04).
– Noel
Jun 7 '11 at 13:33
3
As far as my experience with this, it looks like a usability bug. I have run updates countless times and whenever this dialog pops up, I click nothing in the first dialog and then confirm that I want to continue without installing grub. Never had a problem so far. I guess it is because grub is already installed in the proper MBR otherwise the machine would not have booted in the first place.
– Coffee_fan
Mar 22 '15 at 18:48
2
wtf is that ? I just wanted to update a few package as it was suggesting, now I need to make a choice that might kill my system... such bad bad bad stuff !!
– nicolas
Mar 3 '16 at 8:24
2
This is a terrifying experience! I just had it while simply doing an apt upgrade on Ubuntu 16.04.3 LTS (running inside a VirtualBox VM on a Windows 10 host which just got restarted due to updates, I thought it messed everything up) -- nevertheless it worked after choosing/dev/sda
– Daniel F
Nov 6 '17 at 22:52
add a comment |
8
This dialog also crops up when upgrading a virtualbox vm's ubuntu version (in my case, 10.10 -> 11.04).
– Noel
Jun 7 '11 at 13:33
3
As far as my experience with this, it looks like a usability bug. I have run updates countless times and whenever this dialog pops up, I click nothing in the first dialog and then confirm that I want to continue without installing grub. Never had a problem so far. I guess it is because grub is already installed in the proper MBR otherwise the machine would not have booted in the first place.
– Coffee_fan
Mar 22 '15 at 18:48
2
wtf is that ? I just wanted to update a few package as it was suggesting, now I need to make a choice that might kill my system... such bad bad bad stuff !!
– nicolas
Mar 3 '16 at 8:24
2
This is a terrifying experience! I just had it while simply doing an apt upgrade on Ubuntu 16.04.3 LTS (running inside a VirtualBox VM on a Windows 10 host which just got restarted due to updates, I thought it messed everything up) -- nevertheless it worked after choosing/dev/sda
– Daniel F
Nov 6 '17 at 22:52
8
8
This dialog also crops up when upgrading a virtualbox vm's ubuntu version (in my case, 10.10 -> 11.04).
– Noel
Jun 7 '11 at 13:33
This dialog also crops up when upgrading a virtualbox vm's ubuntu version (in my case, 10.10 -> 11.04).
– Noel
Jun 7 '11 at 13:33
3
3
As far as my experience with this, it looks like a usability bug. I have run updates countless times and whenever this dialog pops up, I click nothing in the first dialog and then confirm that I want to continue without installing grub. Never had a problem so far. I guess it is because grub is already installed in the proper MBR otherwise the machine would not have booted in the first place.
– Coffee_fan
Mar 22 '15 at 18:48
As far as my experience with this, it looks like a usability bug. I have run updates countless times and whenever this dialog pops up, I click nothing in the first dialog and then confirm that I want to continue without installing grub. Never had a problem so far. I guess it is because grub is already installed in the proper MBR otherwise the machine would not have booted in the first place.
– Coffee_fan
Mar 22 '15 at 18:48
2
2
wtf is that ? I just wanted to update a few package as it was suggesting, now I need to make a choice that might kill my system... such bad bad bad stuff !!
– nicolas
Mar 3 '16 at 8:24
wtf is that ? I just wanted to update a few package as it was suggesting, now I need to make a choice that might kill my system... such bad bad bad stuff !!
– nicolas
Mar 3 '16 at 8:24
2
2
This is a terrifying experience! I just had it while simply doing an apt upgrade on Ubuntu 16.04.3 LTS (running inside a VirtualBox VM on a Windows 10 host which just got restarted due to updates, I thought it messed everything up) -- nevertheless it worked after choosing
/dev/sda– Daniel F
Nov 6 '17 at 22:52
This is a terrifying experience! I just had it while simply doing an apt upgrade on Ubuntu 16.04.3 LTS (running inside a VirtualBox VM on a Windows 10 host which just got restarted due to updates, I thought it messed everything up) -- nevertheless it worked after choosing
/dev/sda– Daniel F
Nov 6 '17 at 22:52
add a comment |
3 Answers
3
active
oldest
votes
In your case, the correct selection is /dev/sda, the first one. It's the first and only hard disk in your system, whereas /dev/sda1 is a partition on that hard disk. You can install grub on a partition, but it's a "BAD idea".
If you had multiple hard drives and partitions, first find out where your root partition is:
lsblk
(See also: How do I find out what hard disks are in the system?)
You can then install grub on that hard drive. Look for devices labeled "disk" (e.g. "sda", meaning /dev/sda) to install grub into the master boot record (every physical disk device has only one MBR, no matter the partitions).
20
To finish off the story (which has ended well enough): I selected /dev/sda as suggested. On the next window, I was asked if I wanted to continue without installing grub. Odd, of course, since I had just asked to install it. There was a checkbox to mark to continue without installing, or, if I pressed the "Forward" button, it went back to the previous screen, asking where I wanted to install grub. Instead of looping forever, I checked the box, told it not to install grub and crossed my fingers. On reboot, there were no problems. It remains perplexing why this interaction was required.
– belacqua
Jan 27 '11 at 6:01
2
@StefanoPalazzo So what causes the install/don't install loop? I just had the same experience in 12.04.
– Wes Miller
Dec 30 '13 at 13:55
2
I just had the same issue on 14.04. I would say this was a bug, if not in code then in usability.
– sevis127
Oct 14 '14 at 1:18
3
Just got the same thing on 14.04. I think the purpose of the dialog was to ask you whether you would like to install Grub on any other drive, other than the one it is currently installed on, and thus showed you the "Continue without install" option. I am not totally sure about this, though.
– Mo2
May 16 '15 at 2:54
2
In my case, the install/don't install loop was caused by me not actually selecting a drive. I would move the selection bar to what I'd want, and then hit Enter. I was supposed to hit space bar first, making an asterisk appear in front of the selection. After I'd done that, it counted as 'selected' and would let me out of the loop.
– spoorlezer
Nov 17 '16 at 13:47
|
show 5 more comments
This issue was still present when I upgraded Ubuntu 16.04 after a fresh install. To fix it, do this:
- The selection of
/dev/sdais correct, so press Spacebar for the first option. - An asterisk appears for the
/dev/sdaoption, signifying successful selection. - Then press Tab key to highlight the 'OK' button and then press Spacebar key to select the OK action.
After this, the installation should proceed smoothly.
This is only if it shows a "Bash menu" or dialog not in the example of the question with Ubuntu DE where you have a GUI and can click the checkbox with the mouse pointer.
– Azteca
Nov 13 '18 at 23:11
add a comment |
well during some large updare or software installation the grub config-pc is appearing. in my case it was during vmware installation. it is now also stuck at 96 %. neways my boot is on sdax for ubuntu and so i chose it, but on pressing next the dialog box says you have chose not to install grub....wierd.. i just told it to install. how ever first partition the dialogue box shows is having windows on it( as i just installed ubuntu and by mistake corrupted my MBR for windows) if i check this windows partition, the config box is ready to install grub....which i oviously do not want and i want my windows back with dual boot. the box higlight one thing that --(if u press close config-box window and why this config box has appeared-due to upgrade or whatever, and u can close it) so i did and nothing happened. i hope it solves the case.
but please help me for getting my windows MBR back in sda1 without win10 image as i cannot make win10 bootable from linux as winusb utility install purge grub and boot problem happens every time. when i run boot-repair and chose to recover windows mbr, the repair runs and on reboot grub prompt appears, then have to load kernel again and boot, also need to run grub upgrade for regular loading. but by pressing f9 if i chose to run windows from efi, the bootx64 efi is there but it prompts that **exiting network no operating system found and afterwards the efi bar of win10 disppears from boot efi options. its getting wierd and wierd for windows to boot again. if it helps to understand the problem, my mbr partition and os partition is intact with dos partitions. i just need to reinstall mbr of windows. and i also dnt have cd drive in my hardware.
New contributor
annie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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%2f23418%2fwhat-do-i-select-for-grub-install-devices-after-an-update%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
In your case, the correct selection is /dev/sda, the first one. It's the first and only hard disk in your system, whereas /dev/sda1 is a partition on that hard disk. You can install grub on a partition, but it's a "BAD idea".
If you had multiple hard drives and partitions, first find out where your root partition is:
lsblk
(See also: How do I find out what hard disks are in the system?)
You can then install grub on that hard drive. Look for devices labeled "disk" (e.g. "sda", meaning /dev/sda) to install grub into the master boot record (every physical disk device has only one MBR, no matter the partitions).
20
To finish off the story (which has ended well enough): I selected /dev/sda as suggested. On the next window, I was asked if I wanted to continue without installing grub. Odd, of course, since I had just asked to install it. There was a checkbox to mark to continue without installing, or, if I pressed the "Forward" button, it went back to the previous screen, asking where I wanted to install grub. Instead of looping forever, I checked the box, told it not to install grub and crossed my fingers. On reboot, there were no problems. It remains perplexing why this interaction was required.
– belacqua
Jan 27 '11 at 6:01
2
@StefanoPalazzo So what causes the install/don't install loop? I just had the same experience in 12.04.
– Wes Miller
Dec 30 '13 at 13:55
2
I just had the same issue on 14.04. I would say this was a bug, if not in code then in usability.
– sevis127
Oct 14 '14 at 1:18
3
Just got the same thing on 14.04. I think the purpose of the dialog was to ask you whether you would like to install Grub on any other drive, other than the one it is currently installed on, and thus showed you the "Continue without install" option. I am not totally sure about this, though.
– Mo2
May 16 '15 at 2:54
2
In my case, the install/don't install loop was caused by me not actually selecting a drive. I would move the selection bar to what I'd want, and then hit Enter. I was supposed to hit space bar first, making an asterisk appear in front of the selection. After I'd done that, it counted as 'selected' and would let me out of the loop.
– spoorlezer
Nov 17 '16 at 13:47
|
show 5 more comments
In your case, the correct selection is /dev/sda, the first one. It's the first and only hard disk in your system, whereas /dev/sda1 is a partition on that hard disk. You can install grub on a partition, but it's a "BAD idea".
If you had multiple hard drives and partitions, first find out where your root partition is:
lsblk
(See also: How do I find out what hard disks are in the system?)
You can then install grub on that hard drive. Look for devices labeled "disk" (e.g. "sda", meaning /dev/sda) to install grub into the master boot record (every physical disk device has only one MBR, no matter the partitions).
20
To finish off the story (which has ended well enough): I selected /dev/sda as suggested. On the next window, I was asked if I wanted to continue without installing grub. Odd, of course, since I had just asked to install it. There was a checkbox to mark to continue without installing, or, if I pressed the "Forward" button, it went back to the previous screen, asking where I wanted to install grub. Instead of looping forever, I checked the box, told it not to install grub and crossed my fingers. On reboot, there were no problems. It remains perplexing why this interaction was required.
– belacqua
Jan 27 '11 at 6:01
2
@StefanoPalazzo So what causes the install/don't install loop? I just had the same experience in 12.04.
– Wes Miller
Dec 30 '13 at 13:55
2
I just had the same issue on 14.04. I would say this was a bug, if not in code then in usability.
– sevis127
Oct 14 '14 at 1:18
3
Just got the same thing on 14.04. I think the purpose of the dialog was to ask you whether you would like to install Grub on any other drive, other than the one it is currently installed on, and thus showed you the "Continue without install" option. I am not totally sure about this, though.
– Mo2
May 16 '15 at 2:54
2
In my case, the install/don't install loop was caused by me not actually selecting a drive. I would move the selection bar to what I'd want, and then hit Enter. I was supposed to hit space bar first, making an asterisk appear in front of the selection. After I'd done that, it counted as 'selected' and would let me out of the loop.
– spoorlezer
Nov 17 '16 at 13:47
|
show 5 more comments
In your case, the correct selection is /dev/sda, the first one. It's the first and only hard disk in your system, whereas /dev/sda1 is a partition on that hard disk. You can install grub on a partition, but it's a "BAD idea".
If you had multiple hard drives and partitions, first find out where your root partition is:
lsblk
(See also: How do I find out what hard disks are in the system?)
You can then install grub on that hard drive. Look for devices labeled "disk" (e.g. "sda", meaning /dev/sda) to install grub into the master boot record (every physical disk device has only one MBR, no matter the partitions).
In your case, the correct selection is /dev/sda, the first one. It's the first and only hard disk in your system, whereas /dev/sda1 is a partition on that hard disk. You can install grub on a partition, but it's a "BAD idea".
If you had multiple hard drives and partitions, first find out where your root partition is:
lsblk
(See also: How do I find out what hard disks are in the system?)
You can then install grub on that hard drive. Look for devices labeled "disk" (e.g. "sda", meaning /dev/sda) to install grub into the master boot record (every physical disk device has only one MBR, no matter the partitions).
edited Apr 13 '17 at 12:37
Community♦
1
1
answered Jan 26 '11 at 21:14
Stefano Palazzo♦Stefano Palazzo
63.7k33183216
63.7k33183216
20
To finish off the story (which has ended well enough): I selected /dev/sda as suggested. On the next window, I was asked if I wanted to continue without installing grub. Odd, of course, since I had just asked to install it. There was a checkbox to mark to continue without installing, or, if I pressed the "Forward" button, it went back to the previous screen, asking where I wanted to install grub. Instead of looping forever, I checked the box, told it not to install grub and crossed my fingers. On reboot, there were no problems. It remains perplexing why this interaction was required.
– belacqua
Jan 27 '11 at 6:01
2
@StefanoPalazzo So what causes the install/don't install loop? I just had the same experience in 12.04.
– Wes Miller
Dec 30 '13 at 13:55
2
I just had the same issue on 14.04. I would say this was a bug, if not in code then in usability.
– sevis127
Oct 14 '14 at 1:18
3
Just got the same thing on 14.04. I think the purpose of the dialog was to ask you whether you would like to install Grub on any other drive, other than the one it is currently installed on, and thus showed you the "Continue without install" option. I am not totally sure about this, though.
– Mo2
May 16 '15 at 2:54
2
In my case, the install/don't install loop was caused by me not actually selecting a drive. I would move the selection bar to what I'd want, and then hit Enter. I was supposed to hit space bar first, making an asterisk appear in front of the selection. After I'd done that, it counted as 'selected' and would let me out of the loop.
– spoorlezer
Nov 17 '16 at 13:47
|
show 5 more comments
20
To finish off the story (which has ended well enough): I selected /dev/sda as suggested. On the next window, I was asked if I wanted to continue without installing grub. Odd, of course, since I had just asked to install it. There was a checkbox to mark to continue without installing, or, if I pressed the "Forward" button, it went back to the previous screen, asking where I wanted to install grub. Instead of looping forever, I checked the box, told it not to install grub and crossed my fingers. On reboot, there were no problems. It remains perplexing why this interaction was required.
– belacqua
Jan 27 '11 at 6:01
2
@StefanoPalazzo So what causes the install/don't install loop? I just had the same experience in 12.04.
– Wes Miller
Dec 30 '13 at 13:55
2
I just had the same issue on 14.04. I would say this was a bug, if not in code then in usability.
– sevis127
Oct 14 '14 at 1:18
3
Just got the same thing on 14.04. I think the purpose of the dialog was to ask you whether you would like to install Grub on any other drive, other than the one it is currently installed on, and thus showed you the "Continue without install" option. I am not totally sure about this, though.
– Mo2
May 16 '15 at 2:54
2
In my case, the install/don't install loop was caused by me not actually selecting a drive. I would move the selection bar to what I'd want, and then hit Enter. I was supposed to hit space bar first, making an asterisk appear in front of the selection. After I'd done that, it counted as 'selected' and would let me out of the loop.
– spoorlezer
Nov 17 '16 at 13:47
20
20
To finish off the story (which has ended well enough): I selected /dev/sda as suggested. On the next window, I was asked if I wanted to continue without installing grub. Odd, of course, since I had just asked to install it. There was a checkbox to mark to continue without installing, or, if I pressed the "Forward" button, it went back to the previous screen, asking where I wanted to install grub. Instead of looping forever, I checked the box, told it not to install grub and crossed my fingers. On reboot, there were no problems. It remains perplexing why this interaction was required.
– belacqua
Jan 27 '11 at 6:01
To finish off the story (which has ended well enough): I selected /dev/sda as suggested. On the next window, I was asked if I wanted to continue without installing grub. Odd, of course, since I had just asked to install it. There was a checkbox to mark to continue without installing, or, if I pressed the "Forward" button, it went back to the previous screen, asking where I wanted to install grub. Instead of looping forever, I checked the box, told it not to install grub and crossed my fingers. On reboot, there were no problems. It remains perplexing why this interaction was required.
– belacqua
Jan 27 '11 at 6:01
2
2
@StefanoPalazzo So what causes the install/don't install loop? I just had the same experience in 12.04.
– Wes Miller
Dec 30 '13 at 13:55
@StefanoPalazzo So what causes the install/don't install loop? I just had the same experience in 12.04.
– Wes Miller
Dec 30 '13 at 13:55
2
2
I just had the same issue on 14.04. I would say this was a bug, if not in code then in usability.
– sevis127
Oct 14 '14 at 1:18
I just had the same issue on 14.04. I would say this was a bug, if not in code then in usability.
– sevis127
Oct 14 '14 at 1:18
3
3
Just got the same thing on 14.04. I think the purpose of the dialog was to ask you whether you would like to install Grub on any other drive, other than the one it is currently installed on, and thus showed you the "Continue without install" option. I am not totally sure about this, though.
– Mo2
May 16 '15 at 2:54
Just got the same thing on 14.04. I think the purpose of the dialog was to ask you whether you would like to install Grub on any other drive, other than the one it is currently installed on, and thus showed you the "Continue without install" option. I am not totally sure about this, though.
– Mo2
May 16 '15 at 2:54
2
2
In my case, the install/don't install loop was caused by me not actually selecting a drive. I would move the selection bar to what I'd want, and then hit Enter. I was supposed to hit space bar first, making an asterisk appear in front of the selection. After I'd done that, it counted as 'selected' and would let me out of the loop.
– spoorlezer
Nov 17 '16 at 13:47
In my case, the install/don't install loop was caused by me not actually selecting a drive. I would move the selection bar to what I'd want, and then hit Enter. I was supposed to hit space bar first, making an asterisk appear in front of the selection. After I'd done that, it counted as 'selected' and would let me out of the loop.
– spoorlezer
Nov 17 '16 at 13:47
|
show 5 more comments
This issue was still present when I upgraded Ubuntu 16.04 after a fresh install. To fix it, do this:
- The selection of
/dev/sdais correct, so press Spacebar for the first option. - An asterisk appears for the
/dev/sdaoption, signifying successful selection. - Then press Tab key to highlight the 'OK' button and then press Spacebar key to select the OK action.
After this, the installation should proceed smoothly.
This is only if it shows a "Bash menu" or dialog not in the example of the question with Ubuntu DE where you have a GUI and can click the checkbox with the mouse pointer.
– Azteca
Nov 13 '18 at 23:11
add a comment |
This issue was still present when I upgraded Ubuntu 16.04 after a fresh install. To fix it, do this:
- The selection of
/dev/sdais correct, so press Spacebar for the first option. - An asterisk appears for the
/dev/sdaoption, signifying successful selection. - Then press Tab key to highlight the 'OK' button and then press Spacebar key to select the OK action.
After this, the installation should proceed smoothly.
This is only if it shows a "Bash menu" or dialog not in the example of the question with Ubuntu DE where you have a GUI and can click the checkbox with the mouse pointer.
– Azteca
Nov 13 '18 at 23:11
add a comment |
This issue was still present when I upgraded Ubuntu 16.04 after a fresh install. To fix it, do this:
- The selection of
/dev/sdais correct, so press Spacebar for the first option. - An asterisk appears for the
/dev/sdaoption, signifying successful selection. - Then press Tab key to highlight the 'OK' button and then press Spacebar key to select the OK action.
After this, the installation should proceed smoothly.
This issue was still present when I upgraded Ubuntu 16.04 after a fresh install. To fix it, do this:
- The selection of
/dev/sdais correct, so press Spacebar for the first option. - An asterisk appears for the
/dev/sdaoption, signifying successful selection. - Then press Tab key to highlight the 'OK' button and then press Spacebar key to select the OK action.
After this, the installation should proceed smoothly.
edited Aug 9 '17 at 2:45
Eliah Kagan
82.8k22227369
82.8k22227369
answered Aug 8 '17 at 18:32
Manoj P.Manoj P.
16112
16112
This is only if it shows a "Bash menu" or dialog not in the example of the question with Ubuntu DE where you have a GUI and can click the checkbox with the mouse pointer.
– Azteca
Nov 13 '18 at 23:11
add a comment |
This is only if it shows a "Bash menu" or dialog not in the example of the question with Ubuntu DE where you have a GUI and can click the checkbox with the mouse pointer.
– Azteca
Nov 13 '18 at 23:11
This is only if it shows a "Bash menu" or dialog not in the example of the question with Ubuntu DE where you have a GUI and can click the checkbox with the mouse pointer.
– Azteca
Nov 13 '18 at 23:11
This is only if it shows a "Bash menu" or dialog not in the example of the question with Ubuntu DE where you have a GUI and can click the checkbox with the mouse pointer.
– Azteca
Nov 13 '18 at 23:11
add a comment |
well during some large updare or software installation the grub config-pc is appearing. in my case it was during vmware installation. it is now also stuck at 96 %. neways my boot is on sdax for ubuntu and so i chose it, but on pressing next the dialog box says you have chose not to install grub....wierd.. i just told it to install. how ever first partition the dialogue box shows is having windows on it( as i just installed ubuntu and by mistake corrupted my MBR for windows) if i check this windows partition, the config box is ready to install grub....which i oviously do not want and i want my windows back with dual boot. the box higlight one thing that --(if u press close config-box window and why this config box has appeared-due to upgrade or whatever, and u can close it) so i did and nothing happened. i hope it solves the case.
but please help me for getting my windows MBR back in sda1 without win10 image as i cannot make win10 bootable from linux as winusb utility install purge grub and boot problem happens every time. when i run boot-repair and chose to recover windows mbr, the repair runs and on reboot grub prompt appears, then have to load kernel again and boot, also need to run grub upgrade for regular loading. but by pressing f9 if i chose to run windows from efi, the bootx64 efi is there but it prompts that **exiting network no operating system found and afterwards the efi bar of win10 disppears from boot efi options. its getting wierd and wierd for windows to boot again. if it helps to understand the problem, my mbr partition and os partition is intact with dos partitions. i just need to reinstall mbr of windows. and i also dnt have cd drive in my hardware.
New contributor
annie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
well during some large updare or software installation the grub config-pc is appearing. in my case it was during vmware installation. it is now also stuck at 96 %. neways my boot is on sdax for ubuntu and so i chose it, but on pressing next the dialog box says you have chose not to install grub....wierd.. i just told it to install. how ever first partition the dialogue box shows is having windows on it( as i just installed ubuntu and by mistake corrupted my MBR for windows) if i check this windows partition, the config box is ready to install grub....which i oviously do not want and i want my windows back with dual boot. the box higlight one thing that --(if u press close config-box window and why this config box has appeared-due to upgrade or whatever, and u can close it) so i did and nothing happened. i hope it solves the case.
but please help me for getting my windows MBR back in sda1 without win10 image as i cannot make win10 bootable from linux as winusb utility install purge grub and boot problem happens every time. when i run boot-repair and chose to recover windows mbr, the repair runs and on reboot grub prompt appears, then have to load kernel again and boot, also need to run grub upgrade for regular loading. but by pressing f9 if i chose to run windows from efi, the bootx64 efi is there but it prompts that **exiting network no operating system found and afterwards the efi bar of win10 disppears from boot efi options. its getting wierd and wierd for windows to boot again. if it helps to understand the problem, my mbr partition and os partition is intact with dos partitions. i just need to reinstall mbr of windows. and i also dnt have cd drive in my hardware.
New contributor
annie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
well during some large updare or software installation the grub config-pc is appearing. in my case it was during vmware installation. it is now also stuck at 96 %. neways my boot is on sdax for ubuntu and so i chose it, but on pressing next the dialog box says you have chose not to install grub....wierd.. i just told it to install. how ever first partition the dialogue box shows is having windows on it( as i just installed ubuntu and by mistake corrupted my MBR for windows) if i check this windows partition, the config box is ready to install grub....which i oviously do not want and i want my windows back with dual boot. the box higlight one thing that --(if u press close config-box window and why this config box has appeared-due to upgrade or whatever, and u can close it) so i did and nothing happened. i hope it solves the case.
but please help me for getting my windows MBR back in sda1 without win10 image as i cannot make win10 bootable from linux as winusb utility install purge grub and boot problem happens every time. when i run boot-repair and chose to recover windows mbr, the repair runs and on reboot grub prompt appears, then have to load kernel again and boot, also need to run grub upgrade for regular loading. but by pressing f9 if i chose to run windows from efi, the bootx64 efi is there but it prompts that **exiting network no operating system found and afterwards the efi bar of win10 disppears from boot efi options. its getting wierd and wierd for windows to boot again. if it helps to understand the problem, my mbr partition and os partition is intact with dos partitions. i just need to reinstall mbr of windows. and i also dnt have cd drive in my hardware.
New contributor
annie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
well during some large updare or software installation the grub config-pc is appearing. in my case it was during vmware installation. it is now also stuck at 96 %. neways my boot is on sdax for ubuntu and so i chose it, but on pressing next the dialog box says you have chose not to install grub....wierd.. i just told it to install. how ever first partition the dialogue box shows is having windows on it( as i just installed ubuntu and by mistake corrupted my MBR for windows) if i check this windows partition, the config box is ready to install grub....which i oviously do not want and i want my windows back with dual boot. the box higlight one thing that --(if u press close config-box window and why this config box has appeared-due to upgrade or whatever, and u can close it) so i did and nothing happened. i hope it solves the case.
but please help me for getting my windows MBR back in sda1 without win10 image as i cannot make win10 bootable from linux as winusb utility install purge grub and boot problem happens every time. when i run boot-repair and chose to recover windows mbr, the repair runs and on reboot grub prompt appears, then have to load kernel again and boot, also need to run grub upgrade for regular loading. but by pressing f9 if i chose to run windows from efi, the bootx64 efi is there but it prompts that **exiting network no operating system found and afterwards the efi bar of win10 disppears from boot efi options. its getting wierd and wierd for windows to boot again. if it helps to understand the problem, my mbr partition and os partition is intact with dos partitions. i just need to reinstall mbr of windows. and i also dnt have cd drive in my hardware.
New contributor
annie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
annie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 1 hour ago
annieannie
1
1
New contributor
annie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
annie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
annie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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%2f23418%2fwhat-do-i-select-for-grub-install-devices-after-an-update%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
8
This dialog also crops up when upgrading a virtualbox vm's ubuntu version (in my case, 10.10 -> 11.04).
– Noel
Jun 7 '11 at 13:33
3
As far as my experience with this, it looks like a usability bug. I have run updates countless times and whenever this dialog pops up, I click nothing in the first dialog and then confirm that I want to continue without installing grub. Never had a problem so far. I guess it is because grub is already installed in the proper MBR otherwise the machine would not have booted in the first place.
– Coffee_fan
Mar 22 '15 at 18:48
2
wtf is that ? I just wanted to update a few package as it was suggesting, now I need to make a choice that might kill my system... such bad bad bad stuff !!
– nicolas
Mar 3 '16 at 8:24
2
This is a terrifying experience! I just had it while simply doing an apt upgrade on Ubuntu 16.04.3 LTS (running inside a VirtualBox VM on a Windows 10 host which just got restarted due to updates, I thought it messed everything up) -- nevertheless it worked after choosing
/dev/sda– Daniel F
Nov 6 '17 at 22:52