How to remove duplicated Ubuntu image from boot menu?
I've installed Ubuntu 18.04.1 alongside with Windows 10 on my asus gl503ge laptop.
Here is what grub detects:
artur@arturGL503GE:~$ sudo update-grub
[sudo] password for artur:
Sourcing file `/etc/default/grub'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.15.0-45-generic
Found initrd image: /boot/initrd.img-4.15.0-45-generic
Found linux image: /boot/vmlinuz-4.15.0-44-generic
Found initrd image: /boot/initrd.img-4.15.0-44-generic
Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for EFI firmware configuration
done
As you can see, by some reason there are 2 linux images vmlinuz-4.15.0-**45**-generic
and vmlinuz-4.15.0-**44**-generic
Here is lsblk
output:
artur@arturGL503GE:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 140,7M 1 loop /snap/gnome-3-26-1604/74
loop1 7:1 0 140M 1 loop /snap/gnome-3-26-1604/59
loop2 7:2 0 13M 1 loop /snap/gnome-characters/139
loop3 7:3 0 21M 1 loop /snap/gnome-logs/25
loop4 7:4 0 3,3M 1 loop /snap/gnome-system-monitor/36
loop5 7:5 0 14,5M 1 loop /snap/gnome-logs/45
loop6 7:6 0 147,3M 1 loop /snap/skype/66
loop7 7:7 0 12,2M 1 loop /snap/gnome-characters/69
loop8 7:8 0 93,4M 1 loop /snap/telegram-desktop/551
loop9 7:9 0 34,6M 1 loop /snap/gtk-common-themes/818
loop10 7:10 0 93,4M 1 loop /snap/telegram-desktop/524
loop11 7:11 0 34,8M 1 loop /snap/gtk-common-themes/1122
loop12 7:12 0 140,7M 1 loop /snap/gnome-3-26-1604/78
loop13 7:13 0 89,5M 1 loop /snap/core/6130
loop14 7:14 0 2,3M 1 loop /snap/gnome-calculator/260
loop15 7:15 0 91,1M 1 loop /snap/core/6259
loop16 7:16 0 91M 1 loop /snap/core/6350
loop17 7:17 0 3,7M 1 loop /snap/gnome-system-monitor/57
loop18 7:18 0 93,4M 1 loop /snap/telegram-desktop/534
loop19 7:19 0 1,6M 1 loop /snap/gnome-calculator/154
loop20 7:20 0 132,1M 1 loop /snap/postman/81
sda 8:0 0 232,9G 0 disk
├─sda1 8:1 0 499M 0 part
├─sda2 8:2 0 100M 0 part /boot/efi
├─sda3 8:3 0 16M 0 part
└─sda4 8:4 0 232,3G 0 part
sdb 8:16 0 931,5G 0 disk
├─sdb1 8:17 0 1,9G 0 part /windows
├─sdb2 8:18 0 32,6G 0 part /
├─sdb3 8:19 0 465,7G 0 part /home
└─sdb4 8:20 0 431,4G 0 part
sdc 8:32 0 238,5G 0 disk
└─sdc1 8:33 0 238,5G 0 part /media/artur/Backup
dual-boot grub2 partitioning bash uefi
add a comment |
I've installed Ubuntu 18.04.1 alongside with Windows 10 on my asus gl503ge laptop.
Here is what grub detects:
artur@arturGL503GE:~$ sudo update-grub
[sudo] password for artur:
Sourcing file `/etc/default/grub'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.15.0-45-generic
Found initrd image: /boot/initrd.img-4.15.0-45-generic
Found linux image: /boot/vmlinuz-4.15.0-44-generic
Found initrd image: /boot/initrd.img-4.15.0-44-generic
Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for EFI firmware configuration
done
As you can see, by some reason there are 2 linux images vmlinuz-4.15.0-**45**-generic
and vmlinuz-4.15.0-**44**-generic
Here is lsblk
output:
artur@arturGL503GE:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 140,7M 1 loop /snap/gnome-3-26-1604/74
loop1 7:1 0 140M 1 loop /snap/gnome-3-26-1604/59
loop2 7:2 0 13M 1 loop /snap/gnome-characters/139
loop3 7:3 0 21M 1 loop /snap/gnome-logs/25
loop4 7:4 0 3,3M 1 loop /snap/gnome-system-monitor/36
loop5 7:5 0 14,5M 1 loop /snap/gnome-logs/45
loop6 7:6 0 147,3M 1 loop /snap/skype/66
loop7 7:7 0 12,2M 1 loop /snap/gnome-characters/69
loop8 7:8 0 93,4M 1 loop /snap/telegram-desktop/551
loop9 7:9 0 34,6M 1 loop /snap/gtk-common-themes/818
loop10 7:10 0 93,4M 1 loop /snap/telegram-desktop/524
loop11 7:11 0 34,8M 1 loop /snap/gtk-common-themes/1122
loop12 7:12 0 140,7M 1 loop /snap/gnome-3-26-1604/78
loop13 7:13 0 89,5M 1 loop /snap/core/6130
loop14 7:14 0 2,3M 1 loop /snap/gnome-calculator/260
loop15 7:15 0 91,1M 1 loop /snap/core/6259
loop16 7:16 0 91M 1 loop /snap/core/6350
loop17 7:17 0 3,7M 1 loop /snap/gnome-system-monitor/57
loop18 7:18 0 93,4M 1 loop /snap/telegram-desktop/534
loop19 7:19 0 1,6M 1 loop /snap/gnome-calculator/154
loop20 7:20 0 132,1M 1 loop /snap/postman/81
sda 8:0 0 232,9G 0 disk
├─sda1 8:1 0 499M 0 part
├─sda2 8:2 0 100M 0 part /boot/efi
├─sda3 8:3 0 16M 0 part
└─sda4 8:4 0 232,3G 0 part
sdb 8:16 0 931,5G 0 disk
├─sdb1 8:17 0 1,9G 0 part /windows
├─sdb2 8:18 0 32,6G 0 part /
├─sdb3 8:19 0 465,7G 0 part /home
└─sdb4 8:20 0 431,4G 0 part
sdc 8:32 0 238,5G 0 disk
└─sdc1 8:33 0 238,5G 0 part /media/artur/Backup
dual-boot grub2 partitioning bash uefi
2
There are two kernel images, in case one fails to boot, you have a prior one. I'd recommend leaving it there (unless you plan on never having a problem, then good luck). They are not duplicate, one is an older backup (you got the newer one when your system updated to 18.04.2). I don't understand your second part sorry.
– guiverc
Feb 14 at 9:53
There seem to be two questions in one. I suggest removing the second one. Otherwise the question may be closed as "too broad".
– Pilot6
Feb 14 at 9:57
@Pilot6 OK, I edited my question
– arturkuchynski
Feb 14 at 10:24
add a comment |
I've installed Ubuntu 18.04.1 alongside with Windows 10 on my asus gl503ge laptop.
Here is what grub detects:
artur@arturGL503GE:~$ sudo update-grub
[sudo] password for artur:
Sourcing file `/etc/default/grub'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.15.0-45-generic
Found initrd image: /boot/initrd.img-4.15.0-45-generic
Found linux image: /boot/vmlinuz-4.15.0-44-generic
Found initrd image: /boot/initrd.img-4.15.0-44-generic
Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for EFI firmware configuration
done
As you can see, by some reason there are 2 linux images vmlinuz-4.15.0-**45**-generic
and vmlinuz-4.15.0-**44**-generic
Here is lsblk
output:
artur@arturGL503GE:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 140,7M 1 loop /snap/gnome-3-26-1604/74
loop1 7:1 0 140M 1 loop /snap/gnome-3-26-1604/59
loop2 7:2 0 13M 1 loop /snap/gnome-characters/139
loop3 7:3 0 21M 1 loop /snap/gnome-logs/25
loop4 7:4 0 3,3M 1 loop /snap/gnome-system-monitor/36
loop5 7:5 0 14,5M 1 loop /snap/gnome-logs/45
loop6 7:6 0 147,3M 1 loop /snap/skype/66
loop7 7:7 0 12,2M 1 loop /snap/gnome-characters/69
loop8 7:8 0 93,4M 1 loop /snap/telegram-desktop/551
loop9 7:9 0 34,6M 1 loop /snap/gtk-common-themes/818
loop10 7:10 0 93,4M 1 loop /snap/telegram-desktop/524
loop11 7:11 0 34,8M 1 loop /snap/gtk-common-themes/1122
loop12 7:12 0 140,7M 1 loop /snap/gnome-3-26-1604/78
loop13 7:13 0 89,5M 1 loop /snap/core/6130
loop14 7:14 0 2,3M 1 loop /snap/gnome-calculator/260
loop15 7:15 0 91,1M 1 loop /snap/core/6259
loop16 7:16 0 91M 1 loop /snap/core/6350
loop17 7:17 0 3,7M 1 loop /snap/gnome-system-monitor/57
loop18 7:18 0 93,4M 1 loop /snap/telegram-desktop/534
loop19 7:19 0 1,6M 1 loop /snap/gnome-calculator/154
loop20 7:20 0 132,1M 1 loop /snap/postman/81
sda 8:0 0 232,9G 0 disk
├─sda1 8:1 0 499M 0 part
├─sda2 8:2 0 100M 0 part /boot/efi
├─sda3 8:3 0 16M 0 part
└─sda4 8:4 0 232,3G 0 part
sdb 8:16 0 931,5G 0 disk
├─sdb1 8:17 0 1,9G 0 part /windows
├─sdb2 8:18 0 32,6G 0 part /
├─sdb3 8:19 0 465,7G 0 part /home
└─sdb4 8:20 0 431,4G 0 part
sdc 8:32 0 238,5G 0 disk
└─sdc1 8:33 0 238,5G 0 part /media/artur/Backup
dual-boot grub2 partitioning bash uefi
I've installed Ubuntu 18.04.1 alongside with Windows 10 on my asus gl503ge laptop.
Here is what grub detects:
artur@arturGL503GE:~$ sudo update-grub
[sudo] password for artur:
Sourcing file `/etc/default/grub'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.15.0-45-generic
Found initrd image: /boot/initrd.img-4.15.0-45-generic
Found linux image: /boot/vmlinuz-4.15.0-44-generic
Found initrd image: /boot/initrd.img-4.15.0-44-generic
Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for EFI firmware configuration
done
As you can see, by some reason there are 2 linux images vmlinuz-4.15.0-**45**-generic
and vmlinuz-4.15.0-**44**-generic
Here is lsblk
output:
artur@arturGL503GE:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 140,7M 1 loop /snap/gnome-3-26-1604/74
loop1 7:1 0 140M 1 loop /snap/gnome-3-26-1604/59
loop2 7:2 0 13M 1 loop /snap/gnome-characters/139
loop3 7:3 0 21M 1 loop /snap/gnome-logs/25
loop4 7:4 0 3,3M 1 loop /snap/gnome-system-monitor/36
loop5 7:5 0 14,5M 1 loop /snap/gnome-logs/45
loop6 7:6 0 147,3M 1 loop /snap/skype/66
loop7 7:7 0 12,2M 1 loop /snap/gnome-characters/69
loop8 7:8 0 93,4M 1 loop /snap/telegram-desktop/551
loop9 7:9 0 34,6M 1 loop /snap/gtk-common-themes/818
loop10 7:10 0 93,4M 1 loop /snap/telegram-desktop/524
loop11 7:11 0 34,8M 1 loop /snap/gtk-common-themes/1122
loop12 7:12 0 140,7M 1 loop /snap/gnome-3-26-1604/78
loop13 7:13 0 89,5M 1 loop /snap/core/6130
loop14 7:14 0 2,3M 1 loop /snap/gnome-calculator/260
loop15 7:15 0 91,1M 1 loop /snap/core/6259
loop16 7:16 0 91M 1 loop /snap/core/6350
loop17 7:17 0 3,7M 1 loop /snap/gnome-system-monitor/57
loop18 7:18 0 93,4M 1 loop /snap/telegram-desktop/534
loop19 7:19 0 1,6M 1 loop /snap/gnome-calculator/154
loop20 7:20 0 132,1M 1 loop /snap/postman/81
sda 8:0 0 232,9G 0 disk
├─sda1 8:1 0 499M 0 part
├─sda2 8:2 0 100M 0 part /boot/efi
├─sda3 8:3 0 16M 0 part
└─sda4 8:4 0 232,3G 0 part
sdb 8:16 0 931,5G 0 disk
├─sdb1 8:17 0 1,9G 0 part /windows
├─sdb2 8:18 0 32,6G 0 part /
├─sdb3 8:19 0 465,7G 0 part /home
└─sdb4 8:20 0 431,4G 0 part
sdc 8:32 0 238,5G 0 disk
└─sdc1 8:33 0 238,5G 0 part /media/artur/Backup
dual-boot grub2 partitioning bash uefi
dual-boot grub2 partitioning bash uefi
edited Feb 14 at 9:58
arturkuchynski
asked Feb 14 at 9:49
arturkuchynskiarturkuchynski
34
34
2
There are two kernel images, in case one fails to boot, you have a prior one. I'd recommend leaving it there (unless you plan on never having a problem, then good luck). They are not duplicate, one is an older backup (you got the newer one when your system updated to 18.04.2). I don't understand your second part sorry.
– guiverc
Feb 14 at 9:53
There seem to be two questions in one. I suggest removing the second one. Otherwise the question may be closed as "too broad".
– Pilot6
Feb 14 at 9:57
@Pilot6 OK, I edited my question
– arturkuchynski
Feb 14 at 10:24
add a comment |
2
There are two kernel images, in case one fails to boot, you have a prior one. I'd recommend leaving it there (unless you plan on never having a problem, then good luck). They are not duplicate, one is an older backup (you got the newer one when your system updated to 18.04.2). I don't understand your second part sorry.
– guiverc
Feb 14 at 9:53
There seem to be two questions in one. I suggest removing the second one. Otherwise the question may be closed as "too broad".
– Pilot6
Feb 14 at 9:57
@Pilot6 OK, I edited my question
– arturkuchynski
Feb 14 at 10:24
2
2
There are two kernel images, in case one fails to boot, you have a prior one. I'd recommend leaving it there (unless you plan on never having a problem, then good luck). They are not duplicate, one is an older backup (you got the newer one when your system updated to 18.04.2). I don't understand your second part sorry.
– guiverc
Feb 14 at 9:53
There are two kernel images, in case one fails to boot, you have a prior one. I'd recommend leaving it there (unless you plan on never having a problem, then good luck). They are not duplicate, one is an older backup (you got the newer one when your system updated to 18.04.2). I don't understand your second part sorry.
– guiverc
Feb 14 at 9:53
There seem to be two questions in one. I suggest removing the second one. Otherwise the question may be closed as "too broad".
– Pilot6
Feb 14 at 9:57
There seem to be two questions in one. I suggest removing the second one. Otherwise the question may be closed as "too broad".
– Pilot6
Feb 14 at 9:57
@Pilot6 OK, I edited my question
– arturkuchynski
Feb 14 at 10:24
@Pilot6 OK, I edited my question
– arturkuchynski
Feb 14 at 10:24
add a comment |
1 Answer
1
active
oldest
votes
This is normal. Ubuntu installation keeps two kernels: the current and the previous. It is done for a case when you can't boot the latest kernel for some reason.
If you remove the corresponding linux-generic-...
package, the vmlinuz
will be removed.
I don't recommend doing it.
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%2f1118168%2fhow-to-remove-duplicated-ubuntu-image-from-boot-menu%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
This is normal. Ubuntu installation keeps two kernels: the current and the previous. It is done for a case when you can't boot the latest kernel for some reason.
If you remove the corresponding linux-generic-...
package, the vmlinuz
will be removed.
I don't recommend doing it.
add a comment |
This is normal. Ubuntu installation keeps two kernels: the current and the previous. It is done for a case when you can't boot the latest kernel for some reason.
If you remove the corresponding linux-generic-...
package, the vmlinuz
will be removed.
I don't recommend doing it.
add a comment |
This is normal. Ubuntu installation keeps two kernels: the current and the previous. It is done for a case when you can't boot the latest kernel for some reason.
If you remove the corresponding linux-generic-...
package, the vmlinuz
will be removed.
I don't recommend doing it.
This is normal. Ubuntu installation keeps two kernels: the current and the previous. It is done for a case when you can't boot the latest kernel for some reason.
If you remove the corresponding linux-generic-...
package, the vmlinuz
will be removed.
I don't recommend doing it.
answered Feb 14 at 9:54
Pilot6Pilot6
53.5k15109198
53.5k15109198
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%2f1118168%2fhow-to-remove-duplicated-ubuntu-image-from-boot-menu%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
2
There are two kernel images, in case one fails to boot, you have a prior one. I'd recommend leaving it there (unless you plan on never having a problem, then good luck). They are not duplicate, one is an older backup (you got the newer one when your system updated to 18.04.2). I don't understand your second part sorry.
– guiverc
Feb 14 at 9:53
There seem to be two questions in one. I suggest removing the second one. Otherwise the question may be closed as "too broad".
– Pilot6
Feb 14 at 9:57
@Pilot6 OK, I edited my question
– arturkuchynski
Feb 14 at 10:24