Grub transfer to another boot device
This is the story:
I have installed Xubuntu 18.04.1 on an external USB HDD. After the installation, I discovered that the operating system was booting ok after every system restart but it wouldn't boot after a system power on.
When I pressed the system's boot menu button I discovered that the USB HDD was not detected by the BIOS during a system power on but it was always detected after a reboot. I realized that this was happening because the HDD would not spin up in time for the BIOS to detect it when the system was powered on.
That issue was forcing me to press Ctrl-Alt-Del after every system power-on so that the BIOS would detect the external HDD after that, since the spin up procedure would be complete at that point.
In order to resolve this issue and since there is no internal HDD on that laptop, I decided to use the laptop's card reader and create a bootable micro-SD card so that the system would boot from that card instead and switch to the HDD afterwards. The grub boot delay helps a lot and the USB HDD completes the spin up procedure in time now. On the running system I executed grub-install /dev/sdb and update-grub and grub did get installed and updated on that micro-SD card successfully and the system boots successfully every time now.
The questions are:
- Did
grub-install /dev/sdbinstall grub on the micro-SD card only or did it erase the USB HDD's (/dev/sda) grub too? - If not, does
update-grubupdate both grub installations every time it's executed from now on? - How do I disable or erase the USB HDD's grub so that the system boots from the micro-SD card exclusively?
Thank you.
grub2
add a comment |
This is the story:
I have installed Xubuntu 18.04.1 on an external USB HDD. After the installation, I discovered that the operating system was booting ok after every system restart but it wouldn't boot after a system power on.
When I pressed the system's boot menu button I discovered that the USB HDD was not detected by the BIOS during a system power on but it was always detected after a reboot. I realized that this was happening because the HDD would not spin up in time for the BIOS to detect it when the system was powered on.
That issue was forcing me to press Ctrl-Alt-Del after every system power-on so that the BIOS would detect the external HDD after that, since the spin up procedure would be complete at that point.
In order to resolve this issue and since there is no internal HDD on that laptop, I decided to use the laptop's card reader and create a bootable micro-SD card so that the system would boot from that card instead and switch to the HDD afterwards. The grub boot delay helps a lot and the USB HDD completes the spin up procedure in time now. On the running system I executed grub-install /dev/sdb and update-grub and grub did get installed and updated on that micro-SD card successfully and the system boots successfully every time now.
The questions are:
- Did
grub-install /dev/sdbinstall grub on the micro-SD card only or did it erase the USB HDD's (/dev/sda) grub too? - If not, does
update-grubupdate both grub installations every time it's executed from now on? - How do I disable or erase the USB HDD's grub so that the system boots from the micro-SD card exclusively?
Thank you.
grub2
is it a UEFI or BIOS?
– PRATAP
Jan 26 at 11:31
It's BIOS. Not UEFI.
– Stormlord
Jan 26 at 12:29
add a comment |
This is the story:
I have installed Xubuntu 18.04.1 on an external USB HDD. After the installation, I discovered that the operating system was booting ok after every system restart but it wouldn't boot after a system power on.
When I pressed the system's boot menu button I discovered that the USB HDD was not detected by the BIOS during a system power on but it was always detected after a reboot. I realized that this was happening because the HDD would not spin up in time for the BIOS to detect it when the system was powered on.
That issue was forcing me to press Ctrl-Alt-Del after every system power-on so that the BIOS would detect the external HDD after that, since the spin up procedure would be complete at that point.
In order to resolve this issue and since there is no internal HDD on that laptop, I decided to use the laptop's card reader and create a bootable micro-SD card so that the system would boot from that card instead and switch to the HDD afterwards. The grub boot delay helps a lot and the USB HDD completes the spin up procedure in time now. On the running system I executed grub-install /dev/sdb and update-grub and grub did get installed and updated on that micro-SD card successfully and the system boots successfully every time now.
The questions are:
- Did
grub-install /dev/sdbinstall grub on the micro-SD card only or did it erase the USB HDD's (/dev/sda) grub too? - If not, does
update-grubupdate both grub installations every time it's executed from now on? - How do I disable or erase the USB HDD's grub so that the system boots from the micro-SD card exclusively?
Thank you.
grub2
This is the story:
I have installed Xubuntu 18.04.1 on an external USB HDD. After the installation, I discovered that the operating system was booting ok after every system restart but it wouldn't boot after a system power on.
When I pressed the system's boot menu button I discovered that the USB HDD was not detected by the BIOS during a system power on but it was always detected after a reboot. I realized that this was happening because the HDD would not spin up in time for the BIOS to detect it when the system was powered on.
That issue was forcing me to press Ctrl-Alt-Del after every system power-on so that the BIOS would detect the external HDD after that, since the spin up procedure would be complete at that point.
In order to resolve this issue and since there is no internal HDD on that laptop, I decided to use the laptop's card reader and create a bootable micro-SD card so that the system would boot from that card instead and switch to the HDD afterwards. The grub boot delay helps a lot and the USB HDD completes the spin up procedure in time now. On the running system I executed grub-install /dev/sdb and update-grub and grub did get installed and updated on that micro-SD card successfully and the system boots successfully every time now.
The questions are:
- Did
grub-install /dev/sdbinstall grub on the micro-SD card only or did it erase the USB HDD's (/dev/sda) grub too? - If not, does
update-grubupdate both grub installations every time it's executed from now on? - How do I disable or erase the USB HDD's grub so that the system boots from the micro-SD card exclusively?
Thank you.
grub2
grub2
asked Jan 26 at 11:03
StormlordStormlord
3,84921028
3,84921028
is it a UEFI or BIOS?
– PRATAP
Jan 26 at 11:31
It's BIOS. Not UEFI.
– Stormlord
Jan 26 at 12:29
add a comment |
is it a UEFI or BIOS?
– PRATAP
Jan 26 at 11:31
It's BIOS. Not UEFI.
– Stormlord
Jan 26 at 12:29
is it a UEFI or BIOS?
– PRATAP
Jan 26 at 11:31
is it a UEFI or BIOS?
– PRATAP
Jan 26 at 11:31
It's BIOS. Not UEFI.
– Stormlord
Jan 26 at 12:29
It's BIOS. Not UEFI.
– Stormlord
Jan 26 at 12:29
add a comment |
1 Answer
1
active
oldest
votes
when you do the install-grub and it is installed on a new drive that is the grub install that will be updated an will be the one the system looks to to boot from.
I believe the other one on the old drive will be left alone. Glad you figured out a system that works for you :)
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%2f1113035%2fgrub-transfer-to-another-boot-device%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
when you do the install-grub and it is installed on a new drive that is the grub install that will be updated an will be the one the system looks to to boot from.
I believe the other one on the old drive will be left alone. Glad you figured out a system that works for you :)
add a comment |
when you do the install-grub and it is installed on a new drive that is the grub install that will be updated an will be the one the system looks to to boot from.
I believe the other one on the old drive will be left alone. Glad you figured out a system that works for you :)
add a comment |
when you do the install-grub and it is installed on a new drive that is the grub install that will be updated an will be the one the system looks to to boot from.
I believe the other one on the old drive will be left alone. Glad you figured out a system that works for you :)
when you do the install-grub and it is installed on a new drive that is the grub install that will be updated an will be the one the system looks to to boot from.
I believe the other one on the old drive will be left alone. Glad you figured out a system that works for you :)
answered Jan 26 at 11:16
kc1dikc1di
946
946
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%2f1113035%2fgrub-transfer-to-another-boot-device%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
is it a UEFI or BIOS?
– PRATAP
Jan 26 at 11:31
It's BIOS. Not UEFI.
– Stormlord
Jan 26 at 12:29