Is it possible to 'install' an operating system by putting the EFI/boot & system files in the right place?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












3















If I were to partition a /dev/sdb1, place all the needed root/home files, then go to my own /boot/efi folder and put the files there with whatever UUID I need, would it then be bootable?










share|improve this question






















  • No, because you'll also need a bootloader like grub or uboot.

    – mikewhatever
    Feb 20 at 5:33











  • I suspected it was yes, so tried & failed. I suspected I hadn't got it right, but decided it wasn't worth the effort & installed normally (so I defer to mikewhatever's prior comment)

    – guiverc
    Feb 20 at 5:38











  • Well I've got rEFInd, a USB with recovery, an empty NTFS partition and a lot of frustration. Noted on needing a bootloader, I think I can try taking it from a VM or the USB.

    – avisitoritseems
    Feb 20 at 6:01















3















If I were to partition a /dev/sdb1, place all the needed root/home files, then go to my own /boot/efi folder and put the files there with whatever UUID I need, would it then be bootable?










share|improve this question






















  • No, because you'll also need a bootloader like grub or uboot.

    – mikewhatever
    Feb 20 at 5:33











  • I suspected it was yes, so tried & failed. I suspected I hadn't got it right, but decided it wasn't worth the effort & installed normally (so I defer to mikewhatever's prior comment)

    – guiverc
    Feb 20 at 5:38











  • Well I've got rEFInd, a USB with recovery, an empty NTFS partition and a lot of frustration. Noted on needing a bootloader, I think I can try taking it from a VM or the USB.

    – avisitoritseems
    Feb 20 at 6:01













3












3








3








If I were to partition a /dev/sdb1, place all the needed root/home files, then go to my own /boot/efi folder and put the files there with whatever UUID I need, would it then be bootable?










share|improve this question














If I were to partition a /dev/sdb1, place all the needed root/home files, then go to my own /boot/efi folder and put the files there with whatever UUID I need, would it then be bootable?







uefi






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 20 at 5:04









avisitoritseemsavisitoritseems

10310




10310












  • No, because you'll also need a bootloader like grub or uboot.

    – mikewhatever
    Feb 20 at 5:33











  • I suspected it was yes, so tried & failed. I suspected I hadn't got it right, but decided it wasn't worth the effort & installed normally (so I defer to mikewhatever's prior comment)

    – guiverc
    Feb 20 at 5:38











  • Well I've got rEFInd, a USB with recovery, an empty NTFS partition and a lot of frustration. Noted on needing a bootloader, I think I can try taking it from a VM or the USB.

    – avisitoritseems
    Feb 20 at 6:01

















  • No, because you'll also need a bootloader like grub or uboot.

    – mikewhatever
    Feb 20 at 5:33











  • I suspected it was yes, so tried & failed. I suspected I hadn't got it right, but decided it wasn't worth the effort & installed normally (so I defer to mikewhatever's prior comment)

    – guiverc
    Feb 20 at 5:38











  • Well I've got rEFInd, a USB with recovery, an empty NTFS partition and a lot of frustration. Noted on needing a bootloader, I think I can try taking it from a VM or the USB.

    – avisitoritseems
    Feb 20 at 6:01
















No, because you'll also need a bootloader like grub or uboot.

– mikewhatever
Feb 20 at 5:33





No, because you'll also need a bootloader like grub or uboot.

– mikewhatever
Feb 20 at 5:33













I suspected it was yes, so tried & failed. I suspected I hadn't got it right, but decided it wasn't worth the effort & installed normally (so I defer to mikewhatever's prior comment)

– guiverc
Feb 20 at 5:38





I suspected it was yes, so tried & failed. I suspected I hadn't got it right, but decided it wasn't worth the effort & installed normally (so I defer to mikewhatever's prior comment)

– guiverc
Feb 20 at 5:38













Well I've got rEFInd, a USB with recovery, an empty NTFS partition and a lot of frustration. Noted on needing a bootloader, I think I can try taking it from a VM or the USB.

– avisitoritseems
Feb 20 at 6:01





Well I've got rEFInd, a USB with recovery, an empty NTFS partition and a lot of frustration. Noted on needing a bootloader, I think I can try taking it from a VM or the USB.

– avisitoritseems
Feb 20 at 6:01










1 Answer
1






active

oldest

votes


















5














Yes, the "right place" being an EFI FAT partition for the shimx64.efi and grubx64.efi bootloaders, along with the grub.cfg (all in EFI/ubuntu, and copies in /EFI/Boot with shimx64.efi renamed to bootx64.efi. Your root should be on an ext4 partition. The only UUID change needed is in the EFI partition's grub.cfg file to use the root of your system (assuming you just copied the whole EFI from another system. It's really pretty simple, and will even boot a legacy install of the root this way (not secure boot, but UEFI). Surprisingly, even the legacy /boot/grub/grub.cfg will work for a UEFI boot. You can add the /boot/efi and fstab entry for mounting the EFI, but that would only be needed if you tried to update shim/grub, (assuming you have the efi versions of the packages). I've been running a disk set up this way (legacy install, UEFI files added from another system) for years without issue. I did add the /boot/efi and fstab entry, but never bothered with the shi9m/grub efi package change.






share|improve this answer























  • Awesome. I have Linux root as ext4 and its separate boot partition as FAT32. I'm going to run a VM with NTLite, remove junk and copy it over network share to the empty partition, then copy the needed files to my /boot as well. I'll comment again if I run into any errors, thank you.

    – avisitoritseems
    Feb 20 at 6:59











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
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1119721%2fis-it-possible-to-install-an-operating-system-by-putting-the-efi-boot-system%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









5














Yes, the "right place" being an EFI FAT partition for the shimx64.efi and grubx64.efi bootloaders, along with the grub.cfg (all in EFI/ubuntu, and copies in /EFI/Boot with shimx64.efi renamed to bootx64.efi. Your root should be on an ext4 partition. The only UUID change needed is in the EFI partition's grub.cfg file to use the root of your system (assuming you just copied the whole EFI from another system. It's really pretty simple, and will even boot a legacy install of the root this way (not secure boot, but UEFI). Surprisingly, even the legacy /boot/grub/grub.cfg will work for a UEFI boot. You can add the /boot/efi and fstab entry for mounting the EFI, but that would only be needed if you tried to update shim/grub, (assuming you have the efi versions of the packages). I've been running a disk set up this way (legacy install, UEFI files added from another system) for years without issue. I did add the /boot/efi and fstab entry, but never bothered with the shi9m/grub efi package change.






share|improve this answer























  • Awesome. I have Linux root as ext4 and its separate boot partition as FAT32. I'm going to run a VM with NTLite, remove junk and copy it over network share to the empty partition, then copy the needed files to my /boot as well. I'll comment again if I run into any errors, thank you.

    – avisitoritseems
    Feb 20 at 6:59
















5














Yes, the "right place" being an EFI FAT partition for the shimx64.efi and grubx64.efi bootloaders, along with the grub.cfg (all in EFI/ubuntu, and copies in /EFI/Boot with shimx64.efi renamed to bootx64.efi. Your root should be on an ext4 partition. The only UUID change needed is in the EFI partition's grub.cfg file to use the root of your system (assuming you just copied the whole EFI from another system. It's really pretty simple, and will even boot a legacy install of the root this way (not secure boot, but UEFI). Surprisingly, even the legacy /boot/grub/grub.cfg will work for a UEFI boot. You can add the /boot/efi and fstab entry for mounting the EFI, but that would only be needed if you tried to update shim/grub, (assuming you have the efi versions of the packages). I've been running a disk set up this way (legacy install, UEFI files added from another system) for years without issue. I did add the /boot/efi and fstab entry, but never bothered with the shi9m/grub efi package change.






share|improve this answer























  • Awesome. I have Linux root as ext4 and its separate boot partition as FAT32. I'm going to run a VM with NTLite, remove junk and copy it over network share to the empty partition, then copy the needed files to my /boot as well. I'll comment again if I run into any errors, thank you.

    – avisitoritseems
    Feb 20 at 6:59














5












5








5







Yes, the "right place" being an EFI FAT partition for the shimx64.efi and grubx64.efi bootloaders, along with the grub.cfg (all in EFI/ubuntu, and copies in /EFI/Boot with shimx64.efi renamed to bootx64.efi. Your root should be on an ext4 partition. The only UUID change needed is in the EFI partition's grub.cfg file to use the root of your system (assuming you just copied the whole EFI from another system. It's really pretty simple, and will even boot a legacy install of the root this way (not secure boot, but UEFI). Surprisingly, even the legacy /boot/grub/grub.cfg will work for a UEFI boot. You can add the /boot/efi and fstab entry for mounting the EFI, but that would only be needed if you tried to update shim/grub, (assuming you have the efi versions of the packages). I've been running a disk set up this way (legacy install, UEFI files added from another system) for years without issue. I did add the /boot/efi and fstab entry, but never bothered with the shi9m/grub efi package change.






share|improve this answer













Yes, the "right place" being an EFI FAT partition for the shimx64.efi and grubx64.efi bootloaders, along with the grub.cfg (all in EFI/ubuntu, and copies in /EFI/Boot with shimx64.efi renamed to bootx64.efi. Your root should be on an ext4 partition. The only UUID change needed is in the EFI partition's grub.cfg file to use the root of your system (assuming you just copied the whole EFI from another system. It's really pretty simple, and will even boot a legacy install of the root this way (not secure boot, but UEFI). Surprisingly, even the legacy /boot/grub/grub.cfg will work for a UEFI boot. You can add the /boot/efi and fstab entry for mounting the EFI, but that would only be needed if you tried to update shim/grub, (assuming you have the efi versions of the packages). I've been running a disk set up this way (legacy install, UEFI files added from another system) for years without issue. I did add the /boot/efi and fstab entry, but never bothered with the shi9m/grub efi package change.







share|improve this answer












share|improve this answer



share|improve this answer










answered Feb 20 at 5:47









ubfan1ubfan1

9,78941730




9,78941730












  • Awesome. I have Linux root as ext4 and its separate boot partition as FAT32. I'm going to run a VM with NTLite, remove junk and copy it over network share to the empty partition, then copy the needed files to my /boot as well. I'll comment again if I run into any errors, thank you.

    – avisitoritseems
    Feb 20 at 6:59


















  • Awesome. I have Linux root as ext4 and its separate boot partition as FAT32. I'm going to run a VM with NTLite, remove junk and copy it over network share to the empty partition, then copy the needed files to my /boot as well. I'll comment again if I run into any errors, thank you.

    – avisitoritseems
    Feb 20 at 6:59

















Awesome. I have Linux root as ext4 and its separate boot partition as FAT32. I'm going to run a VM with NTLite, remove junk and copy it over network share to the empty partition, then copy the needed files to my /boot as well. I'll comment again if I run into any errors, thank you.

– avisitoritseems
Feb 20 at 6:59






Awesome. I have Linux root as ext4 and its separate boot partition as FAT32. I'm going to run a VM with NTLite, remove junk and copy it over network share to the empty partition, then copy the needed files to my /boot as well. I'll comment again if I run into any errors, thank you.

– avisitoritseems
Feb 20 at 6:59


















draft saved

draft discarded
















































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.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1119721%2fis-it-possible-to-install-an-operating-system-by-putting-the-efi-boot-system%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

How to check contact read email or not when send email to Individual?

Displaying single band from multi-band raster using QGIS

How many registers does an x86_64 CPU actually have?