Two grub installations destroying each otherHow to update grub from another distro?How to stop grub from messing with my EFI partition?Configure Grub Update to Install on Partitionchanging grub boot driveInstall new Linux distribution without overwriting GRUB2repairing grub and efiTwo linux distributions, grub does not detect other oneDebian Dual Boot installation GRUB not showinggrub: boot system on non-GPT disk while in UEFI modeupdate-grub vs. grub-install?
How did the USSR manage to innovate in an environment characterized by government censorship and high bureaucracy?
Need help identifying/translating a plaque in Tangier, Morocco
How to manage monthly salary
A poker game description that does not feel gimmicky
Piano - What is the notation for a double stop where both notes in the double stop are different lengths?
Landlord wants to switch my lease to a "Land contract" to "get back at the city"
Pristine Bit Checking
New order #4: World
Is Social Media Science Fiction?
What do the Banks children have against barley water?
How to move the player while also allowing forces to affect it
How could a lack of term limits lead to a "dictatorship?"
Prime joint compound before latex paint?
Why airport relocation isn't done gradually?
What is the offset in a seaplane's hull?
Is this food a bread or a loaf?
What causes the sudden spool-up sound from an F-16 when enabling afterburner?
Doomsday-clock for my fantasy planet
Hosting Wordpress in a EC2 Load Balanced Instance
Copycat chess is back
Can I legally use front facing blue light in the UK?
I see my dog run
Where else does the Shulchan Aruch quote an authority by name?
Calculate Levenshtein distance between two strings in Python
Two grub installations destroying each other
How to update grub from another distro?How to stop grub from messing with my EFI partition?Configure Grub Update to Install on Partitionchanging grub boot driveInstall new Linux distribution without overwriting GRUB2repairing grub and efiTwo linux distributions, grub does not detect other oneDebian Dual Boot installation GRUB not showinggrub: boot system on non-GPT disk while in UEFI modeupdate-grub vs. grub-install?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I have linux mint 19 installed on /dev/sda5
. Recently I connected an external drive and installed Ubuntu 18.04 LTS on that (/dev/sdb2
). After that, I could no longer boot my original Mint installation (except the external drive was present). It just went into the black grub screen with prompt.
My assumption was, that grub was newly installed on the external drive (which is expected, as I want that to be bootable on its own), and somehow the old grub installation then was forgotten. So I repaired grub, through use of a live cd and chroot method.
But now if I reconnect the external drive, I cannot choose to boot from that in BIOS boot selection.
It seems my two grub installations are somehow incompatible, but why and how can that be fixed?
Additional Info: Both disks have grub2 installed, both use EFI and gpt. I have one EFI partition on sda
and have another one on sdb
, as without EFI partition grub wouldn't install (and I did not want to reference the EFI partition on sda, as I want the Ubuntu to be able to boot on its own at other machines).
Update: I have found /boot/efi/EFI/ubuntu
present in my (repaired) Mint 19 installation (without external drive attached). There are no other folders in /boot/efi
and /boot/efi/EFI
I don't know if that means anything, as Mint 19 is based on Ubuntu, and there is no /boot/efi/EFI/mint
or similar directory there. The EFI partition on the external drive is completely empty as is the /boot/efi
folder on my ubuntu installation. I guess I will have to put some research into how to enforce the usage of the right EFI partition.
Just now I got an update of grub2, that gave an error when it tried to run grub-install
:
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
But the system does boot normally. There is no EFI partition mounted.
Update 2
Ok, it seems there are general problems with installing EFI on anything else than the first partition (usually /dev/sda
), see eg here. The fstab on my external Ubuntu install has this line:
# /boot/efi was on /dev/sda1 during installation
UUID=8A3D-B724 /boot/efi vfat umask=0077 0 1
That proves, that the installation ignored the option for EFI partition that I chose.
grub2
New contributor
add a comment |
I have linux mint 19 installed on /dev/sda5
. Recently I connected an external drive and installed Ubuntu 18.04 LTS on that (/dev/sdb2
). After that, I could no longer boot my original Mint installation (except the external drive was present). It just went into the black grub screen with prompt.
My assumption was, that grub was newly installed on the external drive (which is expected, as I want that to be bootable on its own), and somehow the old grub installation then was forgotten. So I repaired grub, through use of a live cd and chroot method.
But now if I reconnect the external drive, I cannot choose to boot from that in BIOS boot selection.
It seems my two grub installations are somehow incompatible, but why and how can that be fixed?
Additional Info: Both disks have grub2 installed, both use EFI and gpt. I have one EFI partition on sda
and have another one on sdb
, as without EFI partition grub wouldn't install (and I did not want to reference the EFI partition on sda, as I want the Ubuntu to be able to boot on its own at other machines).
Update: I have found /boot/efi/EFI/ubuntu
present in my (repaired) Mint 19 installation (without external drive attached). There are no other folders in /boot/efi
and /boot/efi/EFI
I don't know if that means anything, as Mint 19 is based on Ubuntu, and there is no /boot/efi/EFI/mint
or similar directory there. The EFI partition on the external drive is completely empty as is the /boot/efi
folder on my ubuntu installation. I guess I will have to put some research into how to enforce the usage of the right EFI partition.
Just now I got an update of grub2, that gave an error when it tried to run grub-install
:
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
But the system does boot normally. There is no EFI partition mounted.
Update 2
Ok, it seems there are general problems with installing EFI on anything else than the first partition (usually /dev/sda
), see eg here. The fstab on my external Ubuntu install has this line:
# /boot/efi was on /dev/sda1 during installation
UUID=8A3D-B724 /boot/efi vfat umask=0077 0 1
That proves, that the installation ignored the option for EFI partition that I chose.
grub2
New contributor
Once booted into your Mint, have you checked the contents of/boot/efi/EFI
? Did you end up with mint and ubuntu side by side, or does mint (cheekily) install its bootloader to/boot/efi/EFI/ubuntu
?
– Philip Couling
Apr 5 at 23:10
@PhilipCouling I checked, and yes, I found/boot/efi/EFI/ubuntu
, will update the question accordingly
– Paul
2 days ago
add a comment |
I have linux mint 19 installed on /dev/sda5
. Recently I connected an external drive and installed Ubuntu 18.04 LTS on that (/dev/sdb2
). After that, I could no longer boot my original Mint installation (except the external drive was present). It just went into the black grub screen with prompt.
My assumption was, that grub was newly installed on the external drive (which is expected, as I want that to be bootable on its own), and somehow the old grub installation then was forgotten. So I repaired grub, through use of a live cd and chroot method.
But now if I reconnect the external drive, I cannot choose to boot from that in BIOS boot selection.
It seems my two grub installations are somehow incompatible, but why and how can that be fixed?
Additional Info: Both disks have grub2 installed, both use EFI and gpt. I have one EFI partition on sda
and have another one on sdb
, as without EFI partition grub wouldn't install (and I did not want to reference the EFI partition on sda, as I want the Ubuntu to be able to boot on its own at other machines).
Update: I have found /boot/efi/EFI/ubuntu
present in my (repaired) Mint 19 installation (without external drive attached). There are no other folders in /boot/efi
and /boot/efi/EFI
I don't know if that means anything, as Mint 19 is based on Ubuntu, and there is no /boot/efi/EFI/mint
or similar directory there. The EFI partition on the external drive is completely empty as is the /boot/efi
folder on my ubuntu installation. I guess I will have to put some research into how to enforce the usage of the right EFI partition.
Just now I got an update of grub2, that gave an error when it tried to run grub-install
:
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
But the system does boot normally. There is no EFI partition mounted.
Update 2
Ok, it seems there are general problems with installing EFI on anything else than the first partition (usually /dev/sda
), see eg here. The fstab on my external Ubuntu install has this line:
# /boot/efi was on /dev/sda1 during installation
UUID=8A3D-B724 /boot/efi vfat umask=0077 0 1
That proves, that the installation ignored the option for EFI partition that I chose.
grub2
New contributor
I have linux mint 19 installed on /dev/sda5
. Recently I connected an external drive and installed Ubuntu 18.04 LTS on that (/dev/sdb2
). After that, I could no longer boot my original Mint installation (except the external drive was present). It just went into the black grub screen with prompt.
My assumption was, that grub was newly installed on the external drive (which is expected, as I want that to be bootable on its own), and somehow the old grub installation then was forgotten. So I repaired grub, through use of a live cd and chroot method.
But now if I reconnect the external drive, I cannot choose to boot from that in BIOS boot selection.
It seems my two grub installations are somehow incompatible, but why and how can that be fixed?
Additional Info: Both disks have grub2 installed, both use EFI and gpt. I have one EFI partition on sda
and have another one on sdb
, as without EFI partition grub wouldn't install (and I did not want to reference the EFI partition on sda, as I want the Ubuntu to be able to boot on its own at other machines).
Update: I have found /boot/efi/EFI/ubuntu
present in my (repaired) Mint 19 installation (without external drive attached). There are no other folders in /boot/efi
and /boot/efi/EFI
I don't know if that means anything, as Mint 19 is based on Ubuntu, and there is no /boot/efi/EFI/mint
or similar directory there. The EFI partition on the external drive is completely empty as is the /boot/efi
folder on my ubuntu installation. I guess I will have to put some research into how to enforce the usage of the right EFI partition.
Just now I got an update of grub2, that gave an error when it tried to run grub-install
:
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
But the system does boot normally. There is no EFI partition mounted.
Update 2
Ok, it seems there are general problems with installing EFI on anything else than the first partition (usually /dev/sda
), see eg here. The fstab on my external Ubuntu install has this line:
# /boot/efi was on /dev/sda1 during installation
UUID=8A3D-B724 /boot/efi vfat umask=0077 0 1
That proves, that the installation ignored the option for EFI partition that I chose.
grub2
grub2
New contributor
New contributor
edited yesterday
Paul
New contributor
asked Apr 5 at 17:51
PaulPaul
215
215
New contributor
New contributor
Once booted into your Mint, have you checked the contents of/boot/efi/EFI
? Did you end up with mint and ubuntu side by side, or does mint (cheekily) install its bootloader to/boot/efi/EFI/ubuntu
?
– Philip Couling
Apr 5 at 23:10
@PhilipCouling I checked, and yes, I found/boot/efi/EFI/ubuntu
, will update the question accordingly
– Paul
2 days ago
add a comment |
Once booted into your Mint, have you checked the contents of/boot/efi/EFI
? Did you end up with mint and ubuntu side by side, or does mint (cheekily) install its bootloader to/boot/efi/EFI/ubuntu
?
– Philip Couling
Apr 5 at 23:10
@PhilipCouling I checked, and yes, I found/boot/efi/EFI/ubuntu
, will update the question accordingly
– Paul
2 days ago
Once booted into your Mint, have you checked the contents of
/boot/efi/EFI
? Did you end up with mint and ubuntu side by side, or does mint (cheekily) install its bootloader to /boot/efi/EFI/ubuntu
?– Philip Couling
Apr 5 at 23:10
Once booted into your Mint, have you checked the contents of
/boot/efi/EFI
? Did you end up with mint and ubuntu side by side, or does mint (cheekily) install its bootloader to /boot/efi/EFI/ubuntu
?– Philip Couling
Apr 5 at 23:10
@PhilipCouling I checked, and yes, I found
/boot/efi/EFI/ubuntu
, will update the question accordingly– Paul
2 days ago
@PhilipCouling I checked, and yes, I found
/boot/efi/EFI/ubuntu
, will update the question accordingly– Paul
2 days ago
add a comment |
2 Answers
2
active
oldest
votes
When you install Ubuntu (and probably Mint too) in UEFI mode, the bootloader goes into the first drive (typically the internal one), /dev/sda
, into the EFI system partition on that drive. This happens even if you tell the system to install it into another drive.
If you want the second drive to be portable and the booting to work, when the second drive is removed, you should disconnect (or unplug) the first drive before you start installing.
The following link may help,
How do I install Ubuntu to a USB key? (without using Startup Disk Creator)
In order to repair the boot system in the first drive (typically the internal one), you should disconnect the second drive before you start the repair actions.
Edit:
If you cannot disconnect/remove an internal drive there are workarounds:
Disable the internal drive in an UEFI/BIOS menu
The flag method
a. Make a note on paper of the flags of the EFI partition in the internal drive
b. Remove the flags from the EFI partition in the internal drive (for example with
gparted
, when booted from a live drive)c. Perform the installation
d. Restore the flags to the EFI partition in the internal drive (with
gparted
booted from a live drive).
I have disconnected/removed the drive, and I know people who have disabled it in an UEFI/BIOS menu, and I have read about modifying the flags, but have no own experience of the flag method.
1
Removing all other drives ought to work of course, but not for all machines it is possible to just remove one, or all drives.
– Paul
yesterday
add a comment |
If one already has run into the situation, and does not want to install everything anew, with all other disks disconected as sudodus suggests in his answer, I found a way:
First, if the main system cannot boot on its own, disconnect the external drive and boot from a live cd, or live usb flash drive. If not present in the live session, install the tool "boot-repair" (details for advanced use and install here, by typing in the terminal
sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update
sudo apt-get install -y boot-repair && boot-repair
and then start it by typing boot-repair
. It is has a GUI that is quite self-explanatory. Repair the boot of the main system, then restart.
Second, when the main system boots again, boot into that, connect the external drive. Copy the entire content of EFI/ubuntu
on internal drive's EFI partition (/dev/sda1
in this case) to the external drive's EFI partition twice. Once to EFI/ubuntu
there and once to EFI/Boot
. And then in EFI/Boot
rename shimx64.efi
to bootx64.efi
.
Now on the external ubuntu root partition edit the file etc/fstab
and find a line like this:
# /boot/efi was on /dev/sda1 during installation
UUID=8A3D-B724 /boot/efi vfat umask=0077 0 1
replace the UUID 8A3D-B724
, which should belong to your main system's EFI partition with the UUID of the external EFI partition. One can find that with the command blkid
or if one prefers a GUI application, one can use Disks, or Gparted.
After that is done, the external drive is bootable.
Also see:
Full install to USB flash drive, UEFI Boot
New contributor
+1 Thanks for sharing your solution :-)
– sudodus
19 hours ago
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
);
);
Paul is a new contributor. Be nice, and check out our Code of Conduct.
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%2funix.stackexchange.com%2fquestions%2f510773%2ftwo-grub-installations-destroying-each-other%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
When you install Ubuntu (and probably Mint too) in UEFI mode, the bootloader goes into the first drive (typically the internal one), /dev/sda
, into the EFI system partition on that drive. This happens even if you tell the system to install it into another drive.
If you want the second drive to be portable and the booting to work, when the second drive is removed, you should disconnect (or unplug) the first drive before you start installing.
The following link may help,
How do I install Ubuntu to a USB key? (without using Startup Disk Creator)
In order to repair the boot system in the first drive (typically the internal one), you should disconnect the second drive before you start the repair actions.
Edit:
If you cannot disconnect/remove an internal drive there are workarounds:
Disable the internal drive in an UEFI/BIOS menu
The flag method
a. Make a note on paper of the flags of the EFI partition in the internal drive
b. Remove the flags from the EFI partition in the internal drive (for example with
gparted
, when booted from a live drive)c. Perform the installation
d. Restore the flags to the EFI partition in the internal drive (with
gparted
booted from a live drive).
I have disconnected/removed the drive, and I know people who have disabled it in an UEFI/BIOS menu, and I have read about modifying the flags, but have no own experience of the flag method.
1
Removing all other drives ought to work of course, but not for all machines it is possible to just remove one, or all drives.
– Paul
yesterday
add a comment |
When you install Ubuntu (and probably Mint too) in UEFI mode, the bootloader goes into the first drive (typically the internal one), /dev/sda
, into the EFI system partition on that drive. This happens even if you tell the system to install it into another drive.
If you want the second drive to be portable and the booting to work, when the second drive is removed, you should disconnect (or unplug) the first drive before you start installing.
The following link may help,
How do I install Ubuntu to a USB key? (without using Startup Disk Creator)
In order to repair the boot system in the first drive (typically the internal one), you should disconnect the second drive before you start the repair actions.
Edit:
If you cannot disconnect/remove an internal drive there are workarounds:
Disable the internal drive in an UEFI/BIOS menu
The flag method
a. Make a note on paper of the flags of the EFI partition in the internal drive
b. Remove the flags from the EFI partition in the internal drive (for example with
gparted
, when booted from a live drive)c. Perform the installation
d. Restore the flags to the EFI partition in the internal drive (with
gparted
booted from a live drive).
I have disconnected/removed the drive, and I know people who have disabled it in an UEFI/BIOS menu, and I have read about modifying the flags, but have no own experience of the flag method.
1
Removing all other drives ought to work of course, but not for all machines it is possible to just remove one, or all drives.
– Paul
yesterday
add a comment |
When you install Ubuntu (and probably Mint too) in UEFI mode, the bootloader goes into the first drive (typically the internal one), /dev/sda
, into the EFI system partition on that drive. This happens even if you tell the system to install it into another drive.
If you want the second drive to be portable and the booting to work, when the second drive is removed, you should disconnect (or unplug) the first drive before you start installing.
The following link may help,
How do I install Ubuntu to a USB key? (without using Startup Disk Creator)
In order to repair the boot system in the first drive (typically the internal one), you should disconnect the second drive before you start the repair actions.
Edit:
If you cannot disconnect/remove an internal drive there are workarounds:
Disable the internal drive in an UEFI/BIOS menu
The flag method
a. Make a note on paper of the flags of the EFI partition in the internal drive
b. Remove the flags from the EFI partition in the internal drive (for example with
gparted
, when booted from a live drive)c. Perform the installation
d. Restore the flags to the EFI partition in the internal drive (with
gparted
booted from a live drive).
I have disconnected/removed the drive, and I know people who have disabled it in an UEFI/BIOS menu, and I have read about modifying the flags, but have no own experience of the flag method.
When you install Ubuntu (and probably Mint too) in UEFI mode, the bootloader goes into the first drive (typically the internal one), /dev/sda
, into the EFI system partition on that drive. This happens even if you tell the system to install it into another drive.
If you want the second drive to be portable and the booting to work, when the second drive is removed, you should disconnect (or unplug) the first drive before you start installing.
The following link may help,
How do I install Ubuntu to a USB key? (without using Startup Disk Creator)
In order to repair the boot system in the first drive (typically the internal one), you should disconnect the second drive before you start the repair actions.
Edit:
If you cannot disconnect/remove an internal drive there are workarounds:
Disable the internal drive in an UEFI/BIOS menu
The flag method
a. Make a note on paper of the flags of the EFI partition in the internal drive
b. Remove the flags from the EFI partition in the internal drive (for example with
gparted
, when booted from a live drive)c. Perform the installation
d. Restore the flags to the EFI partition in the internal drive (with
gparted
booted from a live drive).
I have disconnected/removed the drive, and I know people who have disabled it in an UEFI/BIOS menu, and I have read about modifying the flags, but have no own experience of the flag method.
edited 19 hours ago
answered 2 days ago
sudodussudodus
1,73249
1,73249
1
Removing all other drives ought to work of course, but not for all machines it is possible to just remove one, or all drives.
– Paul
yesterday
add a comment |
1
Removing all other drives ought to work of course, but not for all machines it is possible to just remove one, or all drives.
– Paul
yesterday
1
1
Removing all other drives ought to work of course, but not for all machines it is possible to just remove one, or all drives.
– Paul
yesterday
Removing all other drives ought to work of course, but not for all machines it is possible to just remove one, or all drives.
– Paul
yesterday
add a comment |
If one already has run into the situation, and does not want to install everything anew, with all other disks disconected as sudodus suggests in his answer, I found a way:
First, if the main system cannot boot on its own, disconnect the external drive and boot from a live cd, or live usb flash drive. If not present in the live session, install the tool "boot-repair" (details for advanced use and install here, by typing in the terminal
sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update
sudo apt-get install -y boot-repair && boot-repair
and then start it by typing boot-repair
. It is has a GUI that is quite self-explanatory. Repair the boot of the main system, then restart.
Second, when the main system boots again, boot into that, connect the external drive. Copy the entire content of EFI/ubuntu
on internal drive's EFI partition (/dev/sda1
in this case) to the external drive's EFI partition twice. Once to EFI/ubuntu
there and once to EFI/Boot
. And then in EFI/Boot
rename shimx64.efi
to bootx64.efi
.
Now on the external ubuntu root partition edit the file etc/fstab
and find a line like this:
# /boot/efi was on /dev/sda1 during installation
UUID=8A3D-B724 /boot/efi vfat umask=0077 0 1
replace the UUID 8A3D-B724
, which should belong to your main system's EFI partition with the UUID of the external EFI partition. One can find that with the command blkid
or if one prefers a GUI application, one can use Disks, or Gparted.
After that is done, the external drive is bootable.
Also see:
Full install to USB flash drive, UEFI Boot
New contributor
+1 Thanks for sharing your solution :-)
– sudodus
19 hours ago
add a comment |
If one already has run into the situation, and does not want to install everything anew, with all other disks disconected as sudodus suggests in his answer, I found a way:
First, if the main system cannot boot on its own, disconnect the external drive and boot from a live cd, or live usb flash drive. If not present in the live session, install the tool "boot-repair" (details for advanced use and install here, by typing in the terminal
sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update
sudo apt-get install -y boot-repair && boot-repair
and then start it by typing boot-repair
. It is has a GUI that is quite self-explanatory. Repair the boot of the main system, then restart.
Second, when the main system boots again, boot into that, connect the external drive. Copy the entire content of EFI/ubuntu
on internal drive's EFI partition (/dev/sda1
in this case) to the external drive's EFI partition twice. Once to EFI/ubuntu
there and once to EFI/Boot
. And then in EFI/Boot
rename shimx64.efi
to bootx64.efi
.
Now on the external ubuntu root partition edit the file etc/fstab
and find a line like this:
# /boot/efi was on /dev/sda1 during installation
UUID=8A3D-B724 /boot/efi vfat umask=0077 0 1
replace the UUID 8A3D-B724
, which should belong to your main system's EFI partition with the UUID of the external EFI partition. One can find that with the command blkid
or if one prefers a GUI application, one can use Disks, or Gparted.
After that is done, the external drive is bootable.
Also see:
Full install to USB flash drive, UEFI Boot
New contributor
+1 Thanks for sharing your solution :-)
– sudodus
19 hours ago
add a comment |
If one already has run into the situation, and does not want to install everything anew, with all other disks disconected as sudodus suggests in his answer, I found a way:
First, if the main system cannot boot on its own, disconnect the external drive and boot from a live cd, or live usb flash drive. If not present in the live session, install the tool "boot-repair" (details for advanced use and install here, by typing in the terminal
sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update
sudo apt-get install -y boot-repair && boot-repair
and then start it by typing boot-repair
. It is has a GUI that is quite self-explanatory. Repair the boot of the main system, then restart.
Second, when the main system boots again, boot into that, connect the external drive. Copy the entire content of EFI/ubuntu
on internal drive's EFI partition (/dev/sda1
in this case) to the external drive's EFI partition twice. Once to EFI/ubuntu
there and once to EFI/Boot
. And then in EFI/Boot
rename shimx64.efi
to bootx64.efi
.
Now on the external ubuntu root partition edit the file etc/fstab
and find a line like this:
# /boot/efi was on /dev/sda1 during installation
UUID=8A3D-B724 /boot/efi vfat umask=0077 0 1
replace the UUID 8A3D-B724
, which should belong to your main system's EFI partition with the UUID of the external EFI partition. One can find that with the command blkid
or if one prefers a GUI application, one can use Disks, or Gparted.
After that is done, the external drive is bootable.
Also see:
Full install to USB flash drive, UEFI Boot
New contributor
If one already has run into the situation, and does not want to install everything anew, with all other disks disconected as sudodus suggests in his answer, I found a way:
First, if the main system cannot boot on its own, disconnect the external drive and boot from a live cd, or live usb flash drive. If not present in the live session, install the tool "boot-repair" (details for advanced use and install here, by typing in the terminal
sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update
sudo apt-get install -y boot-repair && boot-repair
and then start it by typing boot-repair
. It is has a GUI that is quite self-explanatory. Repair the boot of the main system, then restart.
Second, when the main system boots again, boot into that, connect the external drive. Copy the entire content of EFI/ubuntu
on internal drive's EFI partition (/dev/sda1
in this case) to the external drive's EFI partition twice. Once to EFI/ubuntu
there and once to EFI/Boot
. And then in EFI/Boot
rename shimx64.efi
to bootx64.efi
.
Now on the external ubuntu root partition edit the file etc/fstab
and find a line like this:
# /boot/efi was on /dev/sda1 during installation
UUID=8A3D-B724 /boot/efi vfat umask=0077 0 1
replace the UUID 8A3D-B724
, which should belong to your main system's EFI partition with the UUID of the external EFI partition. One can find that with the command blkid
or if one prefers a GUI application, one can use Disks, or Gparted.
After that is done, the external drive is bootable.
Also see:
Full install to USB flash drive, UEFI Boot
New contributor
edited 6 hours ago
New contributor
answered yesterday
PaulPaul
215
215
New contributor
New contributor
+1 Thanks for sharing your solution :-)
– sudodus
19 hours ago
add a comment |
+1 Thanks for sharing your solution :-)
– sudodus
19 hours ago
+1 Thanks for sharing your solution :-)
– sudodus
19 hours ago
+1 Thanks for sharing your solution :-)
– sudodus
19 hours ago
add a comment |
Paul is a new contributor. Be nice, and check out our Code of Conduct.
Paul is a new contributor. Be nice, and check out our Code of Conduct.
Paul is a new contributor. Be nice, and check out our Code of Conduct.
Paul is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f510773%2ftwo-grub-installations-destroying-each-other%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
Once booted into your Mint, have you checked the contents of
/boot/efi/EFI
? Did you end up with mint and ubuntu side by side, or does mint (cheekily) install its bootloader to/boot/efi/EFI/ubuntu
?– Philip Couling
Apr 5 at 23:10
@PhilipCouling I checked, and yes, I found
/boot/efi/EFI/ubuntu
, will update the question accordingly– Paul
2 days ago