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;








2















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.










share|improve this question









New contributor




Paul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • 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

















2















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.










share|improve this question









New contributor




Paul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • 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













2












2








2








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.










share|improve this question









New contributor




Paul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












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






share|improve this question









New contributor




Paul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




Paul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited yesterday







Paul













New contributor




Paul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked Apr 5 at 17:51









PaulPaul

215




215




New contributor




Paul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Paul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Paul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












  • 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











  • @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










2 Answers
2






active

oldest

votes


















1














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.






share|improve this answer




















  • 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














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






share|improve this answer










New contributor




Paul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • +1 Thanks for sharing your solution :-)

    – sudodus
    19 hours ago











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.









draft saved

draft discarded


















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









1














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.






share|improve this answer




















  • 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














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.






share|improve this answer




















  • 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








1







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.






share|improve this answer















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.







share|improve this answer














share|improve this answer



share|improve this answer








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












  • 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













1














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






share|improve this answer










New contributor




Paul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • +1 Thanks for sharing your solution :-)

    – sudodus
    19 hours ago















1














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






share|improve this answer










New contributor




Paul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • +1 Thanks for sharing your solution :-)

    – sudodus
    19 hours ago













1












1








1







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






share|improve this answer










New contributor




Paul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.










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







share|improve this answer










New contributor




Paul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this answer



share|improve this answer








edited 6 hours ago





















New contributor




Paul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









answered yesterday









PaulPaul

215




215




New contributor




Paul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Paul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Paul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












  • +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





+1 Thanks for sharing your solution :-)

– sudodus
19 hours ago










Paul is a new contributor. Be nice, and check out our Code of Conduct.









draft saved

draft discarded


















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.




draft saved


draft discarded














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





















































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

getting Checkpoint VPN SSL Network Extender working in the command lineHow to connect to CheckPoint VPN on Ubuntu 18.04LTS?Will the Linux ( red-hat ) Open VPNC Client connect to checkpoint or nortel VPN gateways?VPN client for linux machine + support checkpoint gatewayVPN SSL Network Extender in FirefoxLinux Checkpoint SNX tool configuration issuesCheck Point - Connect under Linux - snx + OTPSNX VPN Ububuntu 18.XXUsing Checkpoint VPN SSL Network Extender CLI with certificateVPN with network manager (nm-applet) is not workingWill the Linux ( red-hat ) Open VPNC Client connect to checkpoint or nortel VPN gateways?VPN client for linux machine + support checkpoint gatewayImport VPN config files to NetworkManager from command lineTrouble connecting to VPN using network-manager, while command line worksStart a VPN connection with PPTP protocol on command linestarting a docker service daemon breaks the vpn networkCan't connect to vpn with Network-managerVPN SSL Network Extender in FirefoxUsing Checkpoint VPN SSL Network Extender CLI with certificate

NetworkManager fails with “Could not find source connection”Trouble connecting to VPN using network-manager, while command line worksHow can I be notified about state changes to a VPN adapterBacktrack 5 R3 - Refuses to connect to VPNFeed all traffic through OpenVPN for a specific network namespace onlyRun daemon on startup in Debian once openvpn connection establishedpfsense tcp connection between openvpn and lan is brokenInternet connection problem with web browsers onlyWhy does NetworkManager explicitly support tun/tap devices?Browser issues with VPNTwo IP addresses assigned to the same network card - OpenVPN issues?Cannot connect to WiFi with nmcli, although secrets are provided

