Grub2 of previous OS controls the boot process
up vote
0
down vote
favorite
I have 3 OS's on my computer.
First, I installed windows 10.
Secondly, Ubuntu 16.04 LTS (with GUI).
Thirdly, CentOS 7 (without GUI).
During Ubuntu installation, I installed Grub2 into MBR and it was taking care of booting.
Then, during CentOS installation I again installed Grub2 into MBR, so that CentOS controls booting. And it was controlling for a year or so.
However, recently, I've used such commands as apt-update and apt-upgrade while on Ubuntu system, and now the boot process is controlled by Ubuntu. How do I know ? Well, when the booting process starts and I get to choose which OS I want to load, the background of the menu is in Ubuntu colors. Previously, when CentOS installation based Grub2 was in control of booting everything was in black and white.
How do I make CentOS Grub2 be responsible for the booting process again ?
I've tried to login to CentOS and do something like :
grub2-mkconfig -o /boot/grub2/grub.cfg
But this didn't do anything.
multi-boot centos-7 grub2 ubuntu-16.04
asked Dec 2 at 18:15
Tomas.R
92
add a comment |
up vote
0
down vote
favorite
I have 3 OS's on my computer.
First, I installed windows 10.
Secondly, Ubuntu 16.04 LTS (with GUI).
Thirdly, CentOS 7 (without GUI).
During Ubuntu installation, I installed Grub2 into MBR and it was taking care of booting.
Then, during CentOS installation I again installed Grub2 into MBR, so that CentOS controls booting. And it was controlling for a year or so.
However, recently, I've used such commands as apt-update and apt-upgrade while on Ubuntu system, and now the boot process is controlled by Ubuntu. How do I know ? Well, when the booting process starts and I get to choose which OS I want to load, the background of the menu is in Ubuntu colors. Previously, when CentOS installation based Grub2 was in control of booting everything was in black and white.
How do I make CentOS Grub2 be responsible for the booting process again ?
I've tried to login to CentOS and do something like :
grub2-mkconfig -o /boot/grub2/grub.cfg
But this didn't do anything.
multi-boot centos-7 grub2 ubuntu-16.04
asked Dec 2 at 18:15
Tomas.R
92
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have 3 OS's on my computer.
First, I installed windows 10.
Secondly, Ubuntu 16.04 LTS (with GUI).
Thirdly, CentOS 7 (without GUI).
During Ubuntu installation, I installed Grub2 into MBR and it was taking care of booting.
Then, during CentOS installation I again installed Grub2 into MBR, so that CentOS controls booting. And it was controlling for a year or so.
However, recently, I've used such commands as apt-update and apt-upgrade while on Ubuntu system, and now the boot process is controlled by Ubuntu. How do I know ? Well, when the booting process starts and I get to choose which OS I want to load, the background of the menu is in Ubuntu colors. Previously, when CentOS installation based Grub2 was in control of booting everything was in black and white.
How do I make CentOS Grub2 be responsible for the booting process again ?
I've tried to login to CentOS and do something like :
grub2-mkconfig -o /boot/grub2/grub.cfg
But this didn't do anything.
multi-boot centos-7 grub2 ubuntu-16.04
asked Dec 2 at 18:15
Tomas.R
92
I have 3 OS's on my computer.
First, I installed windows 10.
Secondly, Ubuntu 16.04 LTS (with GUI).
Thirdly, CentOS 7 (without GUI).
During Ubuntu installation, I installed Grub2 into MBR and it was taking care of booting.
Then, during CentOS installation I again installed Grub2 into MBR, so that CentOS controls booting. And it was controlling for a year or so.
However, recently, I've used such commands as apt-update and apt-upgrade while on Ubuntu system, and now the boot process is controlled by Ubuntu. How do I know ? Well, when the booting process starts and I get to choose which OS I want to load, the background of the menu is in Ubuntu colors. Previously, when CentOS installation based Grub2 was in control of booting everything was in black and white.
How do I make CentOS Grub2 be responsible for the booting process again ?
I've tried to login to CentOS and do something like :
grub2-mkconfig -o /boot/grub2/grub.cfg
But this didn't do anything.
multi-boot centos-7 grub2 ubuntu-16.04
multi-boot centos-7 grub2 ubuntu-16.04
asked Dec 2 at 18:15
Tomas.R
92
asked Dec 2 at 18:15
Tomas.R
92
asked Dec 2 at 18:15
Tomas.R
92
asked Dec 2 at 18:15
Tomas.R
92
asked Dec 2 at 18:15
Tomas.R
92
92
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
Since you chose to install grub for both Linux distros you end up in a "winner takes it all" situation: Whichever GRUB is reinstalled last (e.g. because of an update in the distro) controlls the boot process.
By running install-grub /dev/sdX in the distro of your choice you can force it to be the current winner - until the next update. If you want to make sure Ubuntu takes over never again, just uninstall GRUB or add grub to the update blacklist
answered Dec 2 at 18:22
Eugen Rieck
9,55522127
Thanks Eugen, it worked ! :]
– Tomas.R
Dec 2 at 18:34
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
Since you chose to install grub for both Linux distros you end up in a "winner takes it all" situation: Whichever GRUB is reinstalled last (e.g. because of an update in the distro) controlls the boot process.
By running install-grub /dev/sdX in the distro of your choice you can force it to be the current winner - until the next update. If you want to make sure Ubuntu takes over never again, just uninstall GRUB or add grub to the update blacklist
answered Dec 2 at 18:22
Eugen Rieck
9,55522127
Thanks Eugen, it worked ! :]
– Tomas.R
Dec 2 at 18:34
add a comment |
up vote
1
down vote
accepted
Since you chose to install grub for both Linux distros you end up in a "winner takes it all" situation: Whichever GRUB is reinstalled last (e.g. because of an update in the distro) controlls the boot process.
By running install-grub /dev/sdX in the distro of your choice you can force it to be the current winner - until the next update. If you want to make sure Ubuntu takes over never again, just uninstall GRUB or add grub to the update blacklist
answered Dec 2 at 18:22
Eugen Rieck
9,55522127
Thanks Eugen, it worked ! :]
– Tomas.R
Dec 2 at 18:34
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Since you chose to install grub for both Linux distros you end up in a "winner takes it all" situation: Whichever GRUB is reinstalled last (e.g. because of an update in the distro) controlls the boot process.
By running install-grub /dev/sdX in the distro of your choice you can force it to be the current winner - until the next update. If you want to make sure Ubuntu takes over never again, just uninstall GRUB or add grub to the update blacklist
answered Dec 2 at 18:22
Eugen Rieck
9,55522127
Since you chose to install grub for both Linux distros you end up in a "winner takes it all" situation: Whichever GRUB is reinstalled last (e.g. because of an update in the distro) controlls the boot process.
By running install-grub /dev/sdX in the distro of your choice you can force it to be the current winner - until the next update. If you want to make sure Ubuntu takes over never again, just uninstall GRUB or add grub to the update blacklist
answered Dec 2 at 18:22
Eugen Rieck
9,55522127
answered Dec 2 at 18:22
Eugen Rieck
9,55522127
answered Dec 2 at 18:22
Eugen Rieck
9,55522127
answered Dec 2 at 18:22
Eugen Rieck
9,55522127
9,55522127
Thanks Eugen, it worked ! :]
– Tomas.R
Dec 2 at 18:34
add a comment |
Thanks Eugen, it worked ! :]
– Tomas.R
Dec 2 at 18:34
Thanks Eugen, it worked ! :]
– Tomas.R
Dec 2 at 18:34
Thanks Eugen, it worked ! :]
– Tomas.R
Dec 2 at 18:34
add a comment |
Thanks for contributing an answer to Super User!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2fsuperuser.com%2fquestions%2f1380232%2fgrub2-of-previous-os-controls-the-boot-process%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
