How to handle grub with side-by-side 16.04 and 18.04 installs











up vote
0
down vote

favorite












I am currently running 16.04, and am going to additionally install 18.04 side-by-side in separate partitions. I also have Windows on this machine in another partition. I'm using UEFI boot.



How is grub going to work in this scenario? Currently grub adds a bunch of menu items for Ubuntu 16.04, based on the grub scripts, like the default Ubuntu option, but also a bunch of other options such as any older kernel versions, a few entries with custom boot parameters that I added, options to boot into console/recovery mode, etc.



However, with 16.04 and 18.04, won't my grub entries only reflect whatever install I happen to run update-grub on? I guess the "other" install will be picked up by looking at the EFI entries or whatever (in the same way as Windows is), but will have only a single generic entry?










share|improve this question
























  • UEFI or BIOS. Last install normally is default boot. But other system major updates may revert it to default boot. Grub2 has os-prober that finds other installs and adds then to grub menu. So your 18.04 menu will include 16.04. If you boot into 16.04, you can run sudo update-grub and it will then add 18.04 to its grub. But you will not normally then see 16.04's grub menu as you are booting from 18.04. You can change default boot, or use configfile boot stanza to boot other boot menu or many grub configurations changes. help.ubuntu.com/community/MaintenanceFreeCustomGrub2Screen
    – oldfred
    Nov 20 at 3:31










  • It's easy enough to do, but first you need to decide which is to be your main Ubuntu version and take it from there. If it's 18.04 then grub.cfg on 18.04 is the relevant file to be adjusted to take all boot entries. You'll need what kernel version 16.04 is using (may be older than for 18.04). You'll also need the root partition number for 16.04 and its UUID. You can find latter details from lsblk -o name,mountpoint,UUID and kernel details from uname -r
    – Paul Benson
    Nov 20 at 7:48












  • @Paul - why do I need the kernel version?
    – BeeOnRope
    Nov 20 at 15:48










  • While booted in 16.04, if you look at your /boot/grub/grub.cfg file you'll see under the first menu entry (for Ubuntu) towards the end of that section it shows the kernel version of vmlinuz, which is the image it uses to boot from. It may not be the same version as the one for 18.04 when you install it unless you're up to date. If you select 16.04 in Grub it has to be the latest version that currently resides in 16.04's /boot folder.
    – Paul Benson
    Nov 20 at 16:48

















up vote
0
down vote

favorite












I am currently running 16.04, and am going to additionally install 18.04 side-by-side in separate partitions. I also have Windows on this machine in another partition. I'm using UEFI boot.



How is grub going to work in this scenario? Currently grub adds a bunch of menu items for Ubuntu 16.04, based on the grub scripts, like the default Ubuntu option, but also a bunch of other options such as any older kernel versions, a few entries with custom boot parameters that I added, options to boot into console/recovery mode, etc.



However, with 16.04 and 18.04, won't my grub entries only reflect whatever install I happen to run update-grub on? I guess the "other" install will be picked up by looking at the EFI entries or whatever (in the same way as Windows is), but will have only a single generic entry?










share|improve this question
























  • UEFI or BIOS. Last install normally is default boot. But other system major updates may revert it to default boot. Grub2 has os-prober that finds other installs and adds then to grub menu. So your 18.04 menu will include 16.04. If you boot into 16.04, you can run sudo update-grub and it will then add 18.04 to its grub. But you will not normally then see 16.04's grub menu as you are booting from 18.04. You can change default boot, or use configfile boot stanza to boot other boot menu or many grub configurations changes. help.ubuntu.com/community/MaintenanceFreeCustomGrub2Screen
    – oldfred
    Nov 20 at 3:31










  • It's easy enough to do, but first you need to decide which is to be your main Ubuntu version and take it from there. If it's 18.04 then grub.cfg on 18.04 is the relevant file to be adjusted to take all boot entries. You'll need what kernel version 16.04 is using (may be older than for 18.04). You'll also need the root partition number for 16.04 and its UUID. You can find latter details from lsblk -o name,mountpoint,UUID and kernel details from uname -r
    – Paul Benson
    Nov 20 at 7:48












  • @Paul - why do I need the kernel version?
    – BeeOnRope
    Nov 20 at 15:48










  • While booted in 16.04, if you look at your /boot/grub/grub.cfg file you'll see under the first menu entry (for Ubuntu) towards the end of that section it shows the kernel version of vmlinuz, which is the image it uses to boot from. It may not be the same version as the one for 18.04 when you install it unless you're up to date. If you select 16.04 in Grub it has to be the latest version that currently resides in 16.04's /boot folder.
    – Paul Benson
    Nov 20 at 16:48















up vote
0
down vote

favorite









up vote
0
down vote

favorite











I am currently running 16.04, and am going to additionally install 18.04 side-by-side in separate partitions. I also have Windows on this machine in another partition. I'm using UEFI boot.



How is grub going to work in this scenario? Currently grub adds a bunch of menu items for Ubuntu 16.04, based on the grub scripts, like the default Ubuntu option, but also a bunch of other options such as any older kernel versions, a few entries with custom boot parameters that I added, options to boot into console/recovery mode, etc.



However, with 16.04 and 18.04, won't my grub entries only reflect whatever install I happen to run update-grub on? I guess the "other" install will be picked up by looking at the EFI entries or whatever (in the same way as Windows is), but will have only a single generic entry?










share|improve this question















I am currently running 16.04, and am going to additionally install 18.04 side-by-side in separate partitions. I also have Windows on this machine in another partition. I'm using UEFI boot.



How is grub going to work in this scenario? Currently grub adds a bunch of menu items for Ubuntu 16.04, based on the grub scripts, like the default Ubuntu option, but also a bunch of other options such as any older kernel versions, a few entries with custom boot parameters that I added, options to boot into console/recovery mode, etc.



However, with 16.04 and 18.04, won't my grub entries only reflect whatever install I happen to run update-grub on? I guess the "other" install will be picked up by looking at the EFI entries or whatever (in the same way as Windows is), but will have only a single generic entry?







16.04 dual-boot system-installation 18.04






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 20 at 15:46

























asked Nov 20 at 2:34









BeeOnRope

213313




213313












  • UEFI or BIOS. Last install normally is default boot. But other system major updates may revert it to default boot. Grub2 has os-prober that finds other installs and adds then to grub menu. So your 18.04 menu will include 16.04. If you boot into 16.04, you can run sudo update-grub and it will then add 18.04 to its grub. But you will not normally then see 16.04's grub menu as you are booting from 18.04. You can change default boot, or use configfile boot stanza to boot other boot menu or many grub configurations changes. help.ubuntu.com/community/MaintenanceFreeCustomGrub2Screen
    – oldfred
    Nov 20 at 3:31










  • It's easy enough to do, but first you need to decide which is to be your main Ubuntu version and take it from there. If it's 18.04 then grub.cfg on 18.04 is the relevant file to be adjusted to take all boot entries. You'll need what kernel version 16.04 is using (may be older than for 18.04). You'll also need the root partition number for 16.04 and its UUID. You can find latter details from lsblk -o name,mountpoint,UUID and kernel details from uname -r
    – Paul Benson
    Nov 20 at 7:48












  • @Paul - why do I need the kernel version?
    – BeeOnRope
    Nov 20 at 15:48










  • While booted in 16.04, if you look at your /boot/grub/grub.cfg file you'll see under the first menu entry (for Ubuntu) towards the end of that section it shows the kernel version of vmlinuz, which is the image it uses to boot from. It may not be the same version as the one for 18.04 when you install it unless you're up to date. If you select 16.04 in Grub it has to be the latest version that currently resides in 16.04's /boot folder.
    – Paul Benson
    Nov 20 at 16:48




















  • UEFI or BIOS. Last install normally is default boot. But other system major updates may revert it to default boot. Grub2 has os-prober that finds other installs and adds then to grub menu. So your 18.04 menu will include 16.04. If you boot into 16.04, you can run sudo update-grub and it will then add 18.04 to its grub. But you will not normally then see 16.04's grub menu as you are booting from 18.04. You can change default boot, or use configfile boot stanza to boot other boot menu or many grub configurations changes. help.ubuntu.com/community/MaintenanceFreeCustomGrub2Screen
    – oldfred
    Nov 20 at 3:31










  • It's easy enough to do, but first you need to decide which is to be your main Ubuntu version and take it from there. If it's 18.04 then grub.cfg on 18.04 is the relevant file to be adjusted to take all boot entries. You'll need what kernel version 16.04 is using (may be older than for 18.04). You'll also need the root partition number for 16.04 and its UUID. You can find latter details from lsblk -o name,mountpoint,UUID and kernel details from uname -r
    – Paul Benson
    Nov 20 at 7:48












  • @Paul - why do I need the kernel version?
    – BeeOnRope
    Nov 20 at 15:48










  • While booted in 16.04, if you look at your /boot/grub/grub.cfg file you'll see under the first menu entry (for Ubuntu) towards the end of that section it shows the kernel version of vmlinuz, which is the image it uses to boot from. It may not be the same version as the one for 18.04 when you install it unless you're up to date. If you select 16.04 in Grub it has to be the latest version that currently resides in 16.04's /boot folder.
    – Paul Benson
    Nov 20 at 16:48


















UEFI or BIOS. Last install normally is default boot. But other system major updates may revert it to default boot. Grub2 has os-prober that finds other installs and adds then to grub menu. So your 18.04 menu will include 16.04. If you boot into 16.04, you can run sudo update-grub and it will then add 18.04 to its grub. But you will not normally then see 16.04's grub menu as you are booting from 18.04. You can change default boot, or use configfile boot stanza to boot other boot menu or many grub configurations changes. help.ubuntu.com/community/MaintenanceFreeCustomGrub2Screen
– oldfred
Nov 20 at 3:31




UEFI or BIOS. Last install normally is default boot. But other system major updates may revert it to default boot. Grub2 has os-prober that finds other installs and adds then to grub menu. So your 18.04 menu will include 16.04. If you boot into 16.04, you can run sudo update-grub and it will then add 18.04 to its grub. But you will not normally then see 16.04's grub menu as you are booting from 18.04. You can change default boot, or use configfile boot stanza to boot other boot menu or many grub configurations changes. help.ubuntu.com/community/MaintenanceFreeCustomGrub2Screen
– oldfred
Nov 20 at 3:31












It's easy enough to do, but first you need to decide which is to be your main Ubuntu version and take it from there. If it's 18.04 then grub.cfg on 18.04 is the relevant file to be adjusted to take all boot entries. You'll need what kernel version 16.04 is using (may be older than for 18.04). You'll also need the root partition number for 16.04 and its UUID. You can find latter details from lsblk -o name,mountpoint,UUID and kernel details from uname -r
– Paul Benson
Nov 20 at 7:48






It's easy enough to do, but first you need to decide which is to be your main Ubuntu version and take it from there. If it's 18.04 then grub.cfg on 18.04 is the relevant file to be adjusted to take all boot entries. You'll need what kernel version 16.04 is using (may be older than for 18.04). You'll also need the root partition number for 16.04 and its UUID. You can find latter details from lsblk -o name,mountpoint,UUID and kernel details from uname -r
– Paul Benson
Nov 20 at 7:48














@Paul - why do I need the kernel version?
– BeeOnRope
Nov 20 at 15:48




@Paul - why do I need the kernel version?
– BeeOnRope
Nov 20 at 15:48












While booted in 16.04, if you look at your /boot/grub/grub.cfg file you'll see under the first menu entry (for Ubuntu) towards the end of that section it shows the kernel version of vmlinuz, which is the image it uses to boot from. It may not be the same version as the one for 18.04 when you install it unless you're up to date. If you select 16.04 in Grub it has to be the latest version that currently resides in 16.04's /boot folder.
– Paul Benson
Nov 20 at 16:48






While booted in 16.04, if you look at your /boot/grub/grub.cfg file you'll see under the first menu entry (for Ubuntu) towards the end of that section it shows the kernel version of vmlinuz, which is the image it uses to boot from. It may not be the same version as the one for 18.04 when you install it unless you're up to date. If you select 16.04 in Grub it has to be the latest version that currently resides in 16.04's /boot folder.
– Paul Benson
Nov 20 at 16:48

















active

oldest

votes











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',
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%2f1094398%2fhow-to-handle-grub-with-side-by-side-16-04-and-18-04-installs%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1094398%2fhow-to-handle-grub-with-side-by-side-16-04-and-18-04-installs%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

Mont Emei

Province de Neuquén

Journaliste