대한민국 목차 국명 지리 역사 정치 국방 경제 사회 문화 국제 순위 관련 항목 각주 외부 링크 둘러보기 메뉴북위 37° 34′ 08″ 동경 126° 58′ 36″ / 북위 37.568889° 동경 126.976667°  / 37.568889; 126.976667ehThe Korean Repository문단을 편집문단을 편집추가해Clarkson PLC 사Report for Selected Countries and Subjects-Korea“Human Development Index and its components: P.198”“http://www.law.go.kr/%EB%B2%95%EB%A0%B9/%EB%8C%80%ED%95%9C%EB%AF%BC%EA%B5%AD%EA%B5%AD%EA%B8%B0%EB%B2%95”"한국은 국제법상 한반도 유일 합법정부 아니다" - 오마이뉴스 모바일Report for Selected Countries and Subjects: South Korea격동의 역사와 함께한 조선일보 90년 : 조선일보 인수해 혁신시킨 신석우, 임시정부 때는 '대한민국' 국호(國號) 정해《우리가 몰랐던 우리 역사: 나라 이름의 비밀을 찾아가는 역사 여행》“남북 공식호칭 ‘남한’‘북한’으로 쓴다”“Corea 대 Korea, 누가 이긴 거야?”국내기후자료 - 한국[김대중 前 대통령 서거] 과감한 구조개혁 'DJ노믹스'로 최단기간 환란극복 :: 네이버 뉴스“이라크 "韓-쿠르드 유전개발 MOU 승인 안해"(종합)”“해외 우리국민 추방사례 43%가 일본”차기전차 K2'흑표'의 세계 최고 전력 분석, 쿠키뉴스 엄기영, 2007-03-02두산인프라, 헬기잡는 장갑차 'K21'...내년부터 공급, 고뉴스 이대준, 2008-10-30과거 내용 찾기mk 뉴스 - 구매력 기준으로 보면 한국 1인당 소득 3만弗과거 내용 찾기"The N-11: More Than an Acronym"Archived조선일보 최우석, 2008-11-01Global 500 2008: Countries - South Korea“몇년째 '시한폭탄'... 가계부채, 올해는 터질까”가구당 부채 5000만원 처음 넘어서“‘빚’으로 내몰리는 사회.. 위기의 가계대출”“[경제365] 공공부문 부채 급증…800조 육박”“"소득 양극화 다소 완화...불평등은 여전"”“공정사회·공생발전 한참 멀었네”iSuppli,08年2QのDRAMシェア・ランキングを発表(08/8/11)South Korea dominates shipbuilding industry | Stock Market News & Stocks to Watch from StraightStocks한국 자동차 생산, 3년 연속 세계 5위자동차수출 '현대-삼성 웃고 기아-대우-쌍용은 울고' 과거 내용 찾기동반성장위 창립 1주년 맞아Archived"중기적합 3개업종 합의 무시한 채 선정"李대통령, 사업 무분별 확장 소상공인 생계 위협 질타삼성-LG, 서민업종인 빵·분식사업 잇따라 철수상생은 뒷전…SSM ‘몸집 불리기’ 혈안Archived“경부고속도에 '아시안하이웨이' 표지판”'철의 실크로드' 앞서 '말(言)의 실크로드'부터, 프레시안 정창현, 2008-10-01“'서울 지하철은 안전한가?'”“서울시 “올해 안에 모든 지하철역 스크린도어 설치””“부산지하철 1,2호선 승강장 안전펜스 설치 완료”“전교조, 정부 노조 통계서 처음 빠져”“[Weekly BIZ] 도요타 '제로 이사회'가 리콜 사태 불러들였다”“S Korea slams high tuition costs”““정치가 여론 양극화 부채질… 합리주의 절실””“〈"`촛불집회'는 민주주의의 질적 변화 상징"〉”““촛불집회가 민주주의 왜곡 초래””“국민 65%, "한국 노사관계 대립적"”“한국 국가경쟁력 27위‥노사관계 '꼴찌'”“제대로 형성되지 않은 대한민국 이념지형”“[신년기획-갈등의 시대] 갈등지수 OECD 4위…사회적 손실 GDP 27% 무려 300조”“2012 총선-대선의 키워드는 '국민과 소통'”“한국 삶의 질 27위, 2000년과 2008년 연속 하위권 머물러”“[해피 코리아] 행복점수 68점…해외 평가선 '낙제점'”“한국 어린이·청소년 행복지수 3년 연속 OECD ‘꼴찌’”“한국 이혼율 OECD중 8위”“[통계청] 한국 이혼율 OECD 4위”“오피니언 [이렇게 생각한다] `부부의 날` 에 돌아본 이혼율 1위 한국”“Suicide Rates by Country, Global Health Observatory Data Repository.”“1. 또 다른 차별”“오피니언 [편집자에게] '왕따'와 '패거리 정치' 심리는 닮은꼴”“[미래한국리포트] 무한경쟁에 빠진 대한민국”“대학생 98% "외모가 경쟁력이라는 말 동의"”“특급호텔 웨딩·200만원대 유모차… "남보다 더…" 호화病, 고질병 됐다”“[스트레스 공화국] ① 경쟁사회, 스트레스 쌓인다”““매일 30여명 자살 한국, 의사보다 무속인에…””“"자살 부르는 '우울증', 환자 중 85% 치료 안 받아"”“정신병원을 가다”“대한민국도 ‘묻지마 범죄’,안전지대 아니다”“유엔 "학생 '성적 지향'에 따른 차별 금지하라"”“유엔아동권리위원회 보고서 및 번역본 원문”“고졸 성공스토리 담은 '제빵왕 김탁구' 드라마 나온다”“‘빛 좋은 개살구’ 고졸 취업…실습 대신 착취”원본 문서“정신건강, 사회적 편견부터 고쳐드립니다”‘소통’과 ‘행복’에 목 마른 사회가 잠들어 있던 ‘심리학’ 깨웠다“[포토] 사유리-곽금주 교수의 유쾌한 심리상담”“"올해 한국인 평균 영화관람횟수 세계 1위"(종합)”“[게임연중기획] 게임은 문화다-여가활동 1순위 게임”“영화속 ‘영어 지상주의’ …“왠지 씁쓸한데””“2월 `신문 부수 인증기관` 지정..방송법 후속작업”“무료신문 성장동력 ‘차별성’과 ‘갈등해소’”대한민국 국회 법률지식정보시스템"Pew Research Center's Religion & Public Life Project: South Korea"“amp;vwcd=MT_ZTITLE&path=인구·가구%20>%20인구총조사%20>%20인구부문%20>%20 총조사인구(2005)%20>%20전수부문&oper_YN=Y&item=&keyword=종교별%20인구& amp;lang_mode=kor&list_id= 2005년 통계청 인구 총조사”원본 문서“한국인이 좋아하는 취미와 운동 (2004-2009)”“한국인이 좋아하는 취미와 운동 (2004-2014)”Archived“한국, `부분적 언론자유국' 강등〈프리덤하우스〉”“국경없는기자회 "한국, 인터넷감시 대상국"”“한국, 조선산업 1위 유지(S. Korea Stays Top Shipbuilding Nation) RZD-Partner Portal”원본 문서“한국, 4년 만에 ‘선박건조 1위’”“옛 마산시,인터넷속도 세계 1위”“"한국 초고속 인터넷망 세계1위"”“인터넷·휴대폰 요금, 외국보다 훨씬 비싸”“한국 관세행정 6년 연속 세계 '1위'”“한국 교통사고 사망자 수 OECD 회원국 중 2위”“결핵 후진국' 한국, 환자가 급증한 이유는”“수술은 신중해야… 자칫하면 생명 위협”대한민국분류대한민국의 지도대한민국 정부대표 다국어포털대한민국 전자정부대한민국 국회한국방송공사about korea and information korea브리태니커 백과사전(한국편)론리플래닛의 정보(한국편)CIA의 세계 정보(한국편)마리암 부디아 (Mariam Budia),『한국: 하늘이 내린 한 폭의 그림』, 서울: 트랜스라틴 19호 (2012년 3월)대한민국ehehehehehehehehehehehehehehWorldCat132441370n791268020000 0001 2308 81034078029-6026373548cb11863345f(데이터)00573706ge128